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: BSOD on Windows 7

30 Nov 2010   #1
Blizzkille

Windows 7 professional 64bit
 
 
BSOD on Windows 7

Hello!

I was hopping you could help me with my blue screen problem.
I have zipped it as the instruction.
Happy for all the help i can get!


My System SpecsSystem Spec
.
30 Nov 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Blizzkille View Post
Hello!

I was hopping you could help me with my blue screen problem.
I have zipped it as the instruction.
Happy for all the help i can get!

Two problems


1-sptd.sys used by alcohol and daemon tools almost always causes BSOD's

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


2- Symantec remove and replace with Microsoft Security Essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\113010-28017-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
Debug session time: Tue Nov 30 12:26:02.095 2010 (GMT-5)
System Uptime: 0 days 0:37:09.188
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80256762f0, 2, 1, fffff80002e8480c}

Unable to load image \SystemRoot\System32\Drivers\NISx64\1108000.005\SYMTDIV.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMTDIV.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDIV.SYS
Probably caused by : SYMTDIV.SYS ( SYMTDIV+7139 )

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: fffffa80256762f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e8480c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b70e0
 fffffa80256762f0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88009a773c0 -- (.trap 0xfffff88009a773c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8025676320
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e8480c rsp=fffff88009a77550 rbp=ffffffffffffffff
 r8=fffff80002e0f000  r9=0000000000000000 r10=fffffa8005897b80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx ds:34c0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7eca9 to fffff80002e7f740

STACK_TEXT:  
fffff880`09a77278 fffff800`02e7eca9 : 00000000`0000000a fffffa80`256762f0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09a77280 fffff800`02e7d920 : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09a773c0 fffff800`02e8480c : fffff880`09a77560 fffff880`09a77680 fffffa80`063a39b0 00000000`00000210 : nt!KiPageFault+0x260
fffff880`09a77550 fffff880`0424c686 : ffffffff`ffffffff fffffa80`05988b10 00000000`0000000e fffffa80`09154b70 : nt!ObfDereferenceObject+0x2c
fffff880`09a775b0 fffff880`0424c60a : 00000000`00000000 fffffa80`05988b10 fffff880`09a7982c fffff880`0424c6e5 : afd!AfdDerefPollInfoFileObjects+0x36
fffff880`09a775e0 fffff880`04241448 : 00000000`00000000 00000000`00000000 fffffa80`09154b70 00000000`00000001 : afd!AfdCompletePollIrp+0x9a
fffff880`09a77630 fffff880`0420588c : fffffa80`05988c18 00000000`00000000 00000000`00000000 fffffa80`0a3e41b0 : afd!AfdIndicatePollEvent+0x138
fffff880`09a77680 fffff880`042668a4 : 00000000`00000000 fffff880`09a77988 00000000`00000000 00000000`0000006e : afd!AfdReceiveDatagramEventCommonHandler+0x35c
fffff880`09a77720 fffff880`04327139 : fffffa80`05905bf4 fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e : afd!AfdReceiveDatagramEventHandler+0x124
fffff880`09a77810 fffffa80`05905bf4 : fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e 00000000`00000000 : SYMTDIV+0x7139
fffff880`09a77818 fffffa80`064e0cc0 : fffff880`069329ea fffffa80`0000006e 00000000`00000000 00000000`00000000 : 0xfffffa80`05905bf4
fffff880`09a77820 fffff880`069329ea : fffffa80`0000006e 00000000`00000000 00000000`00000000 fffffa80`0000006e : 0xfffffa80`064e0cc0
fffff880`09a77828 fffffa80`0000006e : 00000000`00000000 00000000`00000000 fffffa80`0000006e 00000000`0000006e : 0xfffff880`069329ea
fffff880`09a77830 00000000`00000000 : 00000000`00000000 fffffa80`0000006e 00000000`0000006e fffff880`09a779b8 : 0xfffffa80`0000006e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMTDIV+7139
fffff880`04327139 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  SYMTDIV+7139

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMTDIV

IMAGE_NAME:  SYMTDIV.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdfa4c3

FAILURE_BUCKET_ID:  X64_0xA_SYMTDIV+7139

BUCKET_ID:  X64_0xA_SYMTDIV+7139

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: fffffa80256762f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e8480c, address which referenced memory

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


WRITE_ADDRESS:  fffffa80256762f0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88009a773c0 -- (.trap 0xfffff88009a773c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8025676320
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e8480c rsp=fffff88009a77550 rbp=ffffffffffffffff
 r8=fffff80002e0f000  r9=0000000000000000 r10=fffffa8005897b80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx ds:34c0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7eca9 to fffff80002e7f740

STACK_TEXT:  
fffff880`09a77278 fffff800`02e7eca9 : 00000000`0000000a fffffa80`256762f0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09a77280 fffff800`02e7d920 : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09a773c0 fffff800`02e8480c : fffff880`09a77560 fffff880`09a77680 fffffa80`063a39b0 00000000`00000210 : nt!KiPageFault+0x260
fffff880`09a77550 fffff880`0424c686 : ffffffff`ffffffff fffffa80`05988b10 00000000`0000000e fffffa80`09154b70 : nt!ObfDereferenceObject+0x2c
fffff880`09a775b0 fffff880`0424c60a : 00000000`00000000 fffffa80`05988b10 fffff880`09a7982c fffff880`0424c6e5 : afd!AfdDerefPollInfoFileObjects+0x36
fffff880`09a775e0 fffff880`04241448 : 00000000`00000000 00000000`00000000 fffffa80`09154b70 00000000`00000001 : afd!AfdCompletePollIrp+0x9a
fffff880`09a77630 fffff880`0420588c : fffffa80`05988c18 00000000`00000000 00000000`00000000 fffffa80`0a3e41b0 : afd!AfdIndicatePollEvent+0x138
fffff880`09a77680 fffff880`042668a4 : 00000000`00000000 fffff880`09a77988 00000000`00000000 00000000`0000006e : afd!AfdReceiveDatagramEventCommonHandler+0x35c
fffff880`09a77720 fffff880`04327139 : fffffa80`05905bf4 fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e : afd!AfdReceiveDatagramEventHandler+0x124
fffff880`09a77810 fffffa80`05905bf4 : fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e 00000000`00000000 : SYMTDIV+0x7139
fffff880`09a77818 fffffa80`064e0cc0 : fffff880`069329ea fffffa80`0000006e 00000000`00000000 00000000`00000000 : 0xfffffa80`05905bf4
fffff880`09a77820 fffff880`069329ea : fffffa80`0000006e 00000000`00000000 00000000`00000000 fffffa80`0000006e : 0xfffffa80`064e0cc0
fffff880`09a77828 fffffa80`0000006e : 00000000`00000000 00000000`00000000 fffffa80`0000006e 00000000`0000006e : 0xfffff880`069329ea
fffff880`09a77830 00000000`00000000 : 00000000`00000000 fffffa80`0000006e 00000000`0000006e fffff880`09a779b8 : 0xfffffa80`0000006e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMTDIV+7139
fffff880`04327139 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  SYMTDIV+7139

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMTDIV

IMAGE_NAME:  SYMTDIV.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdfa4c3

FAILURE_BUCKET_ID:  X64_0xA_SYMTDIV+7139

BUCKET_ID:  X64_0xA_SYMTDIV+7139

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: fffffa80256762f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e8480c, address which referenced memory

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


WRITE_ADDRESS:  fffffa80256762f0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88009a773c0 -- (.trap 0xfffff88009a773c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8025676320
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e8480c rsp=fffff88009a77550 rbp=ffffffffffffffff
 r8=fffff80002e0f000  r9=0000000000000000 r10=fffffa8005897b80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02e8480c f0480fc11f      lock xadd qword ptr [rdi],rbx ds:34c0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7eca9 to fffff80002e7f740

STACK_TEXT:  
fffff880`09a77278 fffff800`02e7eca9 : 00000000`0000000a fffffa80`256762f0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09a77280 fffff800`02e7d920 : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09a773c0 fffff800`02e8480c : fffff880`09a77560 fffff880`09a77680 fffffa80`063a39b0 00000000`00000210 : nt!KiPageFault+0x260
fffff880`09a77550 fffff880`0424c686 : ffffffff`ffffffff fffffa80`05988b10 00000000`0000000e fffffa80`09154b70 : nt!ObfDereferenceObject+0x2c
fffff880`09a775b0 fffff880`0424c60a : 00000000`00000000 fffffa80`05988b10 fffff880`09a7982c fffff880`0424c6e5 : afd!AfdDerefPollInfoFileObjects+0x36
fffff880`09a775e0 fffff880`04241448 : 00000000`00000000 00000000`00000000 fffffa80`09154b70 00000000`00000001 : afd!AfdCompletePollIrp+0x9a
fffff880`09a77630 fffff880`0420588c : fffffa80`05988c18 00000000`00000000 00000000`00000000 fffffa80`0a3e41b0 : afd!AfdIndicatePollEvent+0x138
fffff880`09a77680 fffff880`042668a4 : 00000000`00000000 fffff880`09a77988 00000000`00000000 00000000`0000006e : afd!AfdReceiveDatagramEventCommonHandler+0x35c
fffff880`09a77720 fffff880`04327139 : fffffa80`05905bf4 fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e : afd!AfdReceiveDatagramEventHandler+0x124
fffff880`09a77810 fffffa80`05905bf4 : fffffa80`064e0cc0 fffff880`069329ea fffffa80`0000006e 00000000`00000000 : SYMTDIV+0x7139
fffff880`09a77818 fffffa80`064e0cc0 : fffff880`069329ea fffffa80`0000006e 00000000`00000000 00000000`00000000 : 0xfffffa80`05905bf4
fffff880`09a77820 fffff880`069329ea : fffffa80`0000006e 00000000`00000000 00000000`00000000 fffffa80`0000006e : 0xfffffa80`064e0cc0
fffff880`09a77828 fffffa80`0000006e : 00000000`00000000 00000000`00000000 fffffa80`0000006e 00000000`0000006e : 0xfffff880`069329ea
fffff880`09a77830 00000000`00000000 : 00000000`00000000 fffffa80`0000006e 00000000`0000006e fffff880`09a779b8 : 0xfffffa80`0000006e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMTDIV+7139
fffff880`04327139 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  SYMTDIV+7139

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMTDIV

IMAGE_NAME:  SYMTDIV.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdfa4c3

FAILURE_BUCKET_ID:  X64_0xA_SYMTDIV+7139

BUCKET_ID:  X64_0xA_SYMTDIV+7139

Followup: MachineOwner
---------
Ken J


My System SpecsSystem Spec
01 Dec 2010   #3
Blizzkille

Windows 7 professional 64bit
 
 

Thank you for the help!
will come back if it won´t work.
My System SpecsSystem Spec
.

04 Dec 2010   #4
Blizzkille

Windows 7 professional 64bit
 
 

Got a new BSOD this morning, any help would be nice!
My System SpecsSystem Spec
10 Dec 2010   #5
Blizzkille

Windows 7 professional 64bit
 
 
New BSOD

Hello

I posted a about a bluescreen about a week ago (https://www.sevenforums.com/crashes-d...ml#post1104920)
and i did what he said i should do, but it haven´t helped.
here is the latest BSOD.

Thanks for all the help
My System SpecsSystem Spec
10 Dec 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi, Blizzkille. Sorry that you are still having problems. I am going to ask the moderators to move this post into the original thread. This will keep confusion down make it easy to review what has been done so far.

Your most recent BSOD blames the Windows Direct X driver, which is very likely not the real cause. The dump indicates a memory conflict, which is caused by drivers many times.

ZigZag recommended that you uninstall sptd.sys and I still see this driver loaded on your system.
Quote:
1-sptd.sys used by alcohol and daemon tools almost always causes BSOD's

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


I also find the following out of date drivers loaded on your system. Those in red font are quite obsolete. Old drivers can and do cause memory corruption and BSOD's. Update the drivers from the links provided or uninstall the software or hardware they are associated with.
Quote:
Ctafiltv.sys Thu Aug 14 02:48:33 2008 - Creative Sound-Blaster-Arena-Surround-Driver. Creative Worldwide Support. Update this driver or rename it. It is obsolete.

hamachi.sys Thu Feb 19 05:36:41 2009 - LogMeIn Hamachi Virtual Network interface driver. https://secure.logmein.com/US/support/hamachi2/. Update this driver or uninstall LogMeIn.

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver. https://secure.logmein.com/US/home.aspx. This driver is obsolete. Uninstall LogMeIn.
My System SpecsSystem Spec
10 Dec 2010   #7
Blizzkille

Windows 7 professional 64bit
 
 

okey, thx
My System SpecsSystem Spec
10 Dec 2010   #8
Blizzkille

Windows 7 professional 64bit
 
 

I did as you told me, but i could not use the hamachi links you gave me,
so i reinstalled it.
but now i have a new BSOD, i have not seen before.
My System SpecsSystem Spec
10 Dec 2010   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I still see these obsolete drivers.
Quote:
Ctafiltv.sys Thu Aug 14 02:48:33 2008 - Creative Sound-Blaster-Arena-Surround-Driver. Creative Worldwide Support. Update this driver or rename it. It is obsolete.

hamachi.sys Thu Feb 19 05:36:41 2009 - LogMeIn Hamachi Virtual Network interface driver. https://secure.logmein.com/US/support/hamachi2/. Update this driver or uninstall LogMeIn.

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver. https://secure.logmein.com/US/home.aspx. This driver is obsolete. Uninstall LogMeIn.

I looked your three most recent dumps; all are dated today. All three are the same error code and blame the Windows system Direct X driver, which is very unlikely to be the real cause. Most likely, something, a driver, is causing conflicts. Outdated drivers frequently cause conflicts. Troubleshooting is a process of elimination. We need to eliminate all of the potential causes until we get your system stable.
Quote:
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Fri Dec 10 11:27:10.195 2010 (GMT-5)
System Uptime: 0 days 6:24:07.177
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a02245d7e0, 1, fffff88004401ebd, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+35 )

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

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

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: fffff8a02245d7e0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004401ebd, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f10e0
 fffff8a02245d7e0 

FAULTING_IP: 
dxgmms1!VidMmCloseAllocation+35
fffff880`04401ebd 488908          mov     qword ptr [rax],rcx

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800cb427c0 -- (.trap 0xfffff8800cb427c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a02245d7e0 rbx=0000000000000000 rcx=fffff8a00245d7e0
rdx=fffffa800672ce50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004401ebd rsp=fffff8800cb42950 rbp=0000000000000001
 r8=0000000000000000  r9=fffff880044118d0 r10=0000000000000018
r11=fffffa8007a4d3c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VidMmCloseAllocation+0x35:
fffff880`04401ebd 488908          mov     qword ptr [rax],rcx ds:28d8:fffff8a0`2245d7e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f388f2 to fffff80002eb9740

STACK_TEXT:  
fffff880`0cb42658 fffff800`02f388f2 : 00000000`00000050 fffff8a0`2245d7e0 00000000`00000001 fffff880`0cb427c0 : nt!KeBugCheckEx
fffff880`0cb42660 fffff800`02eb782e : 00000000`00000001 fffff8a0`0245d7e0 00000311`00000100 fffff900`c06c2a90 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0cb427c0 fffff880`04401ebd : fffffa80`05736060 fffff800`02f02fdc 00000000`00000000 fffff800`02ebf9a2 : nt!KiPageFault+0x16e
fffff880`0cb42950 fffff880`04515c10 : 00000000`00000000 fffff8a0`0ef61000 fffff8a0`0ef61000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x35
fffff880`0cb42980 fffff880`0451554b : fffff8a0`0ef61000 fffff8a0`0ef62300 fffff8a0`00000000 00000000`00000003 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0cb42a70 fffff880`0451b18f : 00000000`00000799 00000000`00000001 fffff880`0cb42ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0cb42ac0 fffff960`001db7b6 : 00000000`001de180 ffffffff`40000200 00000000`000007dc fffff8a0`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`0cb42bf0 fffff800`02eb8993 : fffffa80`05736060 00000000`000025c0 fffff880`0cb42bf8 fffffa80`080d6dd0 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0cb42c20 00000000`7422119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001de138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7422119a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmCloseAllocation+35
fffff880`04401ebd 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidMmCloseAllocation+35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmCloseAllocation+35

BUCKET_ID:  X64_0x50_dxgmms1!VidMmCloseAllocation+35

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

3: kd> lmtsmn
start             end                 module name
fffff880`04394000 fffff880`043d2000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`01038000 fffff880`0108f000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d40000 fffff880`02dca000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`051e8000 fffff880`051fe000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00fe9000 fffff880`00ff4000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`0892d000 fffff880`08938000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00fb6000 fffff880`00fbf000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fbf000 fffff880`00fe9000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`05002000 fffff880`0517f000   athrx    athrx.sys    Mon Oct 05 12:33:57 2009 (4ACA1FF5)
fffff880`05af7000 fffff880`05b17000   AtihdW76 AtihdW76.sys Mon Aug 16 06:41:02 2010 (4C6915BE)
fffff880`0480a000 fffff880`04fff000   atikmdag atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1)
fffff880`042c9000 fffff880`04314000   atikmpag atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF)
fffff960`00920000 fffff960`00981000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
fffff880`02c94000 fffff880`02c9b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`040a1000 fffff880`040b2000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`03daa000 fffff880`03dc8000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00640000 fffff960`00667000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`00e14000 fffff880`00e3e000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01216000 fffff880`01246000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d31000 fffff880`00d8f000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0521a000 fffff880`053dc000   cmudaxp  cmudaxp.sys  Mon Oct 19 05:10:53 2009 (4ADC2D1D)
fffff880`0148d000 fffff880`01500000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`051d8000 fffff880`051e8000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05b73000 fffff880`05b81000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04000000 fffff880`04083000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`05a6b000 fffff880`05a78000   Ctafiltv Ctafiltv.sys Thu Aug 14 02:48:33 2008 (48A3D541)
fffff880`05bc8000 fffff880`05bda000   dc3d     dc3d.sys     Thu Jul 01 06:07:45 2010 (4C2C68F1)
fffff880`04083000 fffff880`040a1000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04193000 fffff880`041a2000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`053dc000 fffff880`053fe000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05b8d000 fffff880`05b96000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05b81000 fffff880`05b8d000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05b96000 fffff880`05ba9000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05a44000 fffff880`05a50000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`044de000 fffff880`045d2000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04400000 fffff880`04446000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`00e00000 fffff880`00e14000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00d8f000 fffff880`00ddb000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01511000 fffff880`0151b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015b1000 fffff880`015eb000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0151b000 fffff880`01565000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`0518c000 fffff880`05199000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02e00000 fffff800`02e49000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04285000 fffff880`04290000   hamachi  hamachi.sys  Thu Feb 19 05:36:41 2009 (499D3639)
fffff880`04446000 fffff880`0446a000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05b17000 fffff880`05b73000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`05a00000 fffff880`05a19000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05bda000 fffff880`05be2080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05be3000 fffff880`05bf1000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`03ce2000 fffff880`03daa000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`016b5000 fffff880`016be000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`041a2000 fffff880`041b8000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`0429b000 fffff880`042aa000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05a19000 fffff880`05a27000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb9000 fffff800`00bc3000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04351000 fffff880`04394000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01473000 fffff880`0148d000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05200000 fffff880`05205200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`015eb000 fffff880`01600000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06360000 fffff880`06373000   LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)
fffff880`041b8000 fffff880`041db000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cd9000 fffff880`00d1d000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`05a78000 fffff880`05a86000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`042aa000 fffff880`042b9000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05a27000 fffff880`05a34000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f9c000 fffff880`00fb6000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02c5e000 fffff880`02c8b000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`088ac000 fffff880`088bc000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`03dc8000 fffff880`03de0000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03c00000 fffff880`03c2d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`062ef000 fffff880`0633d000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0633d000 fffff880`06360000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`02cf9000 fffff880`02d04000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0108f000 fffff880`01099000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01415000 fffff880`01473000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`04188000 fffff880`04193000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`016a3000 fffff880`016b5000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016c9000 fffff880`017bb000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043d2000 fffff880`043de000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`03cb7000 fffff880`03cca000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`04200000 fffff880`0422f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05ae2000 fffff880`05af7000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02df0000 fffff880`02dff000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c00000 fffff880`02c45000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02d04000 fffff880`02d15000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0417c000 fffff880`04188000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e49000 fffff800`03425000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01259000 fffff880`013fc000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02c8b000 fffff880`02c94000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03c64000 fffff880`03cb7000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`02dca000 fffff880`02df0000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`010a6000 fffff880`010bb000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ef6000 fffff880`00f29000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f85000 fffff880`00f8c000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f8c000 fffff880`00f9c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01500000 fffff880`01511000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06200000 fffff880`062a6000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05a34000 fffff880`05a44000   point64  point64.sys  Tue Jun 29 04:54:31 2010 (4C29B4C7)
fffff880`04314000 fffff880`04351000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d1d000 fffff880`00d31000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`045d2000 fffff880`045f6000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0422f000 fffff880`0424a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0424a000 fffff880`0426b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0426b000 fffff880`04285000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0412b000 fffff880`0417c000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04290000 fffff880`0429b000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`02cde000 fffff880`02ce7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02ce7000 fffff880`02cf0000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02cf0000 fffff880`02cf9000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`017bb000 fffff880`017f5000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`03cca000 fffff880`03ce2000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05199000 fffff880`051d8000   Rt64win7 Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
fffff880`01009000 fffff880`01038000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`062a6000 fffff880`062b1000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`05206000 fffff880`05212000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`040df000 fffff880`040fc000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0169b000 fffff880`016a3000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`010d6000 fffff880`011fc000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`08816000 fffff880`088ac000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`06385000 fffff880`063ec000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`062b1000 fffff880`062de000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`05212000 fffff880`05213480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`06373000 fffff880`06385000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02d33000 fffff880`02d40000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02d15000 fffff880`02d33000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`04117000 fffff880`0412b000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00580000 fffff960`0058a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`040b2000 fffff880`040d8000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`043de000 fffff880`043f0000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`08938000 fffff880`08949000   usbaapl64 usbaapl64.sys Thu Sep 16 22:19:05 2010 (4C92D019)
fffff880`05a50000 fffff880`05a6ac00   usbaudio usbaudio.sys Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`05ba9000 fffff880`05bc6000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`05bc6000 fffff880`05bc7f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`044cd000 fffff880`044de000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05a88000 fffff880`05ae2000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04477000 fffff880`044cd000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`0446a000 fffff880`04477000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`01099000 fffff880`010a6000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02c9b000 fffff880`02ca9000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02ca9000 fffff880`02cce000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0168b000 fffff880`0169b000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`010bb000 fffff880`010d0000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f29000 fffff880`00f85000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01565000 fffff880`015b1000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0517f000 fffff880`0518c000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`00ddb000 fffff880`00df1000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`040fc000 fffff880`04117000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02cce000 fffff880`02cde000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e43000 fffff880`00ee7000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ee7000 fffff880`00ef6000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02c45000 fffff880`02c4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00050000 fffff960`0035f000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
fffff880`01000000 fffff880`01009000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`041db000 fffff880`041fc000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`088bc000 fffff880`0892d000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`015eb000 fffff880`015f9000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01400000 fffff880`0140c000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`016be000 fffff880`016c7000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01246000 fffff880`01259000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Debug session time: Fri Dec 10 13:41:59.831 2010 (GMT-5)
System Uptime: 0 days 0:26:55.924
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8025a5fc00, 0, fffff80002ff50f3, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )

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

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

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: fffffa8025a5fc00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ff50f3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f80e0
 fffffa8025a5fc00 

