BSOD General Useage 0x000000d1

wnight77 · 06 Nov 2013

man its getting really bad, i checked the logitech usb drivers everything is up to date and running fine according to that.

here is a list of all the blue screens. its bluescreening when the pc is just sitting here nobody is even at the pc.

x BlueRobot · 07 Nov 2013

Code:

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03e95000 fffff880`03f33000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Aug 30 23:32:32 2013 (52211D80)
    CheckSum:         0009C9D2
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update to the latest WHQL version - Latest AMD Catalyst Video Driver for Windows 7

Code:

BugCheck FE, {6, fffffa8008235a18, 63706458, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_AssertSig+25 )

This bugcheck indicates that the signature expected didn't match the signature given, therefore corrupting the object data structure.

Code:

0: kd> dt nt!_OBJECT_TYPE fffffa8008235a18
   +0x000 TypeList         : _LIST_ENTRY [ 0xfffffa80`08235ba0 - 0x00000000`50456368 ]
   +0x010 Name             : _UNICODE_STRING "--- memory read error at address 0x00000000`00000113 ---"
   +0x020 DefaultObject    : 0xfffff800`03455000 Void
   +0x028 Index            : 0 ''
   +0x02c TotalNumberOfObjects : 0
   +0x030 TotalNumberOfHandles : 0x4392db0
   +0x034 HighWaterNumberOfObjects : 0xfffff880
   +0x038 HighWaterNumberOfHandles : 0x8235a18
   +0x040 TypeInfo         : _OBJECT_TYPE_INITIALIZER
   +0x0b0 TypeLock         : _EX_PUSH_LOCK
   +0x0b8 Key              : 0x8235410
   +0x0c0 CallbackList     : _LIST_ENTRY [ 0xfffffa80`08235050 - 0x63706458`524f4975 ]

Unfortunately, either the object data structure is completely corrupt, or it was retained within the Minidump.

What do you have connected to your USB ports?

Code:

BugCheck 3B, {c0000005, fffff9600012667b, fffff880077e3d60, 0}

Probably caused by : win32k.sys ( win32k!HANDLELOCK::vLockHandle+10f )

Code:

0xfffff880077e3e58 : 0xfffff9600012667b : win32k!HANDLELOCK::vLockHandle+0x10f
0xfffff880077e3e60 : 0xfffff8000323f460 : hal!HalpKInterruptHeap+0x460
0xfffff880077e3e88 : 0xfffff960000d6a64 : win32k!cCapString+0x74
0xfffff880077e3ed8 : 0xfffff960000d796e : win32k!pfsubGetFontSub+0xae
0xfffff880077e3ee8 : 0xfffff960000d985d : win32k!MAPPER::bNearMatch+0x289
0xfffff880077e4188 : 0xfffff800032d6d42 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x12
0xfffff880077e41b8 : 0xfffff800032d6a8b : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x1b
0xfffff880077e41f8 : 0xfffff800032f53d5 : nt!RtlGetExtendedContextLength+0x19
0xfffff880077e4248 : 0xfffff96000287e80 : win32k!DEC_SHARE_REF_CNT+0xe4
0xfffff880077e4258 : 0xfffff9600007fc0d : win32k!RGNOBJ::bCopy+0x5d
0xfffff880077e42b8 : 0xfffff96000095e53 : win32k!EngBitBlt+0x77b
0xfffff880077e4368 : 0xfffff800032d6d42 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x12
0xfffff880077e43c8 : 0xfffff800032cd242 : nt!KiExceptionDispatch+0xc2

The stack frame where our exception occurred, is highlighted in blue,

Code:

win32k!HANDLELOCK::vLockHandle+10f
fffff960`0012667b f0480fba2900    lock bts qword ptr [rcx],0

The instruction locked the processor bus, to stop any other processors have interrupting that thread.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Information

Additional Help - Using Driver Verifier to identify issues with Drivers