BSOD on Windows startup?

Henrik

New member
Hey guys...

So I have been bothered with this little problem I have for quite some time now.. For some reason my computer bluescreens every now and then when I boot in to Windows. Not every time, it seems very random. It's always just before the login screen appears. It has never happend durring the loading animation if you know what I mean...
tongue.gif


I have my CPU oc'ed to 4.0Ghz with the RAM and FSB at 1700Mhz. So my OC is not stable you might say. But I have run LinX all memory usage 100 cycles for several times and never had a error.. (It's about 4 hours run time on my pc). Should i run it for a longer time or whats up here? I find it strange that I get bluescrren only on Boot and NEVER once I get in to Windows... I mean will a boot stress more then LinX??
huh.gif


What do you guys think? Am i not stable after all?

Specs:

CPU: QX9650 4.0Ghz @ 1.344V under load (1.401V idle)

XFX 790i

FSB: 1700Mhz @ 1.3V

Memory: 2x2gb Corsair Dominator 1600Mhz @ 1700Mhz 9-10-9-26

SPP: 1.35V

MCP: 1.4V

GTlVref: (mV)

-45

-45

00

00

OS: Win7 64bit on 2x Corsair F60 in Raid 0
 
Hey guys...

So I have been bothered with this little problem I have for quite some time now.. For some reason my computer bluescreens every now and then when I boot in to Windows. Not every time, it seems very random. It's always just before the login screen appears. It has never happend durring the loading animation if you know what I mean...
tongue.gif


I have my CPU oc'ed to 4.0Ghz with the RAM and FSB at 1700Mhz. So my OC is not stable you might say. But I have run LinX all memory usage 100 cycles for several times and never had a error.. (It's about 4 hours run time on my pc). Should i run it for a longer time or whats up here? I find it strange that I get bluescrren only on Boot and NEVER once I get in to Windows... I mean will a boot stress more then LinX??
huh.gif


What do you guys think? Am i not stable after all?

Specs:

CPU: QX9650 4.0Ghz @ 1.344V under load (1.401V idle)

XFX 790i

FSB: 1700Mhz @ 1.3V

Memory: 2x2gb Corsair Dominator 1600Mhz @ 1700Mhz 9-10-9-26

SPP: 1.35V

MCP: 1.4V

GTlVref: (mV)

-45

-45

00

00

OS: Win7 64bit on 2x Corsair F60 in Raid 0

Have you tried prime 95? it could be that the cpu needs a bit more juice.
 
Yeah I have, I ran Prime for almost 6 hours (without an error) then I canceled it. Could be that it needs more Vcore but I'm a little concerned about going 1.4+ on Vcore. I have heard some people runing 45nm CPUs at 1.45V. what do you think is "safe" to run on these 45nm CPUs?
 

Thanks. I have tested unplugging all my USB devices, no improvements. Its not the boot.ini file because if I understand it correctly win7 dose not use that file.. I find it hard to believe that the ntoskrnl.exe file would be corrupt as I have re installed Windows.

And raising the Vcore did sadly nothing, I also tried different GTLVref values and RAM timings nothing helped.. So I'm really lost right now... But I will keep at it, right now I'm not home so testing will have to wait...

If any one has a clue or just something I could try, let me know.
 
Things to try:

1. Read this about testing your drivers

2. Go into safe mode (if it doesn't blue screen)

Type in msconfig in the search box and then hit enter. goto the services tab and click on the check box with "hide all microsoft services" then hit disable all. Then goto the startup tab and hit disable all, apply and exit - hit restart later.

  • Run cmd (as admin) and enter these commands (without quotes):
  • "chkdsk /f /r" (chkdsk will schedule to run after restart)
  • "sfc /scannow" - after that's done it may want to restart

3. Go into the repair centre using your windows installation disk.

Go to the command prompt at the bottom of the list and enter the following commands one by one:

  • "c:"
  • "bootrec /fixmbr"
  • "bootrec /fixboot"

4. Reset the bios values to optimised defaults.

5. Remove all sticks of ram and boot-up with 1 stick, verify it works place it to one-side and repeat process with another stick (on its own). After all sticks have been tested 1 by 1, test 2 sticks, gradually repeating the process and see if you get any faults.

6. Tbh your best bet could be to just backup your data and re-install windows, cause there is definitely something wrong or conflicting with ntoskrnl.exe

All I have for now, btw try steps 1 by 1 see if it works, if not move onto next.
 
Yes that is correct it's called Vdroop, that's the big downside of the 790i Ultra and not the FTW edition... the Ultra does not have LLC
angry.gif
 
Back
Top