BSOD Help

Jonathan_King · 09 Jun 2010

The only way you can damage your system is by increasing the voltage too much. Other than that, messing with clock speeds can only make the problem worse, or fix it.

jsparry · 10 Jun 2010

Well i tried.

I managed to up the voltage and timings to what was stated on the ram.

And it lasted all night without any issues however after a restart this morning it went back to its usual trick and bsod me.

Message seemed the same as before.

I also noticed that when i turn the power on all the fans and lights turn on for a second then all go off then come back on again. just as it tries to post.

I think i'll try a format tonight when i get home from work (10am here) and see how that goes.

Fumz · 10 Jun 2010

A good rule of thumb: whenever you're going to adjust voltage and timings in the bios, first set the correct voltage, save your changes and reboot back into the bios. Then set the correct timings, again saving your changes and rebooting into the bios, this time to make sure your changes have been applied correctly.

jsparry · 10 Jun 2010

Any chance someone can take a look at these latest memory dumps.

Been trying everything i can think of....

I'm starting to think its hardware and trying to workout what device.

Thanks James

Jonathan_King · 11 Jun 2010

Still looks like hardware.

Code:


BugCheck 1E, {0, 0, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_AllocIoRequest+30 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 6B, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+1331 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80002d89f35, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+2ff )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

You can try updating your USB port drivers, but I suspect RAM.

jsparry · 11 Jun 2010

Well, I've rulled out Gfx card (have a spare).

Just downloaded a HHD checker.

I've run the memory tester again and its passed all 4 times. If memory is to blame could it still pass?

jsparry · 12 Jun 2010

Is there any way to check if its the mobo, or psu.

jsparry · 12 Jun 2010

I've tested the ram one stick at a time with Memtest86+.

1st stick passed 5 times.

2nd stick is on 2nd pass atm

Jonathan_King · 12 Jun 2010

I must have been foggy the first time I responded?

Why did I not ask you to enable driver verifier?

jsparry · 12 Jun 2010

Ahh ok ill put it back on now then.

I've only got 1 stick on ram in atm and i'm doing a stress test to watch mobo voltages to run out psu or mobo.