Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random Windows 7 x64 BSOD - Need Help

27 Jan 2010   #1

Windows 7 x64
 
 
Random Windows 7 x64 BSOD - Need Help

Hopefully, I can get through posting this without another one. I just want to go on record that I have been working on this problem for weeks with no resolve. Currently, my system runs beautifully in Windows 7 Ultimate x64 until these random crashes occur causing BSODs. They are completely random, and happen when I'm just browsing the desktop, on the internet, in a game, whatever. They are frequent and of extreme nuisance.

I have run memory tests, hard drive tests, video card tests, board tests, etc., the whole lot, and everything comes back clean as a whistle. All GPU and CPU components have aftermarket cooling and run well below the normal temperature range when under load. I have the latest BIOS and driver updates for all my hardware components and have even tried older drivers and builds to resolve the problem, but to no avail.

Current system specs:

Motherboard: Gigabyte EP45-UD3R v1.1
CPU: Intel Core 2 Quad Q9550 2.8GHz (at stock clock for now) with aftermarket cooling
RAM: GSkill DDR2 1066 4GB (two 2GB Sticks)
Graphics: EVGA Nvidia Geforce 8800GT with aftermarket cooling
OS: Windows 7 Ultimate x64

I would like to point out that I built this rig less than a year ago, and it has run beautifully until a month or two ago when I've started getting these random blue screens. I have even sent my board and memory in for RMA, and have gotten replacements thinking that was the issue. Everything hardware tests perfectly.

On to the memory dump. When I use windbg.exe to debug the memory dump, it's always a random system component that is at fault. I have gotten almost every stop error known, and it always a different system component every time it crashes.

I will post the dumps periodically as they happen. This one occurred when I was trying to install Windows Debugging Tools for the first time:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff87fde4f844c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88010b80145, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


WRITE_ADDRESS: fffff87fde4f844c

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::StartPreparation+19
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d

MM_INTERNAL_CODE: 5

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

MODULE_NAME: dxgmms1

