Solved BSOD and BCCode 124

[rebelagentm]

When I leave desktop computer on for an extended period of time (say overnight), I find that when I come back to it, it has turned off or rebooted. Sometimes I get a BSOD and other times I get a message saying that Windows did not shut down properly.

There shouldn't be anything going on with the system during these times other than a scheduled nightly backup to an external hard drive. I am using SyncToy for this.

I have done memory and hard disk checks and there were no problems or errors reported.

Attached is the requested files as per the BSOD posting instructions. If anyone can look at these and help me figure out what is going on, it would be greatly appreciated!

If any other info is needed, just let me know.

Thanks!

 

[rebelagentm]

So sorry! I left out some info:

-Windows 7 Professional 64-bit
-Original OS installed on system was Windows 7 Home Premium 64-bit. Upgraded through "Anytime Upgrade" option to Professional
-Retail version of Windows
-System is just under two months old
-Original OS installed just under two months ago. Upgrade to Pro done approximately one month ago.

 

[ttran]

The stop code is 124, which is hardware related, please read this article to know what it means and what to try:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

BUGCHECK SUMMARY:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI05.134\061610-21543-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
Debug session time: Thu Jun 17 07:38:13.939 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:10.079
Loading Kernel Symbols
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800b9e4748, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

There is one stop code that is related to video card, it is 116, and your video card driver was blamed. I would suggest to download and install fresh copy of driver, then follow this instruction for further support:
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI05.542\060710-20389-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
Debug session time: Tue Jun  8 10:51:38.683 2010 (UTC + 7:00)
System Uptime: 0 days 2:28:16.823
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800ca72070, fffff8800ff5cd50, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+11bd50 )

Followup: MachineOwner
---------

 

[rebelagentm]

I have tried Steps 1-6 in the mentioned article. Before I proceed to Step 7 (re-installing Windows), I wanted to collect some opinions and see if there was any way to pinpoint the issue.

I believe that the Stop Code 116 error has been resolved already and I did that by following the same suggestion you mentioned. My recent BSOD problems are the two most recent Minidump files in that zip.

Thanks!

 

[zigzag3143]

When I leave desktop computer on for an extended period of time (say overnight), I find that when I come back to it, it has turned off or rebooted. Sometimes I get a BSOD and other times I get a message saying that Windows did not shut down properly.

There shouldn't be anything going on with the system during these times other than a scheduled nightly backup to an external hard drive. I am using SyncToy for this.

I have done memory and hard disk checks and there were no problems or errors reported.

Attached is the requested files as per the BSOD posting instructions. If anyone can look at these and help me figure out what is going on, it would be greatly appreciated!

If any other info is needed, just let me know.

Thanks!

These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.

http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

The three specific devices listed below are you yukon ethernet controller, your video driver and a generic hardware failure.

Thanks


