Windows 7 Crash dump file

chronic9

Supreme [H]ardness
Joined
Aug 18, 2004
Messages
5,854
Ive been getting BSODs lately, generally when I play video games. I have the latest nvidia drivers installed. and i checked my chipset drivers also newest.
any suggestions?

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c15000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000040

CURRENT_IRQL: 0

FAULTING_IP:
nt+72e83
fffff800`02c87e83 f0490fba6e4000 lock bts qword ptr [r14+40h],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff80002c84ca9 to fffff80002c85740

STACK_TEXT:
fffff880`0459d7d8 fffff800`02c84ca9 : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000001 : nt+0x70740
fffff880`0459d7e0 00000000`0000000a : 00000000`00000040 00000000`00000002 00000000`00000001 fffff800`02c87e83 : nt+0x6fca9
fffff880`0459d7e8 00000000`00000040 : 00000000`00000002 00000000`00000001 fffff800`02c87e83 00000000`00000000 : 0xa
fffff880`0459d7f0 00000000`00000002 : 00000000`00000001 fffff800`02c87e83 00000000`00000000 00000000`00000000 : 0x40
fffff880`0459d7f8 00000000`00000001 : fffff800`02c87e83 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff880`0459d800 fffff800`02c87e83 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0459d808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x72e83


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+72e83
fffff800`02c87e83 f0490fba6e4000 lock bts qword ptr [r14+40h],0

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nt+72e83

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
 
After opening the dump in windbg, run .symfix, .reload, then !analyze -v
 
Yeah, with no symbols it would be just a complete guess. If you have the dump somewhere I can take a look.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Yeah, with no symbols it would be just a complete guess. If you have the dump somewhere I can take a look.

This posting is provided "AS IS" with no warranties, and confers no rights.

That is, unless it's a full kernel dump :)
 
I will tell you, though, that this is an IRQL_NOT_LESS_OR_EQUAL fault, but without symbols, that doesn't do us much good ;)
 
Back
Top