Random BSOD when Waking Up

[JungleCurry]

Hi

Please could someone help as I have tried everything I thought would solve the problem but my computer still crashes randomly? Here's the information.

MB: Gigabyte Z97X-UD3H
CPU: i7 4790K (non-OC)
RAM: 16GB
Graphics: Sapphire R7 250 Ultimate Fanless
Sound Card: Asus Xonar DX
PSU: FSP Aurum AU-500FL Xilenser 500W
Samsung 840 Pro 128GB
Seagate ST4000DM000 SATA 4TB

My PC runs fine for normal use but when I wake it up from sleep it occasionally crashes showing BSOD. Any advice is most welcome. Thank you.

JungleCurry

 

[Arc]

Hi JungleCurry.

Uninstall the driver to ASUS Xonar DX and install Version 7.0.8.1821 from ASUSTeK Computer Inc. -Support- Drivers and Download Xonar DX

Also Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the result.
__________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88003db5d91}

*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : cmudaxp.sys ( cmudaxp+2f7d91 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003db5d91, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ca100
GetUlongFromAddress: unable to read from fffff800038ca1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
cmudaxp+2f7d91
fffff880`03db5d91 488b01          mov     rax,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  AirVideoServer

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF8000400DFB0

TRAP_FRAME:  fffff8000400d560 -- (.trap 0xfffff8000400d560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003db5d91 rsp=fffff8000400d6f0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000001cfaff8 r10=fffff8000361d000
r11=fffff8000400d7e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cmudaxp+0x2f7d91:
fffff880`03db5d91 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003692169 to fffff80003692bc0

STACK_TEXT:  
fffff800`0400d418 fffff800`03692169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0400d420 fffff800`03690de0 : fffff800`0400d830 00000000`00000000 fffff800`0400d600 fffffa80`0dd4e900 : nt!KiBugCheckDispatch+0x69
fffff800`0400d560 fffff880`03db5d91 : 00000000`00000000 fffffa80`0de20f70 00000000`00000180 00000000`00000000 : nt!KiPageFault+0x260
fffff800`0400d6f0 00000000`00000000 : fffffa80`0de20f70 00000000`00000180 00000000`00000000 fffffa80`0de20e50 : cmudaxp+0x2f7d91


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cmudaxp+2f7d91
fffff880`03db5d91 488b01          mov     rax,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cmudaxp+2f7d91

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmudaxp

IMAGE_NAME:  cmudaxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51ec89b4

FAILURE_BUCKET_ID:  X64_0xD1_cmudaxp+2f7d91

BUCKET_ID:  X64_0xD1_cmudaxp+2f7d91

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_cmudaxp+2f7d91

FAILURE_ID_HASH:  {a3a29dfc-eac6-6a08-0369-bcbf00df8243}

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

0: kd> lmvm cmudaxp
start             end                 module name
fffff880`03abe000 fffff880`03dec000   cmudaxp  T (no symbols)           
    Loaded symbol image file: cmudaxp.sys
    Image path: \SystemRoot\system32\drivers\cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp:        Mon Jul 22 06:54:04 2013 (51EC89B4)
    CheckSum:         002A3BAA
    ImageSize:        0032E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[JungleCurry]

Hi Arc

I have uninstalled the old Xonar DX driver and installed a newer version. The system have been stable for the past 48 hours. Thank you for your help.

Best wishes
JungleCurry

 

[JungleCurry]

I spoke too soon! My PC just crashed again. It happened when I watched a video on XBMC. Please see attached for a new log file.

JungleCurry

 

[Arc]

Now it is different one.

Uninstall the display driver using DDU. Then install it again. See how it goes.
(Because it may be caused by an improper installation of the display driver. I guess you updated the driver directly).
_________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800f16ae53, fffff88008a39750, 0}

