pman860507
New Member
- Joined
- Sep 20, 2010
- Messages
- 84
- Thread Author
- #1
i have been having bsod problems since i installed windows 7 on my computer. every where i post says that its a different issue. it really has its moments sometimes it goes weeks and months without a bosd and then all then its a every day or multiple times a day. the past 2 days its been acting up again and i have 3 memory dump files and it looks like ntoskrnl.exe is casing 2 of the crashes and dxgmms1.sys caused the other one. i have ran the debugging tools and bluescreen view i will show bluescreen viewer first.
mini dump file has been attached.
im only showing the file that was highlighted red. i think that is the only one that matters. (let me know if im wrong.)
they will be in the order that they happened with the most recent first.
092010-26863-01.dmp
091910-22292-01.dmp
091910-30872-01.dmp
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path ntoskrnl.exentoskrnl.exe+6fca9fffff800`02e09000fffff800`033e50000x005dc0000x4c1c44a96/18/2010 11:16:41 PMMicrosoft® Windows® Operating SystemNT Kernel & System6.1.7600.16617 (win7_gdr.100618-1621)Microsoft CorporationC:\Windows\system32\ntoskrnl.exe
091910-30872-01.dmp (the most recent crash)
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path dxgmms1.sysdxgmms1.sys+1e7c3fffff880`040b7000fffff880`040fd0000x000460000x4a5bc5787/13/2009 6:38:32 PM
windbg
first one is 092010-26863-01.dmp
091910-22292-01.dmp
091910-30872-01.dmp (the most recent crash)
in the past i ran memtest86 and got no errors. have not ran it since the last bsod problem though.
from these i gather that i needed to update my video card drivers which i did today. here is a complete specs of my pc.
mini dump file has been attached.
im only showing the file that was highlighted red. i think that is the only one that matters. (let me know if im wrong.)
they will be in the order that they happened with the most recent first.
092010-26863-01.dmp
091910-22292-01.dmp
091910-30872-01.dmp
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path ntoskrnl.exentoskrnl.exe+6fca9fffff800`02e09000fffff800`033e50000x005dc0000x4c1c44a96/18/2010 11:16:41 PMMicrosoft® Windows® Operating SystemNT Kernel & System6.1.7600.16617 (win7_gdr.100618-1621)Microsoft CorporationC:\Windows\system32\ntoskrnl.exe
091910-30872-01.dmp (the most recent crash)
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path dxgmms1.sysdxgmms1.sys+1e7c3fffff880`040b7000fffff880`040fd0000x000460000x4a5bc5787/13/2009 6:38:32 PM
windbg
first one is 092010-26863-01.dmp
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fad0bf, Address of the instruction which caused the bugcheck
Arg3: fffff88007386f90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExDeferredFreePool+233
fffff800`02fad0bf 4c395008 cmp qword ptr [rax+8],r10
CONTEXT: fffff88007386f90 -- (.cxr 0xfffff88007386f90)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800395b1d0
rdx=fffff8a00aa51840 rsi=0000000000000000 rdi=fffff8a0009efd40
rip=fffff80002fad0bf rsp=fffff88007387960 rbp=0000000000000000
r8=0000000000000000 r9=fffff8a00aa51840 r10=fffff8a00aa51850
r11=0000000000000001 r12=fffffa800395b000 r13=0000000000000000
r14=000000000000001d r15=0000000000000001
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
nt!ExDeferredFreePool+0x233:
fffff800`02fad0bf 4c395008 cmp qword ptr [rax+8],r10 ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: GSvr.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002fad0bf
STACK_TEXT:
fffff880`07387960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x233
FOLLOWUP_IP:
nt!ExDeferredFreePool+233
fffff800`02fad0bf 4c395008 cmp qword ptr [rax+8],r10
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+233
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff88007386f90 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+233
BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+233
Followup: Pool_corruption
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880040f0f0f, fffff88006c8e688, fffff88006c8def0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchGetNewSubmissionFenceId+4f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880040f0f0f, The address that the exception occurred at
Arg3: fffff88006c8e688, Exception Record Address
Arg4: fffff88006c8def0, 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!VidSchGetNewSubmissionFenceId+4f
fffff880`040f0f0f 4d85d2 test r10,r10
EXCEPTION_RECORD: fffff88006c8e688 -- (.exr 0xfffff88006c8e688)
ExceptionAddress: fffff880040f0f0f (dxgmms1!VidSchGetNewSubmissionFenceId+0x000000000000004f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003
CONTEXT: fffff88006c8def0 -- (.cxr 0xfffff88006c8def0)
rax=fffffa80064681a0 rbx=0000000000000000 rcx=000000000000bb40
rdx=0000000000000000 rsi=0000000000000003 rdi=fffffa800643f000
rip=fffff880040f0f0f rsp=fffff88006c8e8c8 rbp=0000000001788889
r8=0000000000000000 r9=fffff88006c8e988 r10=fffffa800558d010
r11=fffffa80063f9010 r12=0000000000000000 r13=0000000000000000
r14=fffffa8006000110 r15=0000000000000003
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!VidSchGetNewSubmissionFenceId+0x4f:
fffff880`040f0f0f 4d85d2 test r10,r10
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 0000000000000003
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c30e0
0000000000000003
FOLLOWUP_IP:
dxgmms1!VidSchGetNewSubmissionFenceId+4f
fffff880`040f0f0f 4d85d2 test r10,r10
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff880040d57c3 to fffff880040f0f0f
STACK_TEXT:
fffff880`06c8e8c8 fffff880`040d57c3 : 00000000`00000000 fffffa80`03b2e000 00000000`00000003 00000000`00000000 : dxgmms1!VidSchGetNewSubmissionFenceId+0x4f
fffff880`06c8e8d0 fffff880`040ef65d : 00000000`00000000 fffff8a0`01735500 fffffa80`00000000 fffffa80`06000110 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd2f
fffff880`06c8eaa0 fffff880`040ef398 : fffff880`02f67f40 fffff880`040eed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`06c8ec90 fffff880`040eee96 : 00000000`00000000 fffffa80`064681a0 00000000`00000080 fffffa80`063f9010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06c8ecc0 fffff800`0312fc06 : 00000000`0448e8c7 fffffa80`064174d0 fffffa80`039eb040 fffffa80`064174d0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06c8ed00 fffff800`02e69c26 : fffff880`02f63180 fffffa80`064174d0 fffff880`02f6dfc0 fffff880`01263a90 : nt!PspSystemThreadStartup+0x5a
fffff880`06c8ed40 00000000`00000000 : fffff880`06c8f000 fffff880`06c89000 fffff880`06c8e650 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidSchGetNewSubmissionFenceId+4f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff88006c8def0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VidSchGetNewSubmissionFenceId+4f
BUCKET_ID: X64_0x7E_dxgmms1!VidSchGetNewSubmissionFenceId+4f
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003171a4a, fffff880089f8fa0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003171a4a, Address of the instruction which caused the bugcheck
Arg3: fffff880089f8fa0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ObpLookupDirectoryEntry+16a
fffff800`03171a4a 396b10 cmp dword ptr [rbx+10h],ebp
CONTEXT: fffff880089f8fa0 -- (.cxr 0xfffff880089f8fa0)
rax=000000000000000a rbx=00fffff8a00a7ab7 rcx=fffff80003029d80
rdx=00000000843d4884 rsi=fffff8a003a88201 rdi=fffffa8003ed5498
rip=fffff80003171a4a rsp=fffff880089f9970 rbp=00000000b537894d
r8=000000000000000d r9=000000000000007d r10=000000000000007d
r11=0000000000000000 r12=fffff880089f9a70 r13=0000000000000001
r14=fffff8a00a5a6970 r15=fffff8a00a5a6920
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!ObpLookupDirectoryEntry+0x16a:
fffff800`03171a4a 396b10 cmp dword ptr [rbx+10h],ebp ds:002b:00fffff8`a00a7ac7=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: wmpnetwk.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003171a4a
STACK_TEXT:
fffff880`089f9970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupDirectoryEntry+0x16a
FOLLOWUP_IP:
nt!ObpLookupDirectoryEntry+16a
fffff800`03171a4a 396b10 cmp dword ptr [rbx+10h],ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpLookupDirectoryEntry+16a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff880089f8fa0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+16a
BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+16a
Followup: MachineOwner
---------from these i gather that i needed to update my video card drivers which i did today. here is a complete specs of my pc.
Code:
DVD
http://www.newegg.com/Product/Product.aspx?Item=N82E16827106289
CASE
http://www.newegg.com/Product/Product.aspx?Item=N82E16811119137
HD
http://www.newegg.com/Product/Product.aspx?Item=N82E16822136320
MONITOR
http://www.newegg.com/Product/Product.aspx?Item=N82E16824009145
VIDEO CARD
http://www.newegg.com/Product/Product.aspx?Item=N82E16814150359
PSU
http://www.newegg.com/Product/Product.aspx?Item=N82E16817341019
RAM
http://www.newegg.com/Product/Product.aspx?Item=N82E16820231166
MOBO
http://www.newegg.com/Product/Product.aspx?Item=N82E16813128358
CPU
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115041
Last edited:
