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 - Crashes Constantly / Dumps attached

28 Dec 2010   #21
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hello again,

Ive gotten another BSOD 50. Dump attached.

I hope we can find out whats going on soon, this is getting to be quite the long road to a fix.

Thanks again!

EDIT: I was just forced to restore back to prior to when the verifier was enabled. I continued to get pc hangs etc. I tried to uninstall my video drivers again and install them again just so that I could say i had done it when you asked and my computer froze etc. The PC has been an absolute pain since the verifier was put on, so I had to restore back so that I could actually get a computer that boots properly.

So far I have updated my video drivers, they are up to date as per the NVidia website. I have tried to install DirectX and it determined that I have an up to date copy etc.

- Rip


My System SpecsSystem Spec
.
29 Dec 2010   #22
CarlTR6

Windows 7 Ultimate 32 bit
 
 

The dump, a Driver Verifier enabled dump blames ks.sys which is a Windows system driver and most likely not the real cause. Leave Driver Verifier off for now. You can try uninstalling CCC and installing only the video drivers. CCC is a known problem on some Win 7 systems.
Quote:
ASACPI.sys Wed May 13 21:25:17 2009 - Asus ATK0110 ACPI Utility (older versions of this driver are a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities. ASUSTeK Computer Inc.-Support-.
My System SpecsSystem Spec
29 Dec 2010   #23
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hey Carl,

Thank you for your follow up.

What does CCC stand for? What is that? sorry. - Did you mean Catalyst Control Center? Because I believe that is ATI and I am running NVidia. Let me know! =)

Also, I thought you already had me do the ASACPI.sys thing? Or is this a different situation?

Thanks,

- Rip
My System SpecsSystem Spec
.

30 Dec 2010   #24
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hey everyone,

Just got a BSOD this morning. I have attached the zip.

After this BSOD, I said eff it and tried this anyway. I uninstalled and wiped my display drivers completely. Restarted, fired up the drivers AGAIN and restarted and have them all installed and updated again just in case. I tried to see if I could uninstall Direct X and then reinstall it but I read up that you cant really uninstall Direct X as all the files in there are connected to windows in a ton of ways. One file missing and windows could error out considerably, so I decided against that. I tried to see if I could
"uninstall/repair" but When I run the installer it errors out because I have the Direct X 11 downloaded and installed anyway. Not sure what I can do on that, but I tried to find a way.

When you mentioned CCC, and I thought it was the Catalyst Control Center, I tried to see if there was an Nvidia equivalent and I couldnt see one. When I install the Drivers it installs the '3D Vision Driver' and the 'PhysX Software' which judging by my Nvidia settings is actually needed to adjust performance and active SLI etc.

Note: I currently have disabled SLI and I am running on 1 card so that I can test it out that way and this morning I still got the BSOD which I attached.

Now that I have reinstalled the display drivers again, I'll play with it tonight and see if it BSOD's again. I have a feeling it will so let me know if you have any other ideas on this beast.

I think I have quite the challenge here for ya, it seems this is definitely a head scratcher, haha.

Thanks again,

- Rip
My System SpecsSystem Spec
30 Dec 2010   #25
Tews

64-bit Windows 8.1 Pro
 
 

Your .dmp file is still blaming dxgmms1.sys as the cause of your crash... Download Driver Sweeper to insure that ALL traces of your graphics drivers are removed, before installing the new ones...


