Solved BSOD ntoskrnl.exe+7f1c0 after NVIDIA Driver update

[Porcupine162]

Hi there,

I recently updated my NVIDIA Drivers for my GTX 570 from 296.10 to 306.23 and immediately received a BSOD when trying to start up Skyrim. Since I did a clean install I had no drivers to rollback to so I decided to install the 301.42 drivers which worked fairly well... for about an hour.

I am now receiving BSODs every 1-3 hours from anything such as writing in a word document, browsing facebook, playing a game or looking at a vimeo video.
I am running dual monitors (one 60hz and the primary 120hz) with Displayfusion, currently have disabled aero and the extended toolbar. This was working fine before I updated my drivers.

I have ran a memtest with all positive results, and I am running Driver Verifier with all non Microsoft drivers checked. The latest crash was with Verifier running and while attempting to load a vimeo page.

The obvious answer would be to rollback to the 296.10 NVIDIA drivers, however I have a feeling there might be something else amiss. I thought I might come here first before any more potential frustration, and to stamp out any further issues.

I have attached the auto-compiled folder and a spec list. Please let me know if there is any more information you would like me to provide. Any help is appreciated

 

[Arc]

Welcome aboard.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005d30028, be200000, 5110a}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware

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

Follow the guide http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696, step by step!

 

[Porcupine162]

Thanks Arc,

I ran through the guide a bit, currently in the process of updating motherboard drivers (including drivers which don't have a device connected etc)
I downgraded to my old 296.10 NVIDIA driver and still received the BSOD. Am now running the latest.

My machine is definitely cooled, nothing is overclocked, ran stress tests on all except HDD yet, will do ASAP.

Am about to update BIOS soon if I can.

I have attached the last 5 BSODs in a zip.

EDIT: Updated all drivers I could find. Still BSOD in the morning when I went on redtube . Left for work with a CHKDSK /r running.
Still haven't updated BIOS. Realised I had OC Genie enabled on motherboard. Will disable when I get home, and if the BSOD still occurs I will attempt a BIOS update.

I am probably going to end up buying a new CPU/Motherboard if the issue proves too difficult, although I would love to avoid it. My motherboard was one of the recalled Sandybridges with the SATA port degrading... If that was causing the issue I am surprised that it only appeared after a driver update.

 

[Arc]

OK, checked those chronologically, starting from the latest.

1. C-Media Audio Interface Driver, which is of March, 2011.
2. Stop 124, caused by hardware.
3. Stop 124, caused by hardware, again.
4. Stop 124, caused by hardware, again.
5. Stop 124, caused by hardware, again.

You may upate your audio driver, probably the update site is C-Media Electronics, Inc..



But, as far as there is the hardware problem, you will continue to receive crashes. Follow the steps I told you to follow. If all tried, go to step 9 and locate the problem hardware out, replace it.

 

[Porcupine162]

Thanks for the reply!

C-Media Audio Interface Driver? Should I know what that is? Never heard of C-Media before. My soundcard is Asus Xonar Essence ST, and onboard is Realtek HD. As far as I know that shouldn't be on my system.

I did go home on my lunch hour and updated my BIOS - still had BSOD when loading a game. Went and turned off OC Genie (a physical button on the motherboard) and was able to load my Skyrim character, Dark Souls character, play youtube videos etc WHILE Driver Verifier was running with no BSOD. Will test further tonight but it looks promising. *fingers crossed*

 

[Arc]

Well, actually it is cmudaxp.sys. Developed by C-Media.
It is used by ASUS Xonar audio interface and HTO CLARO Audio Interface, too.

If you are using ASUS, you may search the updates in ASUSTeK Computer Inc. -Support- Drivers and Download.

 

[Porcupine162]

I definitely have the latest driver for my sound card as I updated it in the morning. The latest driver was released 2011.06.27 so it may be correct after all.

 

[Arc]

Well ... you are using the computer, you know it better, much better. I just have access to the info supplied by you, and say based on those info only.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {62, fffffa80060f3fe8, fffffa80060f5f00, 25}

*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : cmudaxp.sys[/COLOR]

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

 

[Porcupine162]

Interesting. I will double check when I get home. I remember getting a bluescreen right as I was updating the driver for my soundcard, so that would explain the version and the driver being pointed at as the culprit.

I will update this post in 4 hours with my results.

EDIT: YES. That fixed it. Thankyou Arc.