0x124 BSOD

[seekermeister]

While attempting an installation of my mail client yesterday, the system crashed with the titled BSOD. I've included the analysis of the dump and a screenshot of the suspected drivers that it seemed to complain about below.

Since the driver that it pointed at is called a Vista driver, I imagine that it is talking about the Nvidia driver, because the download says that it is for Vista/W7.

This sort of crashed has happened previously, but a bit differently. Before, it always pointed to nvlddmkm.sys, instead of to 0x124, and this time it wouldn't boot to desktop until after running chkdsk /r. It just hung at the login window, which particularly concerns me, because that indicates that it damaged something in the OS.

I've never found a solution for these types of crashes before, but I'm wondering if upgrading the video card would help, or if it is common with all Nvidia video cards?

 

[yowanvista]

It is probably a hardware issue
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html


Your previous crashes with nvlddmkm.sys suggest bad/incorrectly RAM or a faulty GPU

 

[seekermeister]

Thanks, after looking over the possibilities, I have a hunch that the video card is the culprit. Along with the other symptoms, sometimes when running BIOS screens, or using Ctrl-Alt-Del to restart from some BIOS functions, it displays aberrant color patterns on the display. I have been considering upgrading the card anyway, so this just gives another reason to do so.

 

[seekermeister]

I ended up ordering a new video card:

EVGA 768-P3-1362-AR GeForce GTX 460 Superclocked Video Card - 768MB GDDR5, PCI-Express 2.0, Dual DVI, Mini HDMI, SLI, DirectX 11, Fermi, w/ FREE Starcraft II Trial Offer Download at TigerDirect.com

Hopefully, that will cure this BSOD problem. I was wavering, until I tried to boot into Kubuntu, and it lost the video signal before reaching desktop.

 

[yowanvista]

I ended up ordering a new video card:

EVGA 768-P3-1362-AR GeForce GTX 460 Superclocked Video Card - 768MB GDDR5, PCI-Express 2.0, Dual DVI, Mini HDMI, SLI, DirectX 11, Fermi, w/ FREE Starcraft II Trial Offer Download at TigerDirect.com

Hopefully, that will cure this BSOD problem. I was wavering, until I tried to boot into Kubuntu, and it lost the video signal before reaching desktop.

Did you test your RAM?

 

[seekermeister]

Yes, it appears good.

 

[seekermeister]

I got another 0x124 last night, so apparently the video card isn't the problem. Since the ram tested good also, what does that leave?

 

[Jonathan_King]

Could you run our BSOD sticky?

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

I have a suspicion, but I'd like to check out some event logs and other info before saying.

 

[seekermeister]

Will these do?

EDIT: I don't know that it is relevant, but the last two of these BSODs occurred during the installation of 2 different programs.

 

[Jonathan_King]

I was hoping to get the Windows_NT6_BSOD folder, actually. See here: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[seekermeister]

I'm having a problem with both of those diagnostics. Perfmon seems to run okay, but then reports that there was an error creating the report. The other one runs through all of the diagnostics, and creates the folder mentioned, but when I used 7Zip and tried to upload it, the wizard said that it was an invalid file. I then tried using my other zipper...PowerArchiver, but when I browse it to the folder, it doesn't see anything in it. I'm lost.

 

[Jonathan_King]

Try just right-clicking on the Windows_NT6_BSOD_jcgriff2 folder, and selecting Send to > New compressed folder.

 

[seekermeister]

Okay got it:

 

[Jonathan_King]

Thanks, that's good.

I must suspect either a bad CPU, or bad motherboard.

Did you ever do any overclocking on this system?

I recommend Prime95 to stress the CPU, motherboard, and RAM. Try all 3 tests, not just Large FFTs: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

The fact that so many errors point to your graphics drivers points to a bad graphics card, but since you replaced it, it may be the board.

I ran the latest 15 dumps.