Ken

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  9 10:10:24.080 2010 (GMT-4)
System Uptime: 0 days 0:00:10.219
BugCheck 124, {0, fffffa800baf1038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 23:51:38.683 2010 (GMT-4)
System Uptime: 0 days 2:28:16.823
BugCheck 116, {fffffa800ca72070, fffff8800ff5cd50, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+11bd50 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 10:05:55.773 2010 (GMT-4)
System Uptime: 0 days 21:24:55.913
BugCheck 9F, {3, fffffa800ab14a20, fffff8000408f518, fffffa800d5b1300}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

 

[rebelagentm]

I believe the errors related to the Yukon Ethernet Controller and the video card have been resolved for a while now. I stopped receiving those errors after enabling IPv6 in Zone Alarm and uninstalling and reinstalling the video card driver respectively.

The recent problems that prompted this post are the 124 errors. A gentleman over at Microsoft Answers suggested that one of the recent dump files implicated my processor as needing to be replaced. I was looking for some additional opinions though before taking hardware out of my system or attempting a re-install of Windows.

I know 124 errors are not easy to pinpoint (since it could be the physical hardware, a driver, the OS, or other software).

As I mentioned earlier, I have already performed Steps 1-6 in the article mentioned. Should I go forward with a clean install of Windows?

Any other analysis or ideas anyone?

Thanks!

 

[rebelagentm]

Any other thoughts?

A user on another forum is insisting that, based on my minidump files, that this is a CPU and/or motherboard problem and that re-installing Windows will not do any good.

I want to know what the best course of action would be. Should I try the re-install and one-by-one try adding programs? Since these BSODs only occur every other day or so, it would take months to do a one at a time approach of re-installing the OS and programs to see if they cause an issue.

On the other hand, Intel says that I need to remove the processor and try it out in a different system to see if the same issue occurs. They say that this is necessary to avoid wasting time and money because they will not give me an exchange if they test the proc and it turns out to be O.K.

Unfortunately, I don't have another system to test on, which means I would probably have to pay some computer shop to do the work.

Basically, I don't have tons of time and money to be working on this, but I need this computer for day-to-day work.

I know its probably time consuming, but if there is someone out there that has the time, it would be greatly appreciated if someone could assist me in pinpointing the exact cause of these problems.

Thanks!

 

[rebelagentm]

Anyone?

 

[Jonathan_King]

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

 

[rebelagentm]

Thanks! I'm guessing the thought is that the built-in Windows memory test tool is not sufficient enough?

 

[Jonathan_King]

Nope, it misses stuff all the time.

Use Memtest86 instead. Here is a direct link: http://memtest.org/download/4.10/memtest86+-4.10.iso.zip

 

[rebelagentm]

I ran MemTest86+ overnight. It made it through five full passes without any errors and was about 81% complete on a sixth run without any errors thus far.

So, I'm guessing memory is not to blame here. Suggestions for what to do next?

 

[Jonathan_King]

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/free/support/cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[cluberti]

According to Intel, this is a Core i7 - either a 930 or a 975. If it's a 975, it is supposed to be a 3.3GHz part, but you're showing a 2.8GHz part. If it's not an i7 930, this could be a problem, so I thought I'd point it out:

4: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 4  6,26,5 GenuineIntel 2806 0000000f00000000                   211b3ffe

As to the WHEA failures, it looks like it is indeed complaining of a memory *access* issue with processors 0 and 2 failing an internal timer watchdog timeout when accessing bank 5 (all 3 124's you uploaded are a failure accessing bank 5):

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800ba88148
Section       @ fffffa800ba882d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x000038801000fb6e
  Misc.       : 0x0000000000007fff

So, either the CPU is damaged, or you have a bad stick of memory.

 

[rebelagentm]

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/free/support/cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Jonathan,

Why do you suggest removing Zone Alarm? I have heard of Windows 7/Zone Alarm issues before. If this is related to the Yukon Ethernet Controller, enabling IPv6 support in Zone Alarm seems to have fixed this.

 

[rebelagentm]

According to Intel, this is a Core i7 - either a 930 or a 975. If it's a 975, it is supposed to be a 3.3GHz part, but you're showing a 2.8GHz part. If it's not an i7 930, this could be a problem, so I thought I'd point it out:

4: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 4  6,26,5 GenuineIntel 2806 0000000f00000000                   211b3ffe

As to the WHEA failures, it looks like it is indeed complaining of a memory *access* issue with processors 0 and 2 failing an internal timer watchdog timeout when accessing bank 5 (all 3 124's you uploaded are a failure accessing bank 5):

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800ba88148
Section       @ fffffa800ba882d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x000038801000fb6e
  Misc.       : 0x0000000000007fff

So, either the CPU is damaged, or you have a bad stick of memory.

My proc is an i7 930. I ran MemTest overnight and it did not report any errors, so I'm guessing the memory is not an issue.

If the CPU is indeed bad, would running Prime95 expose this? And, would that be responsible for the video card errors?

 

[rebelagentm]

Also, I ran FurMark and it didn't take long before my entire screen distorted. Probably less than one minute. I had to force the PC off because I couldn't see the "Quit" button on the app.

The temp got up around 75 degrees Celcius before it distorted.

According to SpeedFan, my GPU sits around 49 degrees.

Is this normal? If all GPUs will eventually max out with this program, how does this tell you whether your graphics card is bad?

 

[CarlTR6]

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/free/support/cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Jonathan,

Why do you suggest removing Zone Alarm? I have heard of Windows 7/Zone Alarm issues before. If this is related to the Yukon Ethernet Controller, enabling IPv6 support in Zone Alarm seems to have fixed this.

Zone Alarm is a known cause of BSOD on a lot of Win 7 systems. When troubleshooting crashes, you want to eliminate every possible known cause of crashes.

 

[cluberti]

Also, I ran FurMark and it didn't take long before my entire screen distorted. Probably less than one minute. I had to force the PC off because I couldn't see the "Quit" button on the app.

The temp got up around 75 degrees Celcius before it distorted.

According to SpeedFan, my GPU sits around 49 degrees.

Is this normal? If all GPUs will eventually max out with this program, how does this tell you whether your graphics card is bad?

No, I wouldn't think that's normal. 75C is around the thermal ceiling for the Intel CPU as well, in fact it's a few degrees above it (Core i5/i7 have a thermal ceiling of ~72C). The GPU is warm too, although I'm not sure that's anywhere near a ceiling for that part. Given the behavior though, I would suspect the GPU right now.

 

[Jonathan_King]

I would purchase a new GFX card, honestly.