Probably caused by : atikmdag.sys ( atikmdag+99e53 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800f16ae53, Address of the instruction which caused the bugcheck
Arg3: fffff88008a39750, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
atikmdag+99e53
fffff880`0f16ae53 48395810        cmp     qword ptr [rax+10h],rbx

CONTEXT:  fffff88008a39750 -- (.cxr 0xfffff88008a39750;r)
rax=0000000000000001 rbx=fffffa8000000000 rcx=38f3591c51f40000
rdx=000000000000008f rsi=0000000000000002 rdi=fffffa800d910894
rip=fffff8800f16ae53 rsp=fffff88008a3a130 rbp=0000000000000000
 r8=000000000000004e  r9=0000000000000000 r10=0000000000000000
r11=fffff88008a3a070 r12=fffff8800f2d8768 r13=0000000000000010
r14=fffff88008a3a950 r15=fffff8800f2d8518
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x99e53:
fffff880`0f16ae53 48395810        cmp     qword ptr [rax+10h],rbx ds:002b:00000000`00000011=????????????????
Last set context:
rax=0000000000000001 rbx=fffffa8000000000 rcx=38f3591c51f40000
rdx=000000000000008f rsi=0000000000000002 rdi=fffffa800d910894
rip=fffff8800f16ae53 rsp=fffff88008a3a130 rbp=0000000000000000
 r8=000000000000004e  r9=0000000000000000 r10=0000000000000000
r11=fffff88008a3a070 r12=fffff8800f2d8768 r13=0000000000000010
r14=fffff88008a3a950 r15=fffff8800f2d8518
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x99e53:
fffff880`0f16ae53 48395810        cmp     qword ptr [rax+10h],rbx ds:002b:00000000`00000011=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f16ae53

STACK_TEXT:  
fffff880`08a3a130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x99e53


FOLLOWUP_IP: 
atikmdag+99e53
fffff880`0f16ae53 48395810        cmp     qword ptr [rax+10h],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+99e53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c

STACK_COMMAND:  .cxr 0xfffff88008a39750 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+99e53

BUCKET_ID:  X64_0x3B_atikmdag+99e53

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_atikmdag+99e53

FAILURE_ID_HASH:  {206680b8-57f0-a1ea-2da9-767bbc84f557}

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

1: kd> lmvm atikmdag
start             end                 module name
fffff880`0f0d1000 fffff880`0ffe1000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
    CheckSum:         00EAEEE6
    ImageSize:        00F10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[JungleCurry]

Thank you. I have done what you suggested. I will report back after a couple of days.

JC

 

[JungleCurry]

Hello

After a couple of days with no problem, the BSOD returned again this morning. It crashed right after waking up after it was in the sleep mode for about 2 hours. Please see attached.

This problem started to annoy me as my PC is only about a month old. With my old computer, running XP, I had no problem using it for 5-6 years. If anyone could shed light on the issue, it would be much appreciated.

JC

 

[Arc]

Different bugchecks are appearing!

Now its a time to think alternatively.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there. Let us know the result.
____________________________________

BugCheck 4E, {99, 3bd009, 0, 3bd089}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

 

[JungleCurry]

Thank you for your reply. I will let you know the results of the memory test.

By the way, I have just disabled C3 and C6/C7 states in the BIOS as there are reports that these power saving features cause BSOD for systems with Haswell chips. I am not sure if this is the cause of my problem but at this stage I will try anything!

JC

 

[Layback Bear]

This information should be a nice read about C state.
I never use C states but then I never use Sleep either.

Everything You Need to Know About the CPU C-States Power Saving Modes | Hardware Secrets

 

[essenbe]

What Power Supply do you have? Some power supplies cause BSODs with Haswell because they are not Haswell certified. Haswell uses less power than the supplies can go. Some have a limit of "if it goes lower than this, shut off".

The easiest way is to set the hard drive to never sleep, that's what I do. With an SSD, sleep is not really that necessary. It takes you what, about 25 seconds to start up? Plus it loads all your drivers again. There are a lot of options in advanced power settings that you can control it the way you want it. If you want to try that I can tell you how.

 

[JungleCurry]

Hi essenbe

My PSU is Aurum Xilenser 500 (AURUM XILENSER 500 (Modular) | AURUM Xilenser Series | Power Supply | FSPLifeStyle). The website states that the unit is Haswell compatible.

I actually thought about not putting the system into sleep but shut it down completely when not in use. However, I prefer the sleep mode because I sometimes leave several documents opened and so with sleep I can get back to work right away when the system wakes up.

If push comes to shove, I might have to do what you suggest. However, I would like to see if I can get to the bottom of the issue before giving up!

JC

 

[essenbe]

OK, no problem. I have an Ivy Bridge so can't help a lot with Haswell. But, if I can provide any info, please just ask. BTW, have you tried turning off hybrid sleep mode?

 

[JungleCurry]

OK, no problem. I have an Ivy Bridge so can't help a lot with Haswell. But, if I can provide any info, please just ask. BTW, have you tried turning off hybrid sleep mode?

It seems like Hybrid Sleep is off on my system. However, using "powercfg -a" in the command prompt, I got the following messages.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>powercfg -a
The following sleep states are available on this system: Standby ( S3 )
The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.
Standby (S2)
The system firmware does not support this standby state.
Hibernate
Hibernation has not been enabled.
Hybrid Sleep
C:\Windows\system32>

I was wondering if sleep states S1 and S2 had anything to do with my BSOD problem?

JC

 

[essenbe]

I have S1 enabled on my system and all the other sleep states disabled. I had just read of someone with the same/similar board as you having the same problem. He said he turned off hybrid sleep and it solved his problem. I just thought I'd pass that on.

This is an overclocking guide for the Gigabyte Z97 boards. The guides and the posts that follow usually give a pretty good explanation of the different settings. You may want to look and see if there is a setting that causes the same problems you are having. http://www.overclock.net/t/1490835/the-gigabyte-z97x-overclocking-guide

 

[JungleCurry]

Different bugchecks are appearing!

Now its a time to think alternatively.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there. Let us know the result.
____________________________________

BugCheck 4E, {99, 3bd009, 0, 3bd089}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

Follow-up report:

After 8 passes of memtest, no errors were reported.

I disabled C3 state in BIOS yesterday. Today the machine fell to wake up from sleep. It just showed a black screen. To get it running again, I had to do hard reboot. I then disabled C1E state and so far no issue.

I now think that the BSOD problem and the failure to wake up issue are related. After looking around, I found that the issue is common with Gigabyte motherboards.

If anyone with similar experience with Gigabyte boards managed to solve the issue, please share.

 

[Arc]

I now think that the BSOD problem and the failure to wake up issue are related. After looking around, I found that the issue is common with Gigabyte motherboards.

BSOD issues cannot be generalized in that way. Every single issue is different; and unique depending on the system (software-hardware-settings) environment.

For any further BSOD, let us see the data.

 

[art vandelay]

JungleCurry - did you get anywhere with this?

I have a very similar issue and notice also have Gigabyte Z87 board and same Seagate 4TB drive.

Thanks.

 

[JungleCurry]

Unfortunately not. After weeks of headache, I abandoned the idea of putting my PC to sleep. I believe that the combination of PSU, Gigabyte MB and 4790K chip is the culprit.

 

[art vandelay]

Thanks. I've updated to the latest Intel RST and haven't had a crash waking from sleep yet ...

But it is random. Had a week without any problems up until Saturday. Did have a couple of devices charging on fron USB 3 ports - always suspicious of USB 3 since have seen many issues with USB 3 and sleep early on.

This a clean reinstall Win 8.1 Pro, RAM, SSD and HDD all tested extensively. RAM even swapped out. Gigabyte Z87-HD3. Some reports than ON/OFF should be uninstalled so try that too. Antec 650W Truepower, GTX 970, 16GB Crucial Ballistix, Intel 4770 - just as information for others.

I do need to try another wireless mouse / keyboard combo (Microsoft Desktop 700 v2) - although have disabled them for waking up machine.

Driver verifier gives no useful info and won't crash unless use very aggressive settings.

I'm in computer repair and this issue has me stumped. Hopefully this IRST update will sort but I'm not hugely confident.