...Summary of the dumps

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 20:56:00.595 2010 (UTC - 4:00)
System Uptime: 1 days 0:13:32.923
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 20:55:57.032 2010 (UTC - 4:00)
System Uptime: 0 days 10:06:35.282
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 25 11:50:14.017 2010 (UTC - 4:00)
System Uptime: 0 days 1:18:05.283
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 02:32:05.607 2010 (UTC - 4:00)
System Uptime: 1 days 13:29:55.857
*** 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+1f063b )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1f063b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 09:54:26.595 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:30.861
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 02:01:05.016 2010 (UTC - 4:00)
System Uptime: 1 days 9:00:29.266
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 07:33:23.613 2010 (UTC - 4:00)
System Uptime: 0 days 6:56:07.863
*** 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+17ea65 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+17ea65
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 16:56:49.950 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:37.200
*** WARNING: Unable to verify timestamp for vsmraid.sys
*** ERROR: Module load completed but symbols could not be loaded for vsmraid.sys
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : vsmraid.sys ( vsmraid+d6fd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_vsmraid+d6fd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 29 17:46:32.884 2010 (UTC - 4:00)
System Uptime: 1 days 14:47:59.150
*** 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+119cf8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 16:30:44.152 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:35.417
*** 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+1f063b )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1f063b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 20:37:33.654 2010 (UTC - 4:00)
System Uptime: 2 days 21:28:45.904
Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1397 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  speedfan.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1397
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 20 23:04:01.269 2010 (UTC - 4:00)
System Uptime: 4 days 7:42:02.535
Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1397 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  speedfan.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1397
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 05:10:14.519 2010 (UTC - 4:00)
System Uptime: 1 days 2:56:13.785
Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1397 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  speedfan.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!_??_::FNODOBFM::_string_+1397
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[seekermeister]

This probably doesn't measure up to what you recommended, but I ran HotCPU Lite last night, and it didn't squawk anything:

 

[yowanvista]

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

 

[seekermeister]

A request was made for some of the original dumps, so here they are"

 

[zigzag3143]

A request was made for some of the original dumps, so here they are"

Doing them now

Back in 15 mins

Most are hardware related.

1-sptd.sys (used by daemon tools/alcohol120) yours 2005 MUST be removed.

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-....OLD drivers, even your raid driver is one plus years old

AmdTools64.sys        fffff880`017ff000    0x00015000    6/27/2006 15:24:21            0x44a185e5    fffff880`017ea000                              
speedfan.sys        fffff880`01df1000    0x00007000    9/24/2006 09:26:48            0x45168798    fffff880`01dea000                
regi.sys        fffff880`03917000    0x00008000    4/16/2007 11:19:10            0x462393ee    fffff880`0390f000                
Si3132r5.sys        fffff880`0110e000    0x00055000    6/1/2007 13:08:28            0x4660528c    fffff880`010b9000                
SiWinAcc.sys        fffff880`011f9000    0x00009000    6/14/2007 20:02:02            0x4671d6fa    fffff880`011f0000                
SiRemFil.sys        fffff880`01c4c000    0x00008000    6/20/2007 15:42:10            0x46798312    fffff880`01c44000                
nvstor64.sys        fffff880`01179000    0x00022000    8/9/2007 14:11:52            0x46bb58e8    fffff880`01157000                
dump_nvstor64.sys        fffff880`06dd1000    0x00022000    8/9/2007 14:11:52            0x46bb58e8    fffff880`06daf000                
SI3132.sys        fffff880`01157000    0x0001a000    10/3/2007 14:39:29            0x4703e1e1    fffff880`0113d000                
zl88avs64.sys        fffff880`0526ff00    0x0006ff00    11/27/2007 01:23:44            0x474ba9e0    fffff880`05200000                
nvmfdx64.sys        fffff880`057f9180    0x0016c180    8/1/2008 14:38:28            0x48935824    fffff880`0568d000                
000.fcl        fffff880`07d6f000    0x0002b000    9/26/2008 09:11:22            0x48dcdf7a    fffff880`07d44000                
PROCEXP113.SYS        fffff880`07c39000    0x00008000    11/3/2008 17:19:45            0x490f6af1    fffff880`07c31000                
UltraMonUtility.sys        fffff880`07d44000    0x00009000    11/13/2008 21:10:30            0x491cd006    fffff880`07d3b000                
vsmraid.sys        fffff880`00e54000    0x0002a000    1/30/2009 21:18:57            0x4983a701    fffff880`00e2a000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

 

[seekermeister]

Okay, so far I have updated the ATK0110 driver, and the status of the rest is below:

AmdTools64.sys I have tried a couple of times and I have been unable to access the AMD download for this CPU.

speedfan.sys Updated to 4.42

regi.sys Appears to be for some program from Intervideo, but I have nothing of theirs installed

SI3132.sys I assume that this and the 3 items below are all related to the SI3132 driver that I just updated.
Si3132r5.sys
SiWinAcc.sys
SiRemFil.sys

nvstor64.sys These are related to the nForce4 driver, but nForce4 is no longer supported, and there is nothing newer
nvmfdx64.sys
dump_nvstor64.sys

zl88avs64.sys I'm confused as to where this one comes from, because what I have Googled it appears to be either from my TV card, Nvidia graphics driver or ?

000.fcl This appears to come from PowerDVD 8, but I do not intend to pay for an upgrade.

PROCEXP113.SYS Installed the latest version

UltraMonUtility.sys Installed the latest version

vsmraid.sys I do not need this driver at all, because I uninstalled that controller card, but have been unable to uninstall the driver, whether with or without the card installed.