GTX560, BSOD's, headaches.

fungole said:

Hello!

system specs :

stock speeds , nothing is overclocked.

Intel Q5500 Core2 Quad 2.83ghz
6G Corsair Dominator 1066 DDR2
Asus P5Q Deluxe Motherboard
WD Caviar black 760G
Asus GTX 560 DC 1G DDR5
Antec Earthwatts 500W PSU

Win 7 64 bits profesionnal 7600 OEM legit

--

Two days ago, I installed a new graphic card on my computer. I unmounted the CPU, inspected the fan, applied new thermal paste ( I do it every year ), dusted, yada yada. Booted in safe mode, uninstalled graphic drivers ( previously had a Quadro FX1700 ), rebooted, installed latest Nvidia drivers - 275.33 -, played starcraft 2, got a random BSOD. ( error code 0 irc ). Installed Crysis 2, BSOD 1e 10 minutes into the game. Rebooted, OS couldn't start, gave me the blue screen on startup. At that point the OS wouldn't boot. It would simply blue screen after startup.

Reinstalled Windows, I resetted the CMOS / NVRAM / and flashed my motherboard's bios to the latest version, installed Nvidia drivers 275.33, BSOD'ed in Crysis, once in Google Chrome, system restored, installed 270.48, BSOD'ed, here I am looking for a way to fix this. Faulty brand new graphic card? PSU growing old? Faulty user? Time to buy a Mac?

thanks in advance.

the only thing I have installed on the computer so far are Crysis 2, winrar, google chrome, and a few windows updates.

Memory exception caused by the directX portion of your video driver..Re-install with newest using this method and run memtest


When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

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\060611-20888-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e50
Debug session time: Mon Jun  6 23:45:04.303 2011 (GMT-4)
System Uptime: 0 days 0:35:59.019
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800415bce5, fffff880033666a8, fffff88003365f00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

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

1: 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: fffff8800415bce5, The address that the exception occurred at
Arg3: fffff880033666a8, Exception Record Address
Arg4: fffff88003365f00, 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+19
fffff880`0415bce5 488b02          mov     rax,qword ptr [rdx]

EXCEPTION_RECORD:  fffff880033666a8 -- (.exr 0xfffff880033666a8)
ExceptionAddress: fffff8800415bce5 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000019)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003365f00 -- (.cxr 0xfffff88003365f00)
rax=fffff88003366908 rbx=0000000000000000 rcx=fffffa80077f4000
rdx=fefffa8007d42be0 rsi=fffffa80055bb0f0 rdi=fffffa80077f4000
rip=fffff8800415bce5 rsp=fffff880033668e0 rbp=fffffa80063d32d8
 r8=fffffa8007412d01  r9=0000000000000000 r10=0000000000000000
r11=0000000000000053 r12=0000000000000035 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffff880`0415bce5 488b02          mov     rax,qword ptr [rdx] ds:002b:fefffa80`07d42be0=????????????????
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 fffff80002ec40e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`0415bce5 488b02          mov     rax,qword ptr [rdx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88004158ed3 to fffff8800415bce5

STACK_TEXT:  
fffff880`033668e0 fffff880`04158ed3 : 00000000`00000000 fffffa80`055bb0f0 00000000`00000035 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`03366910 fffff880`0417365d : 00000000`00000000 fffff8a0`01303ce0 fffffa80`00000000 fffffa80`07412dc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`03366ae0 fffff880`04173398 : fffff800`03fce080 fffff880`04172d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03366cd0 fffff880`04172e96 : 00000000`00000000 fffffa80`06256760 00000000`00000080 fffffa80`07743410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03366d00 fffff800`02f31166 : 00000000`030b81f1 fffffa80`07648b60 fffffa80`05206ae0 fffffa80`07648b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03366d40 fffff800`02c6c486 : fffff800`02e06e80 fffffa80`07648b60 fffff800`02e14c40 fffff880`01229a90 : nt!PspSystemThreadStartup+0x5a
fffff880`03366d80 00000000`00000000 : fffff880`03367000 fffff880`03361000 fffff880`03366690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88003365f00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19

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

Used Phyxion's driver sweeper and updated to latest driver. Tested the game, it was stable for 20 minutes until :


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88010B6EDFA
BCP3: FFFFF88009C40990
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


I will run Memtest86 all day long, will post results tonight.

Thanks for the quick answer!

My pleasure