FAULTING_IP: 
nt!ExFreePoolWithTag+43
fffff800`02ff50f3 418b45f0        mov     eax,dword ptr [r13-10h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880086c60e0 -- (.trap 0xfffff880086c60e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8025a5fc10
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ff50f3 rsp=fffff880086c6270 rbp=0000000000000001
 r8=0000000000000001  r9=0000000000000090 r10=fffff80002e50000
r11=fffff88004240a08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExFreePoolWithTag+0x43:
fffff800`02ff50f3 418b45f0        mov     eax,dword ptr [r13-10h] ds:07ff:ffffffff`fffffff0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f3f8f2 to fffff80002ec0740

STACK_TEXT:  
fffff880`086c5f78 fffff800`02f3f8f2 : 00000000`00000050 fffffa80`25a5fc00 00000000`00000000 fffff880`086c60e0 : nt!KeBugCheckEx
fffff880`086c5f80 fffff800`02ebe82e : 00000000`00000000 fffffa80`07e92da0 00000000`00000000 fffff800`02f0a113 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`086c60e0 fffff800`02ff50f3 : 00000000`00000000 fffff8a0`0b0668b0 00000000`6d4d6956 fffff880`00000174 : nt!KiPageFault+0x16e
fffff880`086c6270 fffff880`043315ec : 00000000`00000000 00000000`00000001 fffff8a0`100a2ac0 00000000`00000001 : nt!ExFreePoolWithTag+0x43
fffff880`086c6320 fffff880`04317ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x264
fffff880`086c63f0 fffff880`04259c10 : 00000000`00000000 fffff8a0`028f9000 fffff8a0`028f9000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`086c6420 fffff880`0425954b : fffff8a0`028f9000 fffff8a0`028fa300 fffff8a0`00000000 000009c0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`086c6510 fffff880`04287647 : fffff8a0`10128260 fffff8a0`0af6d4e0 fffff8a0`10128260 fffff880`086c6930 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`086c6560 fffff880`04286d73 : fffff8a0`00000799 fffff8a0`10128260 fffff880`086c68c0 fffff880`086c68f0 : dxgkrnl!DXGCONTEXT::Present+0x2cb
fffff880`086c6880 fffff960`0024baf0 : fffffa80`0753ba10 00000000`7efdb000 fffff8a0`0dbcf8d0 00000000`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`086c6bf0 fffff800`02ebf993 : fffffa80`0753ba10 00000000`000029b8 fffff880`086c6bf8 fffffa80`0583c4b0 : win32k!NtGdiDdDDIPresent+0x18
fffff880`086c6c20 00000000`746713ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ed938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x746713ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
fffff880`043315ec 488b4b20        mov     rcx,qword ptr [rbx+20h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

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

Debug session time: Fri Dec 10 12:04:22.815 2010 (GMT-5)
System Uptime: 0 days 0:35:47.908
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a023505540, 0, fffff88004201c59, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmTerminateAllocation+13d )

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

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

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: fffff8a023505540, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004201c59, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030be0e0
 fffff8a023505540 

FAULTING_IP: 
dxgmms1!VidMmTerminateAllocation+13d
fffff880`04201c59 488b4810        mov     rcx,qword ptr [rax+10h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800be255e0 -- (.trap 0xfffff8800be255e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a023505530 rbx=0000000000000000 rcx=fffff8800be257b8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004201c59 rsp=fffff8800be25770 rbp=fffffa8007f4e710
 r8=0000000000000000  r9=0000000000000000 r10=fffff88003115a60
r11=fffff8a0167ba780 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidMmTerminateAllocation+0x13d:
fffff880`04201c59 488b4810        mov     rcx,qword ptr [rax+10h] ds:da9b:fffff8a0`23505540=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f058f2 to fffff80002e86740

STACK_TEXT:  
fffff880`0be25478 fffff800`02f058f2 : 00000000`00000050 fffff8a0`23505540 00000000`00000000 fffff880`0be255e0 : nt!KeBugCheckEx
fffff880`0be25480 fffff800`02e8482e : 00000000`00000000 fffffa80`07732000 00000000`00000000 fffff880`04b92f60 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0be255e0 fffff880`04201c59 : fffffa80`00000174 fffffa80`07732000 fffffa80`086e29a0 00000000`000007ff : nt!KiPageFault+0x16e
fffff880`0be25770 fffff880`0431f8d2 : fffff8a0`024f9000 fffff8a0`024f9000 00000000`00000001 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x13d
fffff880`0be25850 fffff880`043236e0 : fffff8a0`10fa9700 fffff880`0be25ca0 fffffa80`0771f000 fffff880`042ea3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0x166
fffff880`0be258a0 fffff880`04325d9b : fffff8a0`024f9000 fffff880`0be259b0 00000000`7ef29001 fffff880`042eb001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0be25930 fffff960`0022b822 : 00000000`7ef29000 fffffa80`0565f810 00000000`00000020 00000000`74ff5f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0be25bf0 fffff800`02e85993 : fffffa80`0565f810 00000000`000025c4 00000000`00000000 fffffa80`0685c8d0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0be25c20 00000000`7501120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06e1e448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7501120a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmTerminateAllocation+13d
fffff880`04201c59 488b4810        mov     rcx,qword ptr [rax+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidMmTerminateAllocation+13d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmTerminateAllocation+13d

BUCKET_ID:  X64_0x50_dxgmms1!VidMmTerminateAllocation+13d

Followup: MachineOwner
---------
My System SpecsSystem Spec
16 Dec 2010   #10
Blizzkille

Windows 7 professional 64bit
 
 

Got some1 more BSODs this morning.
Have uninstalled all the everything you said.
have to see if it helps.

Thanks for the help!
My System SpecsSystem Spec
Reply

 BSOD on Windows 7




Thread Tools




Similar help and support threads
Thread Forum
BSOD on Windows Update; BSOD when playing games
NOTE: DM log collector seem to be getting stuck when collecting msinfo32.nfo, so the attached file can be incomplete. Please let me know if it can take longer than 10 minutes to collect this data so i will run the program again. BSOD #1: It started at around January 15th - basically when i shoot...
BSOD Help and Support
BSOD using FULL windows 7, no BSOD using safe mode
My computer has been stable for years, however recently I have been getting BSOD when doing any task. Windows will sometimes load to the desktop and I am able to watch video, run windows score, check email, etc before it will BSOD. Other times, it will BSOD before getting to the windows login...
BSOD Help and Support
BSOD trying to start Windows, gets to desktop then BSOD, then reboots
Hi guys, I encountered BSOD for the first time. Very annoying. Right now I have to run this on Safe Mode in order to access the internet. I also noticed I can't use Firefox right now, and instead am using iE. I couldn't run the the performance scan report either (time out?), but I did attach the...
BSOD Help and Support
lots of BSOD - Format, Clean windows install - Still same BSOD
Hi, I use a 1.5 year old aces aspire 5738z and I think it just died on me. Here is what happens. Whatever I do it cannot stay without a BSOD for more than 10 minutes. I tried reinstalling drivers and it did not change anything so I tried several things but finally just formated it and installed...
BSOD Help and Support
BSOD Starting Windows Virtual PC Machines (any machine, always bsod)
Hello All, I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last...
BSOD Help and Support
Windows crash (BSOD without BSOD) nVidia
Hello! I have been expiriencing problems with my computer which are as follows: I do my thing on the computer (surf, play etc.) and suddently my screen goes black. It has been doing this for about a week now, and I received my new SSDs recently so I popped them in, put them in RAID-0 and...
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 22:59.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App