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: WIN7 64 BIT BSOD debugging help


29 Nov 2009   #1

win7 64 Ultimate retail
 
 
WIN7 64 BIT BSOD debugging help

Lo All

any one here any good at debugging as lately been getting some BSOD's but not sure what they are from even using windows debugger. i have zipped up and attached a mini dump

so any help would be great
thanks all

Ian

My System SpecsSystem Spec
.

29 Nov 2009   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mrbudgie View Post
Lo All

any one here any good at debugging as lately been getting some BSOD's but not sure what they are from even using windows debugger. i have zipped up and attached a mini dump

so any help would be great
thanks all

Ian

Hi and welcome

As usual this 64bit dmp was probably cased by the video driver.

I would update the video driver
and just for giggles I would run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP
if you have a raid update its driver


Hope this helps

Kenn J+



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\112909-17721-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e50
Debug session time: Sun Nov 29 13:19:39.406 2009 (GMT-5)
System Uptime: 0 days 1:18:26.326
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa3205acfc98, 2, 0, fffff80002e7af9f}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8 )


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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:

Arg1: fffffa3205acfc98, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e7af9f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad0e0
fffffa3205acfc98

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+10f
fffff800`02e7af9f 488b09 mov rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe


TRAP_FRAME: fffff88009dc8ce0 -- (.trap 0xfffff88009dc8ce0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005a41580 rbx=0000000000000000 rcx=fffffa3205acfc98
rdx=fffffa3205acfc98 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e7af9f rsp=fffff88009dc8e70 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa8004e42580
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!KeSetEvent+0x10f:
fffff800`02e7af9f 488b09 mov rcx,qword ptr [rcx] ds:1010:fffffa32`05acfc98=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e76469 to fffff80002e76f00

STACK_TEXT:
fffff880`09dc8b98 fffff800`02e76469 : 00000000`0000000a fffffa32`05acfc98 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09dc8ba0 fffff800`02e750e0 : 00000000`00000000 fffffa80`05a41578 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09dc8ce0 fffff800`02e7af9f : 00000000`0000000f 00000000`0000000f fffffa80`04e42501 fffffa80`04e42580 : nt!KiPageFault+0x260
fffff880`09dc8e70 fffff880`04f6d9a0 : fffffa80`00000000 fffffa80`00000000 fffffa80`03b80900 fffffa80`05a41010 : nt!KeSetEvent+0x10f
fffff880`09dc8ee0 fffff880`04f706fd : 00000000`00000001 fffffa80`04e42768 fffff880`09dc9140 00000000`00000000 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1d8
fffff880`09dc8f50 fffff880`04eaf520 : 00000000`00000000 00000000`00000200 fffff880`09dc97b0 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x3ad
fffff880`09dc8fb0 00000000`00000000 : 00000000`00000200 fffff880`09dc97b0 00000000`00000000 00000000`00000001 : dxgkrnl+0x70520


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
fffff880`04f6d9a0 4c8d5c2440 lea r11,[rsp+40h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8

BUCKET_ID: X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 Nov 2009   #3

win7 64 Ultimate retail
 
 

i am using the latest one from ati

anything else that stands out in the file
My System SpecsSystem Spec
.


29 Nov 2009   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mrbudgie View Post
i am using the latest one from ati

anything else that stands out in the file
If you google that driver it is notorius for bein a pain. I think there is a specific method of un-installing and re-installing it. You might also want to search here at SF. I seem to remember something here about it

Ken J+
My System SpecsSystem Spec
29 Nov 2009   #5

win7 64 Ultimate retail
 
 

what is the driver name exactly so i can google it
My System SpecsSystem Spec
30 Nov 2009   #6

win7 64 Ultimate retail
 
 

driver sweeped the old driver out the way for the vid card reinstalled and though it was all dandy but just got this one (file attached) any clue what caused it

thanks ian
My System SpecsSystem Spec
30 Nov 2009   #7

7600.20510 x86
 
 

"Memory corruption"

Update these drivers:

AODDriver AODDriver.sys Mon Oct 13 00:38:55 2008
cmudaxp cmudaxp.sys Mon Mar 26 07:13:37 2007
GVTDrv64 GVTDrv64.sys Tue Sep 05 03:10:02 2006

If doing that doesn't help, find the correct Vdimm, timings and frequency for your RAM modules and set the motherboard bios for that. Visit RAM maker's site for info. Use CPU-Z spd tab to find out which modules you have.

If still not good, run Memtest86+ overnight to test.

Reinstall the ATI driver but this time, let it also update your HDMI. Use custom mode to install.
My System SpecsSystem Spec
30 Nov 2009   #8

win7 64 Ultimate retail
 
 

also just unistalled AVG just incase but any help with the latest dump would be appreciated

thanks ian
My System SpecsSystem Spec
30 Nov 2009   #9

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mrbudgie View Post
what is the driver name exactly so i can google it

dxgmms1.sys

Ken
My System SpecsSystem Spec
30 Nov 2009   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by torrentg View Post
"Memory corruption"

Update these drivers:

AODDriver AODDriver.sys Mon Oct 13 00:38:55 2008
cmudaxp cmudaxp.sys Mon Mar 26 07:13:37 2007
GVTDrv64 GVTDrv64.sys Tue Sep 05 03:10:02 2006

If doing that doesn't help, find the correct Vdimm, timings and frequency for your RAM modules and set the motherboard bios for that. Visit RAM maker's site for info. Use CPU-Z spd tab to find out which modules you have.

If still not good, run Memtest86+ overnight to test.

Reinstall the ATI driver but this time, let it also update your HDMI. Use custom mode to install.

My collegue is right as usual. there is a memory problem. till you solve that you are going to keep having these "random" BSOD's

Ken J+
My System SpecsSystem Spec
Reply

 WIN7 64 BIT BSOD debugging help




Thread Tools



Similar help and support threads for2: WIN7 64 BIT BSOD debugging help
Thread Forum
Debugging A BSOD - My way Crash and lockup debug 'How To'
BSOD Needs debugging BSOD Help and Support
Debugging of BSOD problem BSOD Help and Support
Solved BSOD, need help with debugging. BSOD Help and Support
Bsod Debugging BSOD Help and Support
Suddenly lots of bsod in Win7, some help with debugging please? 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 08:21 PM.
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