Random BSOD, error 0x0000004e

abstractthought · 04 May 2014

Been having this problem for several weeks now. Computer will be running fine and then suddenly BSOD. Seems like its a different error code each time, but I didn't see the first few because I had automatic restart selected and it didn't give me enough time to read them. I recently tried to use driver verifier to check if it was a driver causing the BSOD and it wouldn't let me run windows so had to disable it. Help would be awesome!

Arc · 05 May 2014

Hi abstractthought.

Update the AMD chipset drivers from Support & Drivers .... the drivers available with ASrock is very old.

Let us know the result.
_________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff980040c0ed0, 0, fffff8800525a1aa, 0}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff980040c0ed0, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8800525a1aa, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b12100
GetUlongFromAddress: unable to read from fffff80003b121c0
 fffff980040c0ed0 

FAULTING_IP: 
usbfilter+41aa
fffff880`0525a1aa 8b4230          mov     eax,dword ptr [rdx+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

TRAP_FRAME:  fffff880031bd280 -- (.trap 0xfffff880031bd280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880031bd478
rdx=fffff980040c0ea0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800525a1aa rsp=fffff880031bd410 rbp=0000000000000002
 r8=0000000000000000  r9=fffff8800525a1a5 r10=0000000000000100
r11=fffff88002fd5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbfilter+0x41aa:
fffff880`0525a1aa 8b4230          mov     eax,dword ptr [rdx+30h] ds:fffff980`040c0ed0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003958bf0 to fffff800038dabc0

STACK_TEXT:  
fffff880`031bd118 fffff800`03958bf0 : 00000000`00000050 fffff980`040c0ed0 00000000`00000000 fffff880`031bd280 : nt!KeBugCheckEx
fffff880`031bd120 fffff800`038d8cee : 00000000`00000000 fffff980`040c0ed0 fffffa80`089bd500 fffff980`04144d80 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`031bd280 fffff880`0525a1aa : fffff880`031bd478 00000000`00000000 fffff980`04144d80 fffffa80`0933d910 : nt!KiPageFault+0x16e
fffff880`031bd410 fffff880`031bd478 : 00000000`00000000 fffff980`04144d80 fffffa80`0933d910 00000000`00000000 : usbfilter+0x41aa
fffff880`031bd418 00000000`00000000 : fffff980`04144d80 fffffa80`0933d910 00000000`00000000 fffff880`031bd478 : 0xfffff880`031bd478


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbfilter+41aa
fffff880`0525a1aa 8b4230          mov     eax,dword ptr [rdx+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbfilter+41aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b3082ae

FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd5_vrf_usbfilter+41aa

FAILURE_ID_HASH:  {99a3ab33-5d0d-830d-93f8-a253b816e3d3}

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

3: kd> lmvm usbfilter
start             end                 module name
fffff880`05256000 fffff880`05263000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 13:56:22 2009 (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

abstractthought · 09 May 2014

Well I have gone 3 days with no BSOD, then it happened again last night. My children were watching netflix and bam, BSOD. Error code 0x00000119. I have updated windows, updated avast anti-virus and done a full scan, used cc cleaner to defrag. I'm at my wits end here! Thank you for helping me and others with this forum, you have no idea how much it means to be able to go to someone for help with this!

Arc · 09 May 2014

Now it is a different BSOD. A stop 0x119, that is a display/graphics failure.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

As the display driver is the latest, I am not suggest you to altering it right now; but it might be needed later, depending on the situation.

So let us know the results.
_______________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, c156ec, c156e4, c156e3}

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

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 0000000000c156ec
Arg3: 0000000000c156e4
Arg4: 0000000000c156e3

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  b

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

LAST_CONTROL_TRANSFER:  from fffff880040ba22f to fffff800038d2bc0

STACK_TEXT:  
fffff880`02ffd438 fffff880`040ba22f : 00000000`00000119 00000000`00000001 00000000`00c156ec 00000000`00c156e4 : nt!KeBugCheckEx
fffff880`02ffd440 fffff880`13007ec5 : 00000000`00c156e3 00000000`00c156ec 00000000`00000000 00000000`00c156e4 : watchdog!WdLogEvent5+0x11b
fffff880`02ffd490 fffff880`13008131 : fffffa80`09242000 fffff880`02ffd5d0 00000000`000011ac fffff880`02ffd5d0 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`02ffd4c0 fffff880`13007f82 : fffffa80`00c156ec 00000001`00000000 fffffa80`09238000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`02ffd510 fffff880`048d813f : fffffa80`0898c040 00000000`00000000 00000000`00000202 fffff880`13126170 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02ffd540 fffff880`04878c12 : 00000000`00000000 00000000`00000001 fffff880`02ffd5f9 00000000`0000000f : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02ffd570 00000000`00000000 : 00000000`00000001 fffff880`02ffd5f9 00000000`0000000f 00000000`00c156e3 : atikmpag+0x46c12


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+46c12
fffff880`04878c12 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+46c12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53507abb

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+46c12

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+46c12

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+46c12

FAILURE_ID_HASH:  {64a04541-3229-7790-1f1d-dcd419b5ffef}

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

3: kd> lmvm atikmpag
start             end                 module name
fffff880`04832000 fffff880`048d5000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Apr 18 06:37:07 2014 (53507ABB)
    CheckSum:         000A6939
    ImageSize:        000A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

abstractthought · 18 Aug 2014

Ok, it has been a long time but suddenly I am having the same problem again. Random BSOD's at times that seem to have no connection with each other. Already updated windows, and avast. Ran a full system scan with avast and windows defender. Please help me once again!

Attachment 329658

Attachment 329659

Arc · 18 Aug 2014

You should have replied after following the suggestions. See the "Please Note" below the quick reply box.

I am having the same problem again.

And apparently it is not the same problem. They look the same blue, but the issues are very different. This time it is a memory issue. Either the RAM is failing or any driver is passing bad information to the memory.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________________

Code:

BugCheck 4E, {8d, 90fcf, 510008, fffff680000c9b1b}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+96c )

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

abstractthought · 31 Aug 2014

Ran memtest, no errors. Followed the instructions for driver verifier and immediate BSOD when I restarted to enable DV. Then my PC would not do anything when I tried to power it on. Ended up clearing CMOS and got it started. Then while trying to copy over the dump files using SF Diagnostic had another BSOD. Here is the sf zip file. Hope someone can figure it out. Thank you so much for this.

Arc · 01 Sep 2014

The crash dump is not a driver verifier enabled one.

Disable Logitech, Skype and PeerBlock from startup and try DV again.

abstractthought · 10 Sep 2014

Disabled Skype, Logitech and PeerBlock from startup, enabled DV, still had immediate BSOD.

Arc · 10 Sep 2014

Now we have got some information there.

Code:

BugCheck D5, {fffff980093e0e40, 0, fffff880130371aa, 0}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

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

usbfilter.sys is a part of your chipset driver. Update it from AMD Chipset Drivers ..... get the AMD Chipset Drivers only.

Also, just wanting a clarification again .... have you ran memtest86+ for at least 8 passes before deciding that RAM is not the problem? Asking, because there is the reason ......

Code:

BugCheck 3B, {c0000005, fffff8800180b149, fffff88009793e70, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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