Hangs, Loops and BSOD on Win 7 Ultimate 64 bit

Rapha · 24 Sep 2010

First of all thank you for your time.

Getting down to business, for some months I'm having hangs and system freezes with the sound looping and the only way to get out of it is by forcing restart. Sometimes it's even worst and I get a BSOD, other times is a momentary hang and the system recovers. This happens both in 2D and 3D applications. I can be just browsing the web or playing a 3D game it's pretty much the same.
I've used Driver Genius to update all my drivers, the BIOS has been updated and Windows has all of the updates installed.
I've checked temperatures and they're all normal but just in case the side panels have been removed to eliminate that possibility.
Yesterday did 2 passes with Memtest and had some errors. Already tried some other memory but didn't solve it (didn't try Memtest with those memories).

Hardware:

Intel core 2 Quad Q6600 2.4 GHz 8 Mb
Gigabyte GA-P35-DQ6
Corsair HX 620W Modular
Powercolor HD 5870 1Gb DDR5
Corsair Dominator DDR2 PC 8500 (4 x 2 Gb)
Western Digital 1 Tb 64 Mb Cache Sata 3 (WD100FAEX00Z3Z0)

Any help will be greatly appreciated as I'm about to throw my tower from my 3rd floor window! Several times!!

richc46 · 24 Sep 2010

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Code:

Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp3_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\092010-22557-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02ea3e50
Debug session time: Mon Sep 20 09:24:50.765 2010 (GMT-4)
System Uptime: 0 days 0:17:55.809
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004820d90, fffff88006a726a8, fffff88006a71f10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004820d90, The address that the exception occurred at
Arg3: fffff88006a726a8, Exception Record Address
Arg4: fffff88006a71f10, Context Record Address
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`04820d90 8b4810          mov     ecx,dword ptr [rax+10h]
EXCEPTION_RECORD:  fffff88006a726a8 -- (.exr 0xfffff88006a726a8)
ExceptionAddress: fffff88004820d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT:  fffff88006a71f10 -- (.cxr 0xfffff88006a71f10)
rax=0056000000000000 rbx=fffff8a003359450 rcx=fffffa8008d54ca0
rdx=fffffa80096aa3b0 rsi=fffffa8008d4b000 rdi=fffffa8008d4b000
rip=fffff88004820d90 rsp=fffff88006a728e0 rbp=fffffa8006bf8050
r8=fffffa80067c0000  r9=0000000000000000 r10=0000000000000000
r11=000000000000000b r12=fffffa80096aa3b0 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`04820d90 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:00560000`00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e0e0
ffffffffffffffff 
FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`04820d90 8b4810          mov     ecx,dword ptr [rax+10h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff8800481ded3 to fffff88004820d90
STACK_TEXT:  
fffff880`06a728e0 fffff880`0481ded3 : 00000000`00000000 fffffa80`06ff8018 00000000`00000008 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`06a72910 fffff880`0483865d : 00000000`00000000 fffff8a0`03fb8860 fffffa80`00000000 fffffa80`067c0090 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`06a72ae0 fffff880`04838398 : fffff800`00b96080 fffff880`04837d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`06a72cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`068a4560 00000000`00000080 fffffa80`08c9a010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06a72d00 fffff800`02f7ac06 : 00000000`03134f41 fffffa80`08cac8c0 fffffa80`06723ae0 fffffa80`08cac8c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06a72d40 fffff800`02cb4c26 : fffff800`02e50e80 fffffa80`08cac8c0 fffff800`02e5ec40 6c72506f`6865652b : nt!PspSystemThreadStartup+0x5a
fffff880`06a72d80 00000000`00000000 : fffff880`06a73000 fffff880`06a6d000 fffff880`06a72690 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
STACK_COMMAND:  .cxr 0xfffff88006a71f10 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner
---------

The cause was given as dxgmms1, which is unlikely, as it is an indication of video problems
Update your video driver
If overclocking restore normal settings
SFC /scannow
System Files - SFC Command
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Scan with your Anti Virus

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.

Rapha · 24 Sep 2010

richc46,

I've scanned and you can find the result attached. I'm not overclocking and the video card has te most up to date drivers (downloaded yesterday from ATI site).
Will run memtest tonight and post results tomorrow.
also I forgot to mention this was a clean install and is probably the 4th one (meanwhile between installs I've changed the hard drive).
thanks

richc46 · 24 Sep 2010

Thanks for the information. Follow all the instructions, if you get another BSOD,just post.

richc46 · 24 Sep 2010

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:
www.duplexsecure.com/en/downloads

Rapha · 28 Sep 2010

Completed MemTest for 11 passes (left it alone for too much time) with a lot of errors. This amount of errors may mean the memory is physically damaged?
Regarding Daemon tools, although it's installed now I've had this issue with a fresh install of Win 7 (only had OS, updated drivers and a couple of games for testing).
Will try to uninstall as you said and revert with results.

richc46 · 28 Sep 2010

Sounds like it is basically a memory problem. Get that looked at.

Rapha · 28 Sep 2010

But this also happens with a diferent set of memory. I'll try to test this memory in a diferent computer and post results.

richc46 · 28 Sep 2010

Take a good stick of ram and test in each slot. Should be done over night.

Rapha · 29 Sep 2010

So I've tested my memory on another computer and they came up clean: not a single error. tested that computers memory on my machine and no errors. It's looking more and more like a motherboard / memory incompatibility issue.