FAULTING_MODULE: fffff88010b5a000 dxgmms1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88005bdf710 -- (.trap 0xfffff88005bdf710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005bdfb04 rbx=0000000000000000 rcx=fffffa8005dca000
rdx=fffff8a00174fde0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010b80145 rsp=fffff88005bdf8a0 rbp=fffff8a00174fde0
r8=fffffa800604ebd0 r9=0000000000000001 r10=0000000000000000
r11=000000000000001d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
dxgmms1!VIDMM_GLOBAL::StartPreparation+0x19:
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d ds:9060:a020=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002b4eb91 to fffff80002ad0f00

STACK_TEXT:
fffff880`05bdf5a8 fffff800`02b4eb91 : 00000000`00000050 fffff87f`de4f844c 00000000`00000001 fffff880`05bdf710 : nt!KeBugCheckEx
fffff880`05bdf5b0 fffff800`02acefee : 00000000`00000001 00000000`c0000001 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`05bdf710 fffff880`10b80145 : 00000000`ffffd978 00000000`00000007 fffffa80`05dba000 fffffa80`05dbb750 : nt!KiPageFault+0x16e
fffff880`05bdf8a0 fffff880`10b77e34 : 00000000`c0000001 00000000`0000001d 00000000`00000000 fffffa80`05daf7a0 : dxgmms1!VIDMM_GLOBAL::StartPreparation+0x19
fffff880`05bdf8d0 fffff880`10b9265d : 00000000`00000000 fffff8a0`0174fde0 fffffa80`00000000 fffffa80`0604ebd0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x3a0
fffff880`05bdfaa0 fffff880`10b92398 : fffff800`00b96080 fffff880`10b91d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05bdfc90 fffff880`10b91e96 : 00000000`00000000 fffffa80`06121530 00000000`00000080 fffffa80`05daf010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05bdfcc0 fffff800`02d74166 : 00000000`03bfe2e6 fffffa80`05dc9060 fffffa80`036e5040 fffffa80`05dc9060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05bdfd00 fffff800`02aaf486 : fffff800`02c49e80 fffffa80`05dc9060 fffff800`02c57c40 fffff880`01250534 : nt!PspSystemThreadStartup+0x5a
fffff880`05bdfd40 00000000`00000000 : fffff880`05be0000 fffff880`05bda000 fffff880`05bdf650 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::StartPreparation+19
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::StartPreparation+19

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+19

BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+19

Followup: MachineOwner

My System SpecsSystem Spec
.

27 Jan 2010   #2

Windows 7 x64
 
 

Just got this one while transferring some files to an external drive:


NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800318c6a8
Arg3: fffff8800318bf00
Arg4: fffff80002a79d82

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


EXCEPTION_RECORD: fffff8800318c6a8 -- (.exr 0xfffff8800318c6a8)
ExceptionAddress: fffff80002a79d82 (nt!ExReinitializeResourceLite+0x00000000000000f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800318bf00 -- (.cxr 0xfffff8800318bf00)
rax=fffff8800318c918 rbx=fffffa8003c2d050 rcx=fffffa8003c2d050
rdx=000000000000070d rsi=fffffa8003c2d010 rdi=00fffa8006302260
rip=fffff80002a79d82 rsp=fffff8800318c8e0 rbp=0000000000000745
r8=fffff8800318c9a1 r9=fffff8a002beaf28 r10=fffff80002a1f000
r11=0000000000000000 r12=0000000000000000 r13=fffffa8004a70180
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExReinitializeResourceLite+0xf2:
fffff800`02a79d82 8b7708 mov esi,dword ptr [rdi+8] ds:002b:00fffa80`06302268=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
Ntfs!NtfsDeleteFcb+10c
fffff880`012bbefc 66392e cmp word ptr [rsi],bp

FAULTING_IP:
nt!ExReinitializeResourceLite+f2
fffff800`02a79d82 8b7708 mov esi,dword ptr [rdi+8]

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff880012bbefc to fffff80002a79d82

STACK_TEXT:
fffff880`0318c8e0 fffff880`012bbefc : fffff880`0318c9b0 00000000`00000745 fffffa80`03c2d010 fffffa80`03922010 : nt!ExReinitializeResourceLite+0xf2
fffff880`0318c920 fffff880`0122ef6a : fffff800`02c345a0 fffff880`0318cb01 fffff880`0318c9a1 fffff8a0`05fd1010 : Ntfs!NtfsDeleteFcb+0x10c
fffff880`0318c980 fffff880`012b92cc : fffffa80`03922010 fffffa80`04a70180 fffff8a0`05fd1010 fffff8a0`05fd13a8 : Ntfs!NtfsTeardownFromLcb+0x1ea
fffff880`0318ca10 fffff880`01237882 : fffffa80`03922010 fffffa80`03922010 fffff8a0`05fd1010 fffff880`0318cb00 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`0318ca90 fffff880`012d0813 : fffffa80`04a70180 fffff800`02c345a0 fffff8a0`6366744e 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0318cad0 fffff880`012aa38f : fffffa80`03922010 fffff8a0`05fd1140 fffff8a0`05fd1010 fffffa80`04a70180 : Ntfs!NtfsCommonClose+0x353
fffff880`0318cba0 fffff800`02a9e161 : 00000000`00000000 fffff880`012aa200 fffff800`02c96101 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0318cc70 fffff800`02d34166 : 768d44e3`8b440000 fffffa80`036f6680 00000000`00000080 fffffa80`036cb040 : nt!ExpWorkerThread+0x111
fffff880`0318cd00 fffff800`02a6f486 : fffff880`02f63180 fffffa80`036f6680 fffff880`02f6dfc0 3e0c8d4b`000011e0 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cd40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c9b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!NtfsDeleteFcb+10c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f

STACK_COMMAND: .cxr 0xfffff8800318bf00 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsDeleteFcb+10c

BUCKET_ID: X64_0x24_Ntfs!NtfsDeleteFcb+10c

Followup: MachineOwner
My System SpecsSystem Spec
27 Jan 2010   #3

Windows 7 x64
 
 

Got this one while idle on the desktop doing nothing:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ac6105, The address that the exception occurred at
Arg3: fffff88003c71248, Exception Record Address
Arg4: fffff88003c70aa0, Context Record Address

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

PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ac6105 498b08 mov rcx,qword ptr [r8]

EXCEPTION_RECORD: fffff88003c71248 -- (.exr 0xfffff88003c71248)
ExceptionAddress: fffff80002ac6105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88003c70aa0 -- (.cxr 0xfffff88003c70aa0)
rax=00000000321500ff rbx=0000000000000000 rcx=fffffa8005a923d0
rdx=00fff8a000b1f831 rsi=fffff8a000b46c80 rdi=fffffa8005a91000
rip=fffff80002ac6105 rsp=fffff88003c71480 rbp=0000000040000040
r8=00fff8a000b1f830 r9=0000000000000001 r10=fffffa8005a923d0
r11=fffff8a000ca4000 r12=fffff88003c715f8 r13=0000000000000102
r14=fffff88003c71670 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02ac6105 498b08 mov rcx,qword ptr [r8] ds:002b:00fff8a0`00b1f830=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d
fffff880`04094f25 483bc3 cmp rax,rbx

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88004094f25 to fffff80002ac6105

STACK_TEXT:
fffff880`03c71480 fffff880`04094f25 : fffffa80`00000002 00000000`00000000 fffff8a0`00000001 fffff8a0`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`03c71490 fffff880`0407724b : 00000000`00000000 fffff8a0`00ca4000 00000000`40000040 fffff8a0`00b3c9e0 : dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+0x30d
fffff880`03c715b0 fffff960`006fb3fa : 00000000`00000104 fffff900`c00c2580 fffff900`c00c0020 ffffffff`fffe7960 : dxgkrnl!DxgkCddSubmitPresentHistory+0x20b
fffff880`03c71650 fffff960`006f95d5 : fffffa80`05b22160 fffffa80`05b22160 00000000`00000000 fffff900`c00c0020 : cdd!CHwCommandBuffer::FlushGdiCommands+0x24a
fffff880`03c71940 fffff960`006f5c6e : ffffffff`fffd7476 00000000`00000010 00000000`00000000 00000000`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`03c71970 fffff800`02d66166 : 00000000`034de8ab fffffa80`05af4060 00000000`00000080 fffffa80`05aeeb30 : cdd!PresentWorkerThread+0x902
fffff880`03c71d00 fffff800`02aa1486 : fffff880`02fd3180 fffffa80`05af4060 fffff880`02fddfc0 00000000`00000283 : nt!PspSystemThreadStartup+0x5a
fffff880`03c71d40 00000000`00000000 : fffff880`03c72000 fffff880`03c6c000 fffff880`03c71310 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc590

STACK_COMMAND: .cxr 0xfffff88003c70aa0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

BUCKET_ID: X64_0x7E_dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

Followup: MachineOwner
My System SpecsSystem Spec
.


27 Jan 2010   #4

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hi, Welcome to SF,

I guess according to analysis i think the issue is with your Display driver the Dump file is pointing to Direct X driver dxgkrnl.sys if that didn't do it then post the Dump file we will have a look at it.

Hope this helps,
Captain
My System SpecsSystem Spec
27 Jan 2010   #5

Windows 7 x64
 
 

Got this one while loading up a game:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a82105, The address that the exception occurred at
Arg3: fffff8800383f248, Exception Record Address
Arg4: fffff8800383eaa0, Context Record Address

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

PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a82105 498b08 mov rcx,qword ptr [r8]

EXCEPTION_RECORD: fffff8800383f248 -- (.exr 0xfffff8800383f248)
ExceptionAddress: fffff80002a82105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800383eaa0 -- (.cxr 0xfffff8800383eaa0)
rax=0000000006410100 rbx=0000000000000000 rcx=fffffa8005b753d0
rdx=00fff8a000b3bec1 rsi=fffff8a000b864f0 rdi=fffffa8005b74000
rip=fffff80002a82105 rsp=fffff8800383f480 rbp=0000000040000040
r8=00fff8a000b3bec0 r9=0000000000000001 r10=fffffa8005b753d0
r11=fffff8a000cc8000 r12=fffff8800383f5f8 r13=0000000000000102
r14=fffff8800383f670 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a82105 498b08 mov rcx,qword ptr [r8] ds:002b:00fff8a0`00b3bec0=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d
fffff880`04082161 483bc3 cmp rax,rbx

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88004082161 to fffff80002a82105

STACK_TEXT:
fffff880`0383f480 fffff880`04082161 : fffffa80`00000002 00000000`00000000 fffff8a0`00000001 fffff8a0`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0383f490 fffff880`04064257 : 00000000`00000000 fffff8a0`00cc8000 00000000`40000040 fffff8a0`00b62010 : dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+0x30d
fffff880`0383f5b0 fffff960`0062b3fa : 00000000`00000000 fffff900`c00c1d20 fffff900`c00c0020 ffffffff`fffe7960 : dxgkrnl!DxgkCddSubmitPresentHistory+0x20b
fffff880`0383f650 fffff960`006295d5 : fffffa80`05bc01f0 fffffa80`05bc01f0 00000000`00000002 fffff900`c00c0020 : cdd!CHwCommandBuffer::FlushGdiCommands+0x24a
fffff880`0383f940 fffff960`00625c21 : ffffffff`fffd7476 00000000`00000001 00000000`00000001 fffffa80`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`0383f970 fffff800`02d22166 : 00000000`033b98fd fffffa80`05bd35c0 00000000`00000080 fffffa80`05ba7060 : cdd!PresentWorkerThread+0x8b5
fffff880`0383fd00 fffff800`02a5d486 : fffff880`02fd3180 fffffa80`05bd35c0 fffff880`02fddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0383fd40 00000000`00000000 : fffff880`03840000 fffff880`0383a000 fffff880`0383f4b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e

STACK_COMMAND: .cxr 0xfffff8800383eaa0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

BUCKET_ID: X64_0x7E_dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+30d

Followup: MachineOwner
My System SpecsSystem Spec
27 Jan 2010   #6

Windows 7 x64
 
 

Here is the minidump for the last crash.
My System SpecsSystem Spec
27 Jan 2010   #7

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Looked at the Dump file basically mentioning the same driver dxgkrnl.sys i found that you have already nVidia driver dated 2010. Still i would recommend to remove the drivers completely follow this Info: nVidia Driver Cleaning Guide - Overclock.net - Overclocking.net then download then driver from website NOT from Windows update. Also physically check the video card to make sure that the cooling fan are working and that there's nothing interfering with the airflow.

Hope this helps,
Captain
My System SpecsSystem Spec
28 Jan 2010   #8

Windows 7 x64
 
 

Quote   Quote: Originally Posted by Capt.Jack Sparrow View Post
Looked at the Dump file basically mentioning the same driver dxgkrnl.sys i found that you have already nVidia driver dated 2010. Still i would recommend to remove the drivers completely follow this Info: nVidia Driver Cleaning Guide - Overclock.net - Overclocking.net then download then driver from website NOT from Windows update. Also physically check the video card to make sure that the cooling fan are working and that there's nothing interfering with the airflow.

Hope this helps,
Captain
The driver version I am using is the one off the website and not from the Windows Update. In fact with this install I did not use Windows Update for any of my hardware components. I downloaded all of them from the manufacture's website and installed them manually. Both ways caused BSODs to occur.

However, I did as you asked and cleaned all the drivers out and did a reinstall of the latest drivers. I opened up Mass Effect 2, within 3 minutes or so of playing the computer crashed with a BSOD.

Here is the memory dump contents:

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+0
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: MassEffect2.ex

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88002f92858 -- (.exr 0xfffff88002f92858)
ExceptionAddress: fffff88010418384 (nvlddmkm+0x000000000059f384)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88002f92900 -- (.trap 0xfffff88002f92900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffa80059ec520 rbx=0000000000000000 rcx=0000000000000001
rdx=00000000c1d00011 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010418384 rsp=fffff88002f92a98 rbp=fffffa8004ad1810
r8=000000000000046a r9=fffff88002f92c28 r10=0000000000000000
r11=00000087bd2e788c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nvlddmkm+0x59f384:
fffff880`10418384 4439801c010000 cmp dword ptr [rax+11Ch],r8d ds:6000:c63c=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a74c2e to fffff80002a7ced0

STACK_TEXT:
fffff880`02f91938 fffff800`02a74c2e : 00000000`00000000 00000000`00000000 fffff880`02f920b0 fffff800`02aa9e28 : nt!KeBugCheck
fffff880`02f91940 fffff800`02aa2bed : fffff800`02c89c24 fffff800`02bc2a3c fffff800`02a0b000 fffff880`02f92858 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f91970 fffff800`02aaa250 : fffff800`02bcaa88 fffff880`02f919e8 fffff880`02f92858 fffff800`02a0b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f919a0 fffff800`02ab71b5 : fffff880`02f92858 fffff880`02f920b0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x410
fffff880`02f92080 fffff800`02a7c542 : fffff880`02f92858 00000000`0000046a fffff880`02f92900 fffffa80`04ae6940 : nt!KiDispatchException+0x135
fffff880`02f92720 fffff800`02a7ae4a : 00000000`00000001 fffffa80`038c5b20 fffffa80`05756000 fffffa80`040b9000 : nt!KiExceptionDispatch+0xc2
fffff880`02f92900 fffff880`10418384 : fffff880`10336e58 00000000`0000046c fffffa80`04ae6940 fffffa80`04aea910 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f92a98 fffff880`10336e58 : 00000000`0000046c fffffa80`04ae6940 fffffa80`04aea910 fffffa80`036cf010 : nvlddmkm+0x59f384
fffff880`02f92aa0 fffff880`102eac16 : 00000000`000032d4 fffffa80`04ae6940 00000000`00000100 00000000`0000046c : nvlddmkm+0x4bde58
fffff880`02f92c20 fffff880`101e69c9 : fffffa80`00000000 00000000`00000022 fffffa80`00000000 fffffa80`00000000 : nvlddmkm+0x471c16
fffff880`02f92d30 fffff880`1000644e : fffffa80`05756000 00000000`00000000 fffffa80`04ad1810 fffffa80`04c019d0 : nvlddmkm+0x36d9c9
fffff880`02f92d60 fffff880`0ff17f03 : fffffa80`04e11000 fffffa80`00000001 00000000`00000000 fffffa80`04e11000 : nvlddmkm+0x18d44e
fffff880`02f92e10 fffff880`0fe970c4 : fffff880`0ff17ea9 fffffa80`04e54d20 fffffa80`04e11018 00000000`00000000 : nvlddmkm+0x9ef03
fffff880`02f92e80 fffff800`02a885dc : fffff880`0fe97073 fffff880`02f63180 fffffa80`04e54d38 00000000`00000000 : nvlddmkm+0x1e0c4
fffff880`02f92f00 fffff800`02a83065 : 00000000`00000000 fffffa80`03918b60 00000000`00000000 fffff880`0fedfcf0 : nt!KiRetireDpcList+0x1bc
fffff880`02f92fb0 fffff800`02a82e7c : fffffa80`04074c08 fffff880`06010c60 00000000`00000001 fffffa80`03918b60 : nt!KxRetireDpcList+0x5
fffff880`06010ba0 fffff800`02ac8793 : fffff800`02a788e3 fffff800`02a7894f fffffa80`03918b60 00000000`000005c0 : nt!KiDispatchInterruptContinue
fffff880`06010bd0 fffff800`02a7894f : fffffa80`03918b60 00000000`000005c0 00000000`00000000 fffffa80`03918740 : nt!KiDpcInterruptBypass+0x13
fffff880`06010be0 00000000`72b8db24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x19f
00000000`2c4dfed0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72b8db24


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+59f384
fffff880`10418384 4439801c010000 cmp dword ptr [rax+11Ch],r8d

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nvlddmkm+59f384

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b4c080b

FAILURE_BUCKET_ID: X64_0x1E_nvlddmkm+59f384

BUCKET_ID: X64_0x1E_nvlddmkm+59f384

Followup: MachineOwner
My System SpecsSystem Spec
28 Jan 2010   #9

Windows 7 x64
 
 

I can't even play the game for 2-3 minutes now. I don't understand why my system is crashing. I have the latest Nvidia drivers and the latest Directx drivers. I just got this error:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003b63ff3, The address that the exception occurred at
Arg3: fffff8800411e658, Exception Record Address
Arg4: fffff8800411deb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`03b63ff3 48894108 mov qword ptr [rcx+8],rax

EXCEPTION_RECORD: fffff8800411e658 -- (.exr 0xfffff8800411e658)
ExceptionAddress: fffff88003b63ff3 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800411deb0 -- (.cxr 0xfffff8800411deb0)
rax=fffffa8005d13190 rbx=fffff8a006e6f440 rcx=00fffa800382f2f0
rdx=fffff8a006e539a0 rsi=fffffa8005d39910 rdi=fffffa8005b63000
rip=fffff88003b63ff3 rsp=fffff8800411e890 rbp=0000000000000000
r8=fffffa8005d39960 r9=fffff8800411e901 r10=0000000000000000
r11=fffffa8005b41010 r12=000000000000001c r13=0000000000000000
r14=fffffa80039a4290 r15=0000000000000072
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`03b63ff3 48894108 mov qword ptr [rcx+8],rax ds:002b:00fffa80`0382f2f8=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`03b63ff3 48894108 mov qword ptr [rcx+8],rax

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88003b618af to fffff88003b63ff3

STACK_TEXT:
fffff880`0411e890 fffff880`03b618af : 00000000`00000000 fffffa80`0410c0e0 00000000`00000049 fffffa80`03e412a8 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`0411e8d0 fffff880`03b7b65d : 00000000`00000000 fffff8a0`01992680 fffffa80`00000000 fffffa80`039a4290 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0411eaa0 fffff880`03b7b398 : fffff800`00b96080 fffff880`03b7ad00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0411ec90 fffff880`03b7ae96 : 00000000`00000000 fffffa80`0399dd50 00000000`00000080 fffffa80`05b41010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0411ecc0 fffff800`02d61166 : 00000000`031b7d3b fffffa80`05b45060 fffffa80`0366b890 fffffa80`05b45060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0411ed00 fffff800`02a9c486 : fffff800`02c36e80 fffffa80`05b45060 fffff800`02c44c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0411ed40 00000000`00000000 : fffff880`0411f000 fffff880`04119000 fffff880`0411e650 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff8800411deb0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

Followup: MachineOwner
My System SpecsSystem Spec
29 Jan 2010   #10

Windows 7 x64
 
 

I could use a little help here. These BSODs are ruining me.
My System SpecsSystem Spec
Reply

 Random Windows 7 x64 BSOD - Need Help




Thread Tools



Similar help and support threads for2: Random Windows 7 x64 BSOD - Need Help
Thread Forum
Solved Random BSOD Windows 7 x64 BSOD Help and Support
Solved Random BSOD on windows. BSOD Help and Support
random bsod on windows 7 - f4 03 BSOD Help and Support
Random BSOD - Windows 7 x64 BSOD Help and Support
Windows 7 Random BSOD BSOD Help and Support
Random Windows 7 BSOD BSOD Help and Support
Windows 7 64 Bit Random BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:15 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33