Solved BSOD randon crashes.

[mcco]

Hi

My pc randomly crashes to the BSOD. It can happen after 5 minutes sometimes I can use if for hours/days without crashes and I cannot seem to locate the problem.

It will happen at random, browsing the web, watching video files, playing mp3 files. It also happens when playing Microsoft Flight Sim X and Skyrim.

I have attached the log so see if you guys can help me

Thanks in advance

Michael

 

[FredeGail]

Hello Michael and welcome to Sevenforums.

BSOD Analyse

Dumps are caused by cmudaxp.sys, which is a part of the ASUS Media legacy. Are you somehow able to recognize this driver, and does it list in Control Panel?

Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 0n2
*** 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
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 0n2
*** 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
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 0n2
*** 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
Probably caused by : hardware

Additional information

The NFO was corrupted and not complete. Try this method-

• A nfo file

  • To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Best Regards,
Frederik.

 

[mcco]

Hi Frederik

cmudaxp.sys is part of the Asus Xonar Audio driver which is my sound card. I have checked and I am using the latest driver.

I am also using a USB headset pluged into the front usb port could that be causing a conflict?

I have attached an new version of msinfo32 as requested. It says it is corrupted however the file opens ok

Many Thanks again

Michael

 

[FredeGail]

Hi Frederik

cmudaxp.sys is part of the Asus Xonar Audio driver which is my sound card. I have checked and I am using the latest driver.

Is it like a driver itself? If yes, are you able to uninstall it for the moment? It should run with no problem as Windows 7 has a driver for it as far as I'm concerned.

I am also using a USB headset pluged into the front usb port could that be causing a conflict?

No problem at all.

Thank you,
Frederik.

 

[mcco]

I have uninstalled the driver, reset the pc and now windows has detected the sound card. It has installed an earlier version of the same driver.

Thanks

Michael

 

[FredeGail]

Exactly as it should, great!

Best Regards,
Frederik.

 

[mcco]

Hi

Well the pc crashed again, back to the BOSD this afternoon. I was watching a video on the BBC new website.

Any ideas?

Thanks in advance

Michael

 

[FredeGail]

Hello Michael.

I've come to a conclusion that the ASUS crashes are fixed. Though, something else might be bothering and interrupting your system. Can you upload the newest 1-2 dumps?

Best Regards,
Frederik.

 

[mcco]

Hi Frederik

As requested. Thanks for your help with this

Michael

 

[mcco]

Hi

I have tried to have a go at fixing the problems myself without much luck.

The latest BSOD was as follows:

Mini Kernel Dump does not have process information
Symbol search path is: SRV*C:\Symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Unable to load image Unknown_Module_6e33dffe`08a7bcd6, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_6e33dffe`08a7bcd6
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_6e33dffe`08a7bcd6
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0ec1e000 PsLoadedModuleList = 0xfffff800`0ee62670
Debug session time: Sun Sep  2 21:01:14.797 2012 (UTC + 1:00)
System Uptime: 0 days 1:28:39.000
Unable to load image Unknown_Module_6e33dffe`08a7bcd6, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_6e33dffe`08a7bcd6
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_6e33dffe`08a7bcd6
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80092a0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0334aa58 fffff800`0f218a3b : 00000000`00000124 00000000`00000000 fffffa80`092a0028 00000000`be200000 : 0xfffff800`0ec9d1c0
fffff880`0334aa60 00000000`00000124 : 00000000`00000000 fffffa80`092a0028 00000000`be200000 00000000`0005110a : 0xfffff800`0f218a3b
fffff880`0334aa68 00000000`00000000 : fffffa80`092a0028 00000000`be200000 00000000`0005110a fffffa80`08eadbd0 : 0x124


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Any ideas?

Thanks as always for any help

 

[FredeGail]

Hello mate and sorry for the late reply.

Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
:info: Be sure to check your warranty rules and regulations before opening your case.

* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.​

​

Best Regards,
Frederik.

 

[mcco]

Hi Frederik

I will give this a go this evening.

One quick question, my pc was stable from Monday until Sunday afternoon. During that time my usb headset was unplugged and I had zero BSOD. It seems strange that after I plugged the headset in, I had 3 crashes inside a number of hours. Could it be causing conflicts with my sound card/system. I haven't installed any drivers for it, I let windows choose the best one.

I will update you later on the memory stick tests.

Thanks as always

Michael

 

[FredeGail]

Interesting. Seems like it's a device based crash you've experienced then. Leave it unplugged for a while and see what happens -- unless you have another driver as you said.

Great news so far,
Frederik.

 

[mcco]

So far so good with the memory tests. One stick of 4GB Kingston ram checked in all slots. 2 runs in each slot with no errors. I'll check the other stick tomorrow

Thanks again for your help

Michael

 

[FredeGail]

Good job Michael.

Best Regards,
Frederik.

 

[mcco]

Quick update, I have completed testing the other ram stick in all slots, no errors. Ran 2 tests in each slot. I will leave the headset unplugged, its just a generic one, windows had assigned a pnp audio drive for it.

Regards
Michael

 

[FredeGail]

Good job, let's see how it turns out.

Best Regards,
Frederik.

 

[mcco]

Not good I am afraid. Got another BSOD tonight. The USB headset was unplugged so I guess I can rule that theory out.

Below is the crash info.

Unable to load image Unknown_Module_602cd182`eaa3f27c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_602cd182`eaa3f27c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_602cd182`eaa3f27c
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0ec0a000 PsLoadedModuleList = 0xfffff800`0ee4e670
Debug session time: Wed Sep 5 19:31:31.863 2012 (UTC + 1:00)
System Uptime: 0 days 2:31:30.189
Unable to load image Unknown_Module_602cd182`eaa3f27c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_602cd182`eaa3f27c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_602cd182`eaa3f27c
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80092b5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`009c8a58 fffff800`0f204a3b : 00000000`00000124 00000000`00000000 fffffa80`092b5028 00000000`be200000 : 0xfffff800`0ec891c0
fffff880`009c8a60 00000000`00000124 : 00000000`00000000 fffffa80`092b5028 00000000`be200000 00000000`0005110a : 0xfffff800`0f204a3b
fffff880`009c8a68 00000000`00000000 : fffffa80`092b5028 00000000`be200000 00000000`0005110a fffffa80`092c08b0 : 0x124


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

Any ideas?

Thanks

Michael

 

[FredeGail]

Go to Device Manager, see if you can find your headset listed somewhere. Right-click it, Properties, Driver tab - Uninstall Driver. OK out, Right-click it once more if it's still there, Uninstall Device.

 

[mcco]

Hi Frederik

I will have a look and see if they are listed.

Thanks again

Regards

Michael