BSOD - Fresh Hardware & Windows 7 Installation

[lorika]

Been having problems with this new ITX system. Changed motherboard 4 times, changed CPU once. In order to keep it short, I won't elaborate on the problems happened in the last 3 times.

This time around, I get 3 BSODs within a day after installing new motherboard and freshly installed Windows 7 64-bit. The third BSOD happened while running the dump & system collection app.

The necessary files are attached. Additional info below:

Is Windows 7 . . .
- x64
- Reinstalled OS on the system
- OEM version of Windows 7 (disc given)
- Age of hardware: Less than a month (motherboard is only one-day old)
- Age of OS: Less than one-day old

Please help to shed some light on what's wrong.

Thank you very much.

Cheers,
Lorika

 

[reventon]

Hi,

What Model PSU are you using?

The dump files do not point to a 3rd party driver as a probable cause, meaning that it is either a "hidden" driver or hardware. As your drivers look ok, and you have re-installed several times I suspect hardware on this one.

Run a memtest yet?

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: ISO Recorder v3 Download (How to use IsoRecorder)

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 22:40:50.601 2010 (GMT+12)
System Uptime: 0 days 1:07:18.835
BugCheck 3B, {c0000005, fffffa8004e784d1, fffff880071fece0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 19:45:36.793 2010 (GMT+12)
System Uptime: 0 days 1:24:04.981
BugCheck 3B, {c0000005, fffff80002bea42e, fffff88006d195d0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 17:37:28.869 2010 (GMT+12)
System Uptime: 0 days 1:03:47.103
BugCheck A, {fffffa802445e4a2, 2, 0, fffff800028db077}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+157 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Jonathan_King]

In addition to reventon's good advice, please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[lorika]

Thanks to Jonathan and Reventon for the replies.

I'm using Silverstone's SG05 ITX casing and the 80+ 300W PSU that comes with it. The PSU is manufactured by FSP Group Inc.

I did a 10-pass standard Windows Memory Diagnostic that came with Windows 7 before and the results came back clean. Is this test sufficient?

Yup, I ran Winbdg on the dump files and all seem to be pointing at ntkrnlmp.exe. I'm baffled.

I haven't try the Driver Verifier. Didn't know there's such a thing previously. Will try it.

Thanks!

 

[CarlTR6]

lorika, the Windows memory test is sometimes not thorough enough. Follow reventon's instructions.

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: ISO Recorder v3 Download (How to use IsoRecorder)

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.