Random BSOD's: Memory_management, bad pool header etc.

koolkat77 said:

Alright.

Delete all the stuff that MSE finds. (PS let us know if it finds any virus!)

Observe your computer and post back if you get crashes.

It didn´t find anything.

Just got a BSOD called: Bugcode USB Driver or something.. it didnt give me a mindump for some reason :/

it did update/create a MEMORY.dmp file in the Windows folder (it has a big size, about 310mb)

got a bsod WITH minidump now, attaching file.

koolkat77 said:

BSOD Analyze

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {9174, 2, 0, fffff880041c33d8}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 : dxgmms1.sys ( dxgmms1!VidSchiSignalRegisteredEvent+40 )

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

3: 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: 0000000000009174, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880041c33d8, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
 0000000000009174 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiSignalRegisteredEvent+40
fffff880`041c33d8 837b1005        cmp     dword ptr [rbx+10h],5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd700 -- (.trap 0xfffff88002ffd700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000b rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041c33d8 rsp=fffff88002ffd890 rbp=fffffa8007482010
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80074827d0
r11=fffff88002ffd8d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
dxgmms1!VidSchiSignalRegisteredEvent+0x40:
fffff880`041c33d8 837b1005        cmp     dword ptr [rbx+10h],5 ds:d8ad:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eda769 to fffff80002edb1c0

STACK_TEXT:  
fffff880`02ffd5b8 fffff800`02eda769 : 00000000`0000000a 00000000`00009174 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffd5c0 fffff800`02ed93e0 : 00000000`00000000 00000000`00000000 00000000`0002d8ad 00000000`00009164 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd700 fffff880`041c33d8 : fffffa80`0000000b 00000000`00000000 fffffa80`07495100 00000000`00000002 : nt!KiPageFault+0x260
fffff880`02ffd890 fffff880`041c0709 : fffffa80`07495cc0 fffffa80`054f3010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSignalRegisteredEvent+0x40
fffff880`02ffd8e0 fffff880`041bfe00 : fffffa80`00000000 fffffa80`06bba400 00000000`00000000 fffffa80`06bc6300 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x2e5
fffff880`02ffd980 fffff880`041bfc4c : fffffa80`06bc6300 fffffa80`07482010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02ffd9d0 fffff880`040c61cf : fffffa80`068de480 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffda20 fffff880`111017f0 : fffffa80`06b01000 fffffa80`06b01000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02ffda50 fffffa80`06b01000 : fffffa80`06b01000 00000000`00000000 00000000`00000000 fffff880`11101783 : nvlddmkm+0xd97f0
fffff880`02ffda58 fffffa80`06b01000 : 00000000`00000000 00000000`00000000 fffff880`11101783 fffffa80`06b01000 : 0xfffffa80`06b01000
fffff880`02ffda60 00000000`00000000 : 00000000`00000000 fffff880`11101783 fffffa80`06b01000 00000000`00000000 : 0xfffffa80`06b01000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiSignalRegisteredEvent+40
fffff880`041c33d8 837b1005        cmp     dword ptr [rbx+10h],5

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiSignalRegisteredEvent+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiSignalRegisteredEvent+40

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiSignalRegisteredEvent+40

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

3: kd> lmvm dxgmms1
start             end                 module name
fffff880`041b7000 fffff880`041fd000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\4CE799C146000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Sat Nov 20 15:49:53 2010 (4CE799C1)
    CheckSum:         00047A89
    ImageSize:        00046000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Your DirectX needs to be updated. Before you install the latest, make sure you uninstall the previous version.

BSOD Index
DirectX Update
Driver Reference Table

Had a lot of problems starting up PC so tried out safemode, runs perfect in there no problems. On the other side the normal startup is shitty, it keeps on BSODing me.
How do I uninstall DirectX, and can this cause any other problems?

Thomas :)

koolkat77 said:

Sorry my mistake.

No need to uninstall. Just update from the link I gave earlier.

Okay did so, i did this 1 week ago aswell though.