Hangs, Loops and BSOD on Win 7 Ultimate 64 bit

[Rapha]

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]

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,

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

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

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]

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]

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

 

[richc46]

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]

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]

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

 

[Rapha]

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]

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

 

[Rapha]

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.

 

[richc46]

First, after today, I will be away for 3 weeks. Hopefully another member will continue if the problem is not resolved.

I am still leaning toward memory. Did you test each slot with a known good stick?

 

[Rapha]

I haven't tested each individual slot (lack of time) but I had errors in all slots in the previous tests. I'm doing some aditional tests and post results. thanks