Guru3D - Driver Sweeper



Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Users\Tom\Desktop\123010-22666-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Thu Dec 30 08:07:36.761 2010 (UTC - 5:00)
System Uptime: 0 days 0:30:57.101
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880089ead38, 0, fffff880045c90b9, 0}


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

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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc00e0
 fffff880089ead38 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  BFBC2Game.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880093db0a0 -- (.trap 0xfffff880093db0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001a6 rbx=0000000000000000 rcx=00000000000000d3
rdx=fffff880089ea000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045c90b9 rsp=fffff880093db230 rbp=fffff880093dba40
 r8=fffffa800487d108  r9=0000000000000001 r10=fffff8a0086d9b70
r11=00000000400034c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169:
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8] ds:b000:fffff880`089ead38=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b08f14 to fffff80002a88740

STACK_TEXT:  
fffff880`093daf38 fffff800`02b08f14 : 00000000`00000050 fffff880`089ead38 00000000`00000000 fffff880`093db0a0 : nt!KeBugCheckEx
fffff880`093daf40 fffff800`02a8682e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`093db0a0 fffff880`045c90b9 : fffffa80`070c1b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`093db230 fffff880`045af3e7 : fffffa80`047aef01 fffffa80`0458e420 00000000`01e70108 fffff880`00000126 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169
fffff880`093db320 fffff880`04527d6a : 00000000`00000000 00000000`00000200 fffff880`093dba40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`093db370 fffff880`0452752f : fffff8a0`00000001 fffff8a0`07eef430 fffff880`093db9f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`093db980 fffff960`0022bc22 : 00000000`03a1e6b0 fffff880`093dbca0 00000000`0ba27580 fffff800`02ad2113 : dxgkrnl!DxgkRender+0x3e7
fffff880`093dbbf0 fffff800`02a87993 : fffffa80`070c1b60 00000000`000002c8 00000000`00000000 fffffa80`044a61e0 : win32k!NtGdiDdDDIRender+0x12
fffff880`093dbc20 00000000`73cb143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a1e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73cb143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`045ac000 fffff880`045f2000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Jul 13 19:38:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:    
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Users\Tom\Desktop\123010-22666-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Thu Dec 30 08:07:36.761 2010 (UTC - 5:00)
System Uptime: 0 days 0:30:57.101
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880089ead38, 0, fffff880045c90b9, 0}


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

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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc00e0
 fffff880089ead38 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  BFBC2Game.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880093db0a0 -- (.trap 0xfffff880093db0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001a6 rbx=0000000000000000 rcx=00000000000000d3
rdx=fffff880089ea000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045c90b9 rsp=fffff880093db230 rbp=fffff880093dba40
 r8=fffffa800487d108  r9=0000000000000001 r10=fffff8a0086d9b70
r11=00000000400034c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169:
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8] ds:b000:fffff880`089ead38=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b08f14 to fffff80002a88740

STACK_TEXT:  
fffff880`093daf38 fffff800`02b08f14 : 00000000`00000050 fffff880`089ead38 00000000`00000000 fffff880`093db0a0 : nt!KeBugCheckEx
fffff880`093daf40 fffff800`02a8682e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`093db0a0 fffff880`045c90b9 : fffffa80`070c1b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`093db230 fffff880`045af3e7 : fffffa80`047aef01 fffffa80`0458e420 00000000`01e70108 fffff880`00000126 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169
fffff880`093db320 fffff880`04527d6a : 00000000`00000000 00000000`00000200 fffff880`093dba40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`093db370 fffff880`0452752f : fffff8a0`00000001 fffff8a0`07eef430 fffff880`093db9f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`093db980 fffff960`0022bc22 : 00000000`03a1e6b0 fffff880`093dbca0 00000000`0ba27580 fffff800`02ad2113 : dxgkrnl!DxgkRender+0x3e7
fffff880`093dbbf0 fffff800`02a87993 : fffffa80`070c1b60 00000000`000002c8 00000000`00000000 fffffa80`044a61e0 : win32k!NtGdiDdDDIRender+0x12
fffff880`093dbc20 00000000`73cb143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a1e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73cb143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`045c90b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`045ac000 fffff880`045f2000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Jul 13 19:38:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
My System SpecsSystem Spec
30 Dec 2010   #26
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hello there,

Display drivers uninstalled, cleaned and wiped and reinstalled. We shall see if the ever so hated BSOD returns! =)

Stay tuned! - Thanks again.

- Rip
My System SpecsSystem Spec
30 Dec 2010   #27
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hello again...

And so it begins. At least the details on this one I dont think are the same. I have attached the BSOD I just got, 3B.

Take a look and let me know if this tells us anything different.

Thanks!

- Rip
My System SpecsSystem Spec
30 Dec 2010   #28
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hey there,

Got another one. This one appears to be different as well. Hopefully one of these tells you something. Attached it as per usual.

Thanks,

- Rip
My System SpecsSystem Spec
30 Dec 2010   #29
zigzag3143

Win 8 Release candidate 8400
 
 

The rift torrent client caused a memory exception.

run memtest. remove the rift.

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\123010-19500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50
Debug session time: Thu Dec 30 22:41:50.380 2010 (GMT-5)
System Uptime: 0 days 1:10:54.721
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d64d47, fffff8800c1cb110, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+e7 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002d64d47, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800c1cb110, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ObReferenceObjectByHandleWithTag+e7
fffff800`02d64d47 488b03          mov     rax,qword ptr [rbx]

CONTEXT:  fffff8800c1cb110 -- (.cxr 0xfffff8800c1cb110)
rax=febdf3267af67e76 rbx=febdf3267af68206 rcx=00000000000000e4
rdx=0000000000100000 rsi=fffff8a00906eac0 rdi=fffffa80044619f0
rip=fffff80002d64d47 rsp=fffff8800c1cbae0 rbp=fffff8800c1cbc00
 r8=fffff8800989c000  r9=0000000000000010 r10=fffff80002d6b120
r11=fffff8800c1cbc18 r12=0000000000000000 r13=00000000000008e4
r14=0000000000000001 r15=fffffa8003fc61b0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ObReferenceObjectByHandleWithTag+0xe7:
fffff800`02d64d47 488b03          mov     rax,qword ptr [rbx] ds:002b:febdf326`7af68206=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  rift.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d6b189 to fffff80002d64d47

STACK_TEXT:  
fffff880`0c1cbae0 fffff800`02d6b189 : fffff880`0c1cbc00 fffffa80`00100000 00000000`00000000 00000000`00000001 : nt!ObReferenceObjectByHandleWithTag+0xe7
fffff880`0c1cbbb0 fffff800`02a6f993 : fffffa80`044619f0 00000000`070ac724 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x69
fffff880`0c1cbc20 00000000`73c62dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0696ebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73c62dd9


FOLLOWUP_IP: 
nt!ObReferenceObjectByHandleWithTag+e7
fffff800`02d64d47 488b03          mov     rax,qword ptr [rbx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800c1cb110 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+e7

BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+e7

Followup: MachineOwner
---------
My System SpecsSystem Spec
30 Dec 2010   #30
Rippen7

Windows 7 Ultimate 64 Bit
 
 

Hey there,

Thank you for your response. The BSOD's happen with anything I do. In this case I was on Rift but it doesn't matter what I play or what I do, they happen.

As for Memtest, I have already done that twice. Once at the beginning for 8 hours and another part way through this thread for over 12 hours which went through 8 passes and never detected any issues with my RAM.

I am trying to see if I can pin point what exactly is causing the issues with every thing I try and run.

- Rip
My System SpecsSystem Spec
Reply

 BSOD - Crashes Constantly / Dumps attached




Thread Tools




Similar help and support threads
Thread Forum
Multiple different BSOD - crash dumps attached
Hi folks I have a computer that I'm getting my hands on later this afternoon that has been experiencing multiple BSOD events daily. I've attached the most recent 6 crash dumps, each of which seems to indicate something different. I'd appreciate another set of eyes on these with any...
BSOD Help and Support
BSOD-Kernel Power Error-Dumps Attached
Sure hope ya'll can help! PC info: Relatively new Dell Studio XPS 9100, Win 7 Home Premium x64. - original installed OS - OEM (Dell) version - New machine, received Dec. 10, 2010 - OS Age? Same, have not re-installed OS Problem Info
BSOD Help and Support
BSOD (dumps attached)
After opening some corrupt software last night, my task manager got disabled and my computer started to lock up. I immediately rebooted in Safe Mode and ran HijackThis to remove any suspicious startup programs. After doing these, I rebooted into windows and logged in. However, shortly after...
BSOD Help and Support
Recent BSODs, dumps attached
Hello- Been having BSOD problems on Friday and again today, however I was away this weekend, so its every few minutes I use my computer now. On Friday with the first one I received I only briefly saw the screen before it restarted and was under the impression that something was wrong with my...
BSOD Help and Support
need bsod help (dumps attached)
greetings to helpful people of this forum, I need help with my bsods on my laptop. I get the bsod almost every time I wake the laptop from sleep/hibernate. sometimes it wakes with a bsod sometimes it doesn't wake up at all. I attached all the minidump files I had so far. bios is...
BSOD Help and Support
Bsod 3 dumps and info attached
Bhi all - just trying to get to the bottom of this - PLEASE have a look it- is a 124 stop code which indicates hardware - i have went throught the 124 check list - i ran mem test 86 9 passes - ive ran prime 95 (very scary ;-0 ) put my origional win 7 back on - its good for 2 days then bang bsod - i...
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 14:03.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App