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 report

25 Jan 2011   #1
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
Bsod report

Heya, this is my 1st post

OS : Windows 7 Professional 64 bits
CPU Amd Phenom B50 Quad Core 3,2 Ghz
Memory 6 GB RAM DDR 3 1337 Ghz
Graphics Card HIS ATI Radeon HD 5670 1GB GDDR 5

and it`s an brand new PC ! I just bought it.


My System SpecsSystem Spec
.
25 Jan 2011   #2
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

again bosd... bsod daily !! verry annoying ! can anyone help me ? :/
My System SpecsSystem Spec
25 Jan 2011   #3
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi, tDaniel and welcome to the forum. I got a good chuckle out of your System name - ERROR.

I looked at all four of your dumps. All are bugcheck 50, PAGE_FAULT_IN_NONPAGED_AREA and all show memory corruption. One of the dumps direct blames klif.sys, a Kaspersky driver. I recommend that you completely uninstall Kaspersky using this removal tool: Tool. Kaspersky is a known cause of BSOD's on some Win 7 systems. Once you get your system stable, you can try it again. But get the latest version; you version has two outdated drivers. Do not reinstall it. In the meantime, while you are troubleshooting, download and install Microsoft Security Essentials. It runs smoothly with Win 7. Here is a list of your out of date Kaspersky drivers
Quote:
kl1.sys Thu Jan 22 05:30:38 2009
klfltdev.sys Tue Dec 23 07:46:36 2008
klif.sys Fri Apr 03 02:50:13 2009
klim6.sys Tue Jan 27 08:09:55 2009
Also, uninstall Gigabyte's Easy Saver program, as it is known to cause BSODs. The driver is out of date.
Quote:
gdrv.sys Thu Mar 12 23:22:29 2009

Uninstall Kaspersky and Easy Saver, reboot and see how your system rums. Post back and let us know. If you get another BSOD, upload it and we will go from there.

Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`0348ce50
Debug session time: Mon Jan 24 08:58:49.916 2011 (GMT-5)
System Uptime: 0 days 4:10:55.446
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8a00bee1af8, 0, fffff88000faafa9, 7}

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys

Could not read faulting driver name
Probably caused by : klif.sys ( klif+cef9 )

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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f70e0
 ffffd8a00bee1af8 

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`00faafa9 488b4820        mov     rcx,qword ptr [rax+20h]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dllhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800aca6170 -- (.trap 0xfffff8800aca6170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8a00bee1ad8 rbx=0000000000000000 rcx=ffffd8a00bee1ad8
rdx=fffffa8006685c10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000faafa9 rsp=fffff8800aca6300 rbp=fffff8800aca6480
 r8=0000000000000000  r9=fffff8800aca63e0 r10=fffffa8005f8d3a8
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`00faafa9 488b4820        mov     rcx,qword ptr [rax+20h] ds:ffffd8a0`0bee1af8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000333e849 to fffff800032bf740

STACK_TEXT:  
fffff880`0aca6008 fffff800`0333e849 : 00000000`00000050 ffffd8a0`0bee1af8 00000000`00000000 fffff880`0aca6170 : nt!KeBugCheckEx
fffff880`0aca6010 fffff800`032bd82e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000142 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`0aca6170 fffff880`00faafa9 : 00000000`00000000 00000000`00000000 fffff880`0aca63b0 fffff880`00faa32e : nt!KiPageFault+0x16e
fffff880`0aca6300 fffff880`00fb5d4e : fffffa80`05f8d3a0 fffff880`0aca63e0 fffff880`0aca6430 fffffa80`06636470 : fltmgr!GetContextFromStreamList+0x99
fffff880`0aca6380 fffff880`02aaaef9 : fffffa80`05f8d3a0 00000000`00000000 fffff8a0`0aadd970 fffff880`00faf2c6 : fltmgr!FltGetStreamContext+0x3e
fffff880`0aca63b0 fffffa80`05f8d3a0 : 00000000`00000000 fffff8a0`0aadd970 fffff880`00faf2c6 fffff880`0aca6578 : klif+0xcef9
fffff880`0aca63b8 00000000`00000000 : fffff8a0`0aadd970 fffff880`00faf2c6 fffff880`0aca6578 fffff880`0aca6538 : 0xfffffa80`05f8d3a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
klif+cef9
fffff880`02aaaef9 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  klif+cef9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klif

IMAGE_NAME:  klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49d5b1a5

FAILURE_BUCKET_ID:  X64_0x50_klif+cef9

BUCKET_ID:  X64_0x50_klif+cef9

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

Debug session time: Tue Jan 25 08:15:44.479 2011 (GMT-5)
System Uptime: 0 days 0:54:28.009
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8a00ea31180, 0, fffff800033a400e, 7}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+182 )

Followup: Pool_corruption
---------

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034a80e0
 ffffd8a00ea31180 

FAULTING_IP: 
nt!ExDeferredFreePool+182
fffff800`033a400e 4c3910          cmp     qword ptr [rax],r10

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002f9a5a0 -- (.trap 0xfffff88002f9a5a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8a00ea31180 rbx=0000000000000000 rcx=fffffa80051796f0
rdx=fffff8a00ace89b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033a400e rsp=fffff88002f9a730 rbp=0000000000000000
 r8=fffff8a00ce41690  r9=fffff8a00ace8980 r10=fffff8a00ace8990
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeferredFreePool+0x182:
fffff800`033a400e 4c3910          cmp     qword ptr [rax],r10 ds:0423:ffffd8a0`0ea31180=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032ef849 to fffff80003270740

STACK_TEXT:  
fffff880`02f9a438 fffff800`032ef849 : 00000000`00000050 ffffd8a0`0ea31180 00000000`00000000 fffff880`02f9a5a0 : nt!KeBugCheckEx
fffff880`02f9a440 fffff800`0326e82e : 00000000`00000000 00000000`00000004 fffffa80`0593f600 fffffa80`05ff7650 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`02f9a5a0 fffff800`033a400e : 00000000`00000100 fffff880`02f9a710 00000000`00000002 fffff8a0`0ea217a0 : nt!KiPageFault+0x16e
fffff880`02f9a730 fffff800`033a54c1 : fffff8a0`0ea54ae0 fffff8a0`0ea54a00 00000000`000007ff 00000000`000000c0 : nt!ExDeferredFreePool+0x182
fffff880`02f9a7c0 fffff880`00c58513 : ffffffff`ffffffff fffff8a0`0e7a12a0 fffffa80`6e664d46 fffff880`00c4366e : nt!ExFreePoolWithTag+0x411
fffff880`02f9a870 fffff880`00c5ac51 : fffffa80`05434750 fffffa80`062a3800 00000000`00000130 fffff8a0`0ea217a0 : fltmgr!DeleteNameCacheNodes+0x143
fffff880`02f9a8b0 fffff880`00c5abe8 : fffffa80`062a3800 00000000`00000130 fffff8a0`0ea217a0 fffff8a0`0ea217a0 : fltmgr!FltpFreeNameCacheList+0x21
fffff880`02f9a8f0 fffff880`00c5ab7b : fffffa80`062a3800 fffff8a0`0ea21a08 fffffa80`062a3800 fffff800`03246c1a : fltmgr!CleanupStreamListCtrl+0x48
fffff880`02f9a920 fffff800`0355f896 : 00000000`00000001 fffff880`010ab0b8 fffff8a0`0ea218d0 fffff880`0101e6e1 : fltmgr!DeleteStreamListCtrlCallback+0x6b
fffff880`02f9a950 fffff880`010aabcc : fffff8a0`0ea217a0 fffffa80`052021a0 fffff880`02f9aa28 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2
fffff880`02f9a9a0 fffff880`010aa8d5 : fffffa00`01000000 00000000`00000000 fffff800`03415500 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108
fffff880`02f9a9e0 fffff880`0101dcb4 : fffff8a0`0ea216a0 fffff8a0`0ea217a0 fffff800`03415500 fffff880`02f9ab52 : Ntfs!NtfsRemoveScb+0x61
fffff880`02f9aa20 fffff880`010a82dc : fffff8a0`0ea21670 fffff800`034155a0 fffff880`02f9ab52 fffffa80`0859c1a0 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`02f9aa50 fffff880`01026882 : fffffa80`0859c1a0 fffffa80`0859c1a0 fffff8a0`0ea21670 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`02f9aad0 fffff880`010bf813 : fffffa80`0859c1a0 fffff800`034155a0 fffff8a0`0ea21670 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`02f9ab10 fffff880`0109938f : fffffa80`0859c1a0 fffff8a0`0ea217a0 fffff8a0`0ea21670 fffffa80`06370180 : Ntfs!NtfsCommonClose+0x353
fffff880`02f9abe0 fffff800`0327d961 : 00000000`00000000 fffff880`01099200 fffff800`03477101 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`02f9acb0 fffff800`03514c06 : 00000000`00000000 fffffa80`052021a0 00000000`00000080 fffffa80`051889e0 : nt!ExpWorkerThread+0x111
fffff880`02f9ad40 fffff800`0324ec26 : fffff880`02d63180 fffffa80`052021a0 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f9ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+182
fffff800`033a400e 4c3910          cmp     qword ptr [rax],r10

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExDeferredFreePool+182

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!ExDeferredFreePool+182

BUCKET_ID:  X64_0x50_nt!ExDeferredFreePool+182

Followup: Pool_corruption
---------


My System SpecsSystem Spec
.

26 Jan 2011   #4
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

again bsod, here`s the dump file
My System SpecsSystem Spec
26 Jan 2011   #5
Jonathan_King

Windows 7 Professional x64
 
 

Run driver verifier: Driver Verifier - Enable and Disable

Also run some hardware diagnostics.

Run Memtest86 overnight: RAM - Test with Memtest86+

Run the Blend and Small FFTs Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 26 07:16:13.471 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:52.000
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+ca )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MmUnmapViewInSystemCache+ca
SystemProductName = GA-MA770T-UD3
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
26 Jan 2011   #6
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
Run driver verifier: Driver Verifier - Enable and Disable

Also run some hardware diagnostics.

Run Memtest86 overnight: RAM - Test with Memtest86+

Run the Blend and Small FFTs Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 26 07:16:13.471 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:52.000
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+ca )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MmUnmapViewInSystemCache+ca
SystemProductName = GA-MA770T-UD3
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  

I did the verifier thing but about RAM or CPU problems, I don`t think so, because it`s brand new components, directly from the shop, so any other suggestions ?
My System SpecsSystem Spec
26 Jan 2011   #7
Jonathan_King

Windows 7 Professional x64
 
 

Keep verifier enabled for a while, see if it detects any bad drivers.

RAM and CPU, like any electronic component, has a certain chance of being defective. It's good to run those tests now, because if they fail, you can RMA them for a replacement.
My System SpecsSystem Spec
26 Jan 2011   #8
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

another bsod
My System SpecsSystem Spec
26 Jan 2011   #9
tDaniel

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

again bsod
My System SpecsSystem Spec
26 Jan 2011   #10
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Your dumps are the same bugcheck, 50; both blame the Windows Direct X driver, which is unlikely to be the real cause. The first of your two dumps is a Driver Verifier enabled dump. The second is not.

I agree with Jonathan; I think you should follow his suggestions and test your hardware carefully following the instructions in the tutorials he linked to. Post back with your tests results.
Code:
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0325a000 PsLoadedModuleList = 0xfffff800`03497e50
Debug session time: Wed Jan 26 11:26:55.638 2011 (GMT-5)
System Uptime: 0 days 2:04:45.573
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8a00b9ee530, 0, fffff88004f7205b, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035020e0
 ffffd8a00b9ee530 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`04f7205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88001ffe740 -- (.trap 0xfffff88001ffe740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8a00b9ee530 rbx=0000000000000000 rcx=fffff8a00b9ee548
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004f7205b rsp=fffff88001ffe8d0 rbp=000000000009ef1d
 r8=0000000000000003  r9=0000000000000003 r10=0000000000000018
r11=fffffa8007ce93c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b:
fffff880`04f7205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp ds:0010:ffffd8a0`0b9ee530=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003349849 to fffff800032ca740

STACK_TEXT:  
fffff880`01ffe5d8 fffff800`03349849 : 00000000`00000050 ffffd8a0`0b9ee530 00000000`00000000 fffff880`01ffe740 : nt!KeBugCheckEx
fffff880`01ffe5e0 fffff800`032c882e : 00000000`00000000 fffff8a0`0b9f0de0 00000000`00000000 00001f80`01008c40 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`01ffe740 fffff880`04f7205b : fffff8a0`0b9f0de0 fffffa80`06841ba0 fffffa80`07ce8000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`01ffe8d0 fffff880`04f6f8af : 00000000`00000000 fffffa80`06355608 00000000`0000019b fffffa80`067a4220 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b
fffff880`01ffe910 fffff880`04f8965d : 00000000`00000000 fffff8a0`0b96a500 fffffa80`00000000 fffffa80`09212af0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`01ffeae0 fffff880`04f89398 : fffff800`00b96080 fffff880`04f88d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`01ffecd0 fffff880`04f88e96 : 00000000`00000000 fffffa80`0819d340 00000000`00000080 fffffa80`07add410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`01ffed00 fffff800`0356ec06 : 00000000`034779a5 fffffa80`07ae4620 fffffa80`051a4890 fffffa80`07ae4620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`01ffed40 fffff800`032a8c26 : fffff800`03444e80 fffffa80`07ae4620 fffff800`03452c40 512f344b`66326573 : nt!PspSystemThreadStartup+0x5a
fffff880`01ffed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`04f7205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

BUCKET_ID:  X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

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

Debug session time: Wed Jan 26 12:29:00.850 2011 (GMT-5)
System Uptime: 0 days 1:01:28.380
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8a0049b44e0, 1, fffff88004801983, 7}


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

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

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f50e0
 ffffd8a0049b44e0 

FAULTING_IP: 
dxgmms1!VidMmDestroyAllocation+43
fffff880`04801983 4c8908          mov     qword ptr [rax],r9

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  rift.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007f20600 -- (.trap 0xfffff88007f20600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8a0049b44e0 rbx=0000000000000000 rcx=fffffa80073af000
rdx=fffff8a00243d130 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004801983 rsp=fffff88007f20790 rbp=fffffa80073af000
 r8=fffff8a008408830  r9=fffff8a0049b44e0 r10=0000000000000000
r11=fffff8800196d120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VidMmDestroyAllocation+0x43:
fffff880`04801983 4c8908          mov     qword ptr [rax],r9 ds:ffffd8a0`049b44e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000333c849 to fffff800032bd740

STACK_TEXT:  
fffff880`07f20498 fffff800`0333c849 : 00000000`00000050 ffffd8a0`049b44e0 00000000`00000001 fffff880`07f20600 : nt!KeBugCheckEx
fffff880`07f204a0 fffff800`032bb82e : 00000000`00000001 fffff8a0`049b44e0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`07f20600 fffff880`04801983 : fffffa80`066d2040 fffff880`07f207e0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07f20790 fffff880`05140fb3 : 00000000`00000000 00000000`00000000 fffff8a0`02444000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x43
fffff880`07f207c0 fffff880`0515367c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
fffff880`07f208b0 fffff880`05138815 : 00000000`fffffeda fffff8a0`04796770 fffff8a0`02444000 fffffa80`073a7000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`07f20920 fffff880`05176ca6 : 00000000`00000000 fffffa80`073a7000 fffff8a0`04796770 fffff8a0`047967f0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`07f20950 fffff880`0517663c : fffff900`c2c1cce0 00000000`00000000 00000000`00000001 fffff900`c2c1cce0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`07f20a00 fffff960`001a4c44 : 00000000`00000dac fffff900`c2c1cce0 00000000`00000000 fffff900`c2c1cce0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`07f20a90 fffff960`001a4337 : fffffa80`07167900 00000000`00000001 fffffa80`07865060 00000000`00000000 : win32k!GdiProcessCallout+0x244
fffff880`07f20b10 fffff800`035a2a01 : fffffa80`07167960 00000000`00000000 00000000`00000000 fffffa80`07865060 : win32k!W32pProcessCallout+0x6b
fffff880`07f20b40 fffff800`0357a85b : 00000000`c0000005 00000000`00000001 fffffa80`05852000 00000000`00000000 : nt!PspExitThread+0x561
fffff880`07f20c00 fffff800`032bc993 : fffffa80`05852060 fffff880`c0000005 ffffdf06`ba626efb fffffa80`07865060 : nt!NtTerminateProcess+0x25b
fffff880`07f20c80 fffff800`032b8f30 : fffff800`032f7dbc fffff880`07f21a00 fffff880`07f21350 fffff880`07f21c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07f20e18 fffff800`032f7dbc : fffff880`07f21a00 fffff880`07f21350 fffff880`07f21c20 00000000`00000002 : nt!KiServiceLinkage
fffff880`07f20e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x53b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmDestroyAllocation+43
fffff880`04801983 4c8908          mov     qword ptr [rax],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidMmDestroyAllocation+43

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43

BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 Bsod report




Thread Tools




Similar help and support threads
Thread Forum
BSODs while idle; Driver Verifier report report available
I'll try and make this concise: BSODs occur even while desktop is not in use. Memory_Management and PFN_LIST_CORRUPT is what I remember seeing. Also: IE9, IE10 and IE11 all "stop working" randomly. Chrome - ditto. FF32 - ditto. I've run Memtest86 (10 passes) no errors. The last BSOD was...
BSOD Help and Support
BSOD Plannetside 2 (steam) black screen> reboot> BSOD crash report
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 2057 Additional information about the problem: BCCode: 116 BCP1: FFFFFA8010C69010 BCP2: FFFFF880069CD6AC BCP3: FFFFFFFFC000009A
BSOD Help and Support
Yet another BSOD report
I have googled my error numbers, and could not find anything. I hope you guys can help me. I have Windows 7 Ultimate x64. I have run temperature and memory tests and it all looked good. My Disk drive test failed, but I used the Seagate tool to "repair" it, and it passes now. The reason I...
BSOD Help and Support
BSOD Report
Hello, and thanks in advance for any help someone can offer to me. To answer the basic system information questions: - I'm running Windows 7 x64. - It's an upgrade copy, so I'm fairly sure it was installed on top of Vista (can't really remember, to be honest) - Full retail upgrade version,...
BSOD Help and Support
my last BSOD report
hello there, i was waiting for almost 2 days but there was no respone and reply, so i post another new one.. Actually there's no more BSOD appear few last days, but im just curious if there was anything wrong with my comp,, so here is the attachment, my last perfmon report, please take a...
BSOD Help and Support
Random BSOD... Help please (BSOD dump & system health report attached)
Hello. I am experiencing some random BSODs. It happens no matter what program is running. It could be in a game, surfing the internet, or listening to music. It is very random. Happens about once every two days on average. Some days are worse. I have tried running driver verifier, but it would...
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 10:23.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App