BSOD issue on new Win 7 machine

Rmiller · 28 Sep 2010

A preemptive thanks for this incredible service you provide! This forum is an amazing resource of information and has been very helpful in bringing me up to speed on the Win 7 OS.

This machine is about 2 weeks old, and starting about a week into its life, I started getting a system hang once a login session and usually within 10 minutes of login.

Then in the last few days I started getting BSOD's instead of hangs. I've had probably 4 or 5 of those - and my impression is that they happen during the system "warm-up" right after a login. I usually don't see them again after I reboot from the first one.

Thanks again for any help and direction you can give.

Bob

Other machine info:
Win 7 Ultimate x64
Original OS on system
OEM version
Age of system and OS: 2 weeks

usasma · 30 Sep 2010

The errors are STOP 0x124 errors. These are errors that are caught by your CPU and passed on to Windows. They don't have much information that's useful to us, so we have to resort to other methods to diagnose them.

These are hardware errors, most often either broken or incompatible hardware. If it's not that, then we wonder about Windows corruptions - or even corrupted 3rd party drivers (there is some disagreement about this last one).

So, check carefully to ensure that all your hardware and software is compatible. Use this link to check: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Jiggle/wiggle/reseat all cards and cables. I got this error with a poorly seated video card not long ago. Reseating the card cured the error.

Follow the instructions at this link for further troubleshooting: Stop 0x124 - what it means and what to try

BSOD BUGCHECK SUMMARY

Code:


*** WARNING: Unable to verify timestamp for Unknown_Module_5b5cff42`004c0000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_5b5cff42`004c0000
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 10:36:09.500 2010 (UTC - 4:00)
System Uptime: 0 days 9:30:40.059
*** WARNING: Unable to verify timestamp for Unknown_Module_5b5cff42`004c0000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_5b5cff42`004c0000
Probably caused by : Unknown_Image
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`06bc2028 00000000`b8000000 00000000`00800e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 23:22:10.102 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:22.242
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`05d6a028 00000000`b8000000 00000000`00800e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 26 23:44:37.375 2010 (UTC - 4:00)
System Uptime: 0 days 2:47:21.515
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`05d6d028 00000000`b8000000 00000000`00800e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Rmiller · 30 Sep 2010

Dear usasma,

Thanks for the tips and ideas on where to look. I'll dig into the links you suggested and do an overhaul on the hardware (working all connections) when I get free time tomorrow afternoon.

Also note at one point I saw a STOP 0x104 error, which sounded liek from your list, to potentially be disk related. I'll start there first. I am using an INTEL SSD - I did check the drivers of all my devices and they are up to date.

And thanks again for the time you spent and the service you provide! It's invaluable.

I'll let you know how it turns out.

Best regards,

Bob

Rmiller · 11 Oct 2010

I thought I would post the followup in case it helped anyone. My system's symptoms were a BSOD 0x124 hardware error or a hung system in the first 5-10 minutes after power up. If I rebooted at that point the machine would run "forever".

I had already updated all drivers and BIOS, so I:
- reseated all connectors and plugs - no change
- Cloned the C: drive and rebooted off the clone - no change
- swapped memory - no change
- removed a number of devices - no change

Finally I got a motherboard swap and the problem seems to have gone away (a couple days into it).

Thanks again for all of you who are providing awesome support. It's incredibly helpful,

Bob

Rmiller · 31 Oct 2010

Dear usasma,

Well, I thought I was home free, but it turns out I wasn't. The problem has come back. I have been trying a number of tests to zero in and would like your advice as to what to look at next.

The failure mode is a BSOD or hang, within 1 hour (typ 5 min) of first system start up everyday (except one case). Once the system has crashed, I can restart and run for hours and never see a problem. Based on that and the tests I have done I am getting to the point that I now suspect a driver issue not hardware.

Here are some of the tests I've done:

1) My System integrator replaced the Intel motherboard, CPU (i7 980) and memory (6G) - problem seemed to go away for a few days and now is back
2) Perf95 mem stress test for 3 hours - fine
3) Furmark test of the video card (GeoForce GTX 470) for 1 hour - no problems.
4) System had C: SSD and D: WD raptor HD. In case it was the SD I cloned the SSD to the HD, and for the last 3 days ran C: drive as WD HD - problem still there
5) I disconnected all un-needed HW: SD card reader - that was internally connected to MB, 2 DVD drives (SATA) and SSD (SATA)- still problem. Running off C: WD HD.
6) Uninstalled Avast Anti-virus
7) Did MS driver compatibility - Found .NET 1.1 as incompatible. I haven't found the application SW associated with it. I assume that wouldn't cause a BSOD issue. Need to look into later.

Recent crashes were at:
10/31: 9:08AM 0x9C error BSOD - I thought these errors were only found on Win XP machines - could this be an old driver? Could that be the cause?
10/30: 8:42AM 0x101 BSOD
10/29: 9:25AM Hang
10/28: machine not used
10/27: 8:25AM Hang
10/26: 9:10 AM slow --> hang, BSOD; 10:30PM switch user to Admin and had crash 0x101 BSOD
10/25: 8:50AM 0x124 BSOD

I tried to get a little educated on this and did a WinDbg review of the dumps and used Event Viewer to looks at issues. Nothing seemed to stand out.

One other note: I did notice Warning events indicating access to my Windows Home Server network storage during system start up just before several of the crashes where it indicated links to file blocks failed. Could that be an issue? Note that I have "My Documents" mapped to my WHS, along with a number of programs (such as Outlook) mapped to the WHS. For my next experiment I guess I should try to boot without the WHS connected. However when my system integrator originally replicated the problem at his shop, the WHS was not present.

At this point it seems it has to be software, so it seems I need to rebuild the OS, but before I do that I wanted to get your expert opinion.

All I can say is that it is educational!

Thanks,

Bob

usasma · 31 Oct 2010

Let's get a new look at the system. Please run the data collection app from this link again: https://www.sevenforums.com/crashes-d...tructions.html

Rmiller · 31 Oct 2010

Dear usasma,

Logs attached for prior post...

Bob

zigzag3143 · 31 Oct 2010

Rmiller said:

Dear usasma,

Logs attached for prior post...

Bob

Bob

No DMP file included in upload try this method

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Rmiller · 31 Oct 2010

Dear zigzag,

Here's a re-post of everything along with the attachments.

The minidump directory was oddly empty (viewed as Admin). Yesterday I reviewed the directory and it wasn't empty. Luckily yesterday I had saved off the last minidump (which is attached) because I was reviewing it. It was quite old compared to the issues I've seen before - I guess there was no dump of those more recent problems.

Hopefully this is everything you need. Thanks for all the help,

Bob

********************************

Dear usasma,

Well, I thought I was home free, but it turns out I wasn't. The problem has come back. I have been trying a number of tests to zero in and would like your advice as to what to look at next.

The failure mode is a BSOD or hang, within 1 hour (typ 5 min) of first system start up everyday (except one case). Once the system has crashed, I can restart and run for hours and never see a problem. Based on that and the tests I have done I am getting to the point that I now suspect a driver issue not hardware.

Here are some of the tests I've done:

1) My System integrator replaced the Intel motherboard, CPU (i7 980) and memory (6G) - problem seemed to go away for a few days and now is back
2) Perf95 mem stress test for 3 hours - fine
3) Furmark test of the video card (GeoForce GTX 470) for 1 hour - no problems.
4) System had C: SSD and D: WD raptor HD. In case it was the SD I cloned the SSD to the HD, and for the last 3 days ran C: drive as WD HD - problem still there
5) I disconnected all un-needed HW: SD card reader - that was internally connected to MB, 2 DVD drives (SATA) and SSD (SATA)- still problem. Running off C: WD HD.
6) Uninstalled Avast Anti-virus
7) Did MS driver compatibility - Found .NET 1.1 as incompatible. I haven't found the application SW associated with it. I assume that wouldn't cause a BSOD issue. Need to look into later.

Recent crashes were at:
10/31: 9:08AM 0x9C error BSOD - I thought these errors were only found on Win XP machines - could this be an old driver? Could that be the cause?
10/30: 8:42AM 0x101 BSOD
10/29: 9:25AM Hang
10/28: machine not used
10/27: 8:25AM Hang
10/26: 9:10 AM slow --> hang, BSOD; 10:30PM switch user to Admin and had crash 0x101 BSOD
10/25: 8:50AM 0x124 BSOD

I tried to get a little educated on this and did a WinDbg review of the dumps and used Event Viewer to looks at issues. Nothing seemed to stand out.

One other note: I did notice Warning events indicating access to my Windows Home Server network storage during system start up just before several of the crashes where it indicated links to file blocks failed. Could that be an issue? Note that I have "My Documents" mapped to my WHS, along with a number of programs (such as Outlook) mapped to the WHS. For my next experiment I guess I should try to boot without the WHS connected. However when my system integrator originally replicated the problem at his shop, the WHS was not present.

At this point it seems it has to be software, so it seems I need to rebuild the OS, but before I do that I wanted to get your expert opinion.

All I can say is that it is educational!

Thanks,

Bob

usasma · 31 Oct 2010

The dump file is a STOP 0x101 - and it appears corrupted.
There was also another STOP 0x101 on 28 Oct 2010 (listed in MSINFO32)

STOP 0x9C are the XP equivalent of STOP 0x124 for Vista/Win7
I normally only see it in situations where there's an infection.
Have you scanned with another antivirus in case yours was compromised? Here's links to a few, free, online scanners: Malware

I'd also suggest these free diagnostic tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Please also run the Seagate Seatools as it has a bit more rigorous testing of the controller IMO.

STOP 0x101 troubleshooting: https://www.sevenforums.com/crashes-d...tml#post356791

...What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4