BSOD Wdf01000.sys

[Xhosas]

Hello, just got a bluescreen and i couldnt get back into windows untill i removed one of my RAM`s. I tryed the startup repair system restore before doing that but i was getting bluescreen everytime before or after windows was loading. Tho i only see only one event, the others might have been lost because of system restore, im not sure. Im posting my sf diagnostic tool files for someone to tell me more about this.

 

[x BlueRobot]

Any feedback here?

http://www.sevenforums.com/bsod-help-support/299098-bsod-l1c62x64-sys-2.html

 

[Xhosas]

Well after doing a clean reinstall of the windows those old bsod stoped.

 

[x BlueRobot]

Could you please mark the old thread as solved then?

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1000007E[/COLOR], {[COLOR="SeaGreen"]ffffffffc0000005[/COLOR], fffff88000e80000, fffff88002124318, fffff88002123b70}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR]

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

[COLOR="SeaGreen"]!chkimg -lo 50 -db !Wdf01000[/COLOR]
8 errors : !Wdf01000 (fffff88000e80003-fffff88000e8003b)
fffff88000e80000  48  83  64 *06  50  00  48  8b  69  10  0f *9f  f2  1f  49  8b H.d.P.H.i.....I.
fffff88000e80010  f0  48  8b *f8  83  fa  01  0f  84  a3  01 *23  00  4d  85  c0 .H.........#.M..
fffff88000e80020  75  6a  83 *fc  04  74  65  44  38  85  0c *06  00  00  74  1e uj...teD8.....t.
fffff88000e80030  45  8d  48 *28  48  8d  35  f5  73  04  00 *96  05  45  8d  41 E.H(H.5.s....E.A

[COLOR="SeaGreen"]!chkimg -lo 50 -d -db !Wdf01000[/COLOR]
    fffff88000e80003 - Wdf01000!FxFileObject::_DestroyFileObject+f
	[ 24:06 ]
    fffff88000e8000b - Wdf01000!FxFileObject::_DestroyFileObject+17 (+0x08)
	[ ba:9f ]
    fffff88000e80013 - Wdf01000!FxFileObject::_DestroyFileObject+1f (+0x08)
	[ d9:f8 ]
    fffff88000e8001b - Wdf01000!FxFileObject::_DestroyFileObject+27 (+0x08)
	[ 00:23 ]
    fffff88000e80023 - Wdf01000!FxFileObject::_DestroyFileObject+2f (+0x08)
	[ fa:fc ]
    fffff88000e8002b - Wdf01000!FxFileObject::_DestroyFileObject+37 (+0x08)
	[ 01:06 ]
    fffff88000e80033 - Wdf01000!FxFileObject::_DestroyFileObject+3f (+0x08)
	[ 0b:28 ]
    fffff88000e8003b - Wdf01000!FxFileObject::_DestroyFileObject+47 (+0x08)
	[ b2:96 ]
[COLOR="Red"]8 errors : !Wdf01000[/COLOR] ([COLOR="Blue"]fffff88000e80003-fffff88000e8003b[/COLOR])
fffff88000e80000  48  83  64 *06  50  00  48  8b  69  10  0f *9f  f2  1f  49  8b H.d.P.H.i.....I.
fffff88000e80010  f0  48  8b *f8  83  fa  01  0f  84  a3  01 *23  00  4d  85  c0 .H.........#.M..
fffff88000e80020  75  6a  83 *fc  04  74  65  44  38  85  0c *06  00  00  74  1e uj...teD8.....t.
fffff88000e80030  45  8d  48 *28  48  8d  35  f5  73  04  00 *96  05  45  8d  41 E.H(H.5.s....E.A

fffff88002124318 -- ([COLOR="SeaGreen"].exr 0xfffff88002124318[/COLOR])
ExceptionAddress: [COLOR="Blue"]fffff88000e80000[/COLOR] (Wdf01000!FxFileObject::_DestroyFileObject+0x000000000000000c)
   ExceptionCode: [COLOR="Red"]c0000005 (Access violation)[/COLOR]
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000057ff843a3a8
Attempt to write to address 0000057ff843a3a8

Okay, the image seems to be corrupt, and the reason being so, is because a stride (I'm assuming it means in terms of a array), being the number of bytes until the next or previous element within an array, doesn't quite add up and has crashed the system.

1: kd> [COLOR="SeaGreen"]!dpx[/COLOR]
Start memory scan  : 0xfffff88002124550 ($csp)
End memory scan    : 0xfffff88002125000 (Stack Base)

               rcx : 0xfffffa8007a50810 :  dt Wdf01000!FxDevice
               rbx : 0xfffffa8007a4f180 :  dt Wdf01000!FxPkgGeneral
0xfffff88002124598 : 0xfffff88000e85a9f : Wdf01000!FxPkgGeneral::OnClose+0xd3
0xfffff880021245a0 : 0xfffffa8007a4f180 :  dt Wdf01000!FxPkgGeneral
0xfffff880021245b0 : 0xfffffa8007a4f180 :  dt Wdf01000!FxPkgGeneral
0xfffff880021245e8 : 0xfffffa8007a4f180 :  dt Wdf01000!FxPkgGeneral
0xfffff880021245f8 : 0xfffff88000e852cf : Wdf01000!FxPkgGeneral::Dispatch+0x14f
0xfffff88002124618 : 0xfffffa8007a4faf0 :  dt Wdf01000!FxIoQueue
0xfffff88002124658 : 0xfffff88000e79245 : Wdf01000!FxDevice::Dispatch+0xa9
0xfffff88002124688 : 0xfffff800025cd22e : nt!IopDeleteFile+0x11e
0xfffff880021246e8 : 0xfffff88000e14f10 : mountmgr!MountMgrSendDeviceControl+0xbc
0xfffff88002124718 : 0xfffff800022d7e54 : nt!ObfDereferenceObject+0xd4
0xfffff88002124768 : 0xfffff88000e04110 : mountmgr!WPP_GLOBAL_Control
0xfffff88002124778 : 0xfffff88000e06d9d : mountmgr!QueryDeviceInformation+0x539
0xfffff880021247f8 : 0xfffff88000e0dd83 : mountmgr!MountMgrMountedDeviceArrival+0x1fb
0xfffff88002124840 : 0x0000000000010008 :  Trap @ fffff88002124840
0xfffff88002124848 : 0xfffff88000e0f180 : mountmgr!MountMgrMountedDeviceNotification
0xfffff88002124890 : 0xfffff88000e0f180 : mountmgr!MountMgrMountedDeviceNotification
0xfffff88002124910 : 0xfffff88000e0f180 : mountmgr!MountMgrMountedDeviceNotification
0xfffff88002124968 : 0xfffff88000fc23cf : volmgr!IsEqualGUID+0xf
0xfffff88002124980 : 0xfffff8000279d7d0 : nt!PnpDeviceClassNotifyList+0xb0
0xfffff880021249a8 : 0xfffff88000e0f1f5 : mountmgr!MountMgrMountedDeviceNotification+0x75
0xfffff880021249d8 : 0xfffff8000253c77c : nt!PnpNotifyDriverCallback+0x5c
0xfffff88002124a10 : 0xfffffa8006734c58 : 0xfffff800024742e0 : nt!ExWorkerQueue+0x60
0xfffff88002124a18 : 0xfffff800022c45d2 : nt!KiCommitThreadWait+0x1d2
0xfffff88002124a50 : 0xfffff8000279d7d0 : nt!PnpDeviceClassNotifyList+0xb0
0xfffff88002124a68 : 0xfffff80002710838 : nt!PnpNotifyDeviceClassChange+0x188
0xfffff88002124b38 : 0xfffff8000253b868 : nt!PnpDeviceEventWorker
0xfffff88002124b68 : 0xfffff800022d8261 : nt!ExpWorkerThread+0x111
0xfffff88002124b70 : 0xfffff8000253b868 : nt!PnpDeviceEventWorker
0xfffff88002124b80 : 0xfffff800024742d8 : nt!ExWorkerQueue+0x58
0xfffff88002124be0 : 0xfffff800022d8150 : nt!ExpWorkerThread
0xfffff88002124bf8 : 0xfffff8000256cbae : nt!PspSystemThreadStartup+0x5a
0xfffff88002124c38 : 0xfffff800022bf8c6 : nt!KxStartSystemThread+0x16

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Xhosas]

I did test the ram sticks, no matter where i put one of them i allways get bluescreen before windows starts so i guess that makes means that stick is the fault. Now im running with only one stick.

 

[x BlueRobot]

Did you get any errors running MemTest86+? Using one stick, change it to a different slot, and then see if it crashes, hopefully you will be able to see if the RAM stick(s) are faulty or a motherboard DIMM slot is faulty.