Sign in with
Sign up | Sign in
Your question

Computer restarts during gameplay

Last response: in Windows 7
Share
July 8, 2011 5:13:30 AM

Hi,

When I play world of warcraft, I recently started getting reboots during 2 minutes of game play. I ran a windbg memory dumb and came across this. What am I suppose to do next to fix the problem?

Windows 7 64x
eVga P55
eVga Nvidia 295
Intel i7 860

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


Loading Dump File [C:\Windows\Minidump\040211-13593-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0284e000 PsLoadedModuleList = 0xfffff800`02a8be50
Debug session time: Sat Apr 2 10:36:07.194 2011 (GMT-5)
System Uptime: 0 days 2:33:25.209
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000096, fffff88007cb7ab7, fffff8800cb20e60, 0}

Probably caused by : nvoclk64.sys ( nvoclk64+1ab7 )

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

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

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

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


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.

FAULTING_IP:
nvoclk64+1ab7
fffff880`07cb7ab7 0f32 rdmsr

CONTEXT: fffff8800cb20e60 -- (.cxr 0xfffff8800cb20e60)
rax=fffff88007cc0120 rbx=fffffa8004abe8a0 rcx=000000000000002c
rdx=fffff8800cb21888 rsi=fffffa8004b63e38 rdi=fffff8800cb218d0
rip=fffff88007cb7ab7 rsp=fffff8800cb21830 rbp=fffff8800cb21ca0
r8=fffff8800cb21880 r9=fffff8800cb21888 r10=25a67c1210cd665e
r11=8673ac09509f27e4 r12=fffffa8004b63dc0 r13=fffffa8004abe7d0
r14=0000000000000138 r15=fffffa80078a8880
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvoclk64+0x1ab7:
fffff880`07cb7ab7 0f32 rdmsr
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: NVMonitor.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88007cb7ab7

STACK_TEXT:
fffff880`0cb21830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvoclk64+0x1ab7


FOLLOWUP_IP:
nvoclk64+1ab7
fffff880`07cb7ab7 0f32 rdmsr

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvoclk64+1ab7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvoclk64

IMAGE_NAME: nvoclk64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46de13d9

STACK_COMMAND: .cxr 0xfffff8800cb20e60 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nvoclk64+1ab7

BUCKET_ID: X64_0x3B_nvoclk64+1ab7

Followup: MachineOwner
---------
July 8, 2011 2:07:13 PM

My gut feeling is it's one of 3 things (in no particular order):

1) A driver - have you updated your graphics driver since it started happening? If not, then probably not the issue.
2) Temperature - blow out your PSU, graphics card fan, CPU fan and anything else that collects dust. Run it with your case open. Download Speedfan and see what your temperatures are
3) Failing hardware, most likely RAM or PSU. Run Memtest86 to see if your RAM is ok.

Do you play any other games or primarily just this one? The reason I ask is because I'm curious if it happens only with this specific game (others play fine). Do you do anything else that is graphically or memory intensive with this machine? I suppose if you do other things with it that should result in the same failure but doesn't then it could be something up with the game itself. Maybe there are patches for it, or maybe a patch was installed and now it's crashing...
m
0
l
July 8, 2011 10:19:59 PM

I'm going to give it 24 more hours before I label this solved.

Solution:
Because nvoclk64 was the problem, I figured it would be an nvidia issue. It turns out the problem was nTunes. It was causing a lot of problems and I remember installing it in April of 2011 and that's when my problem began. It's gotten worse until I removed everything there is about nTunes except the uninstall doesn't work and add and remove programs. The icon is still there and it says 30mb. When I try to uninstall nothing happens. I removed every registry that had nTunes and deleted the folder.

Also, there's been issues with the new nVidia drivers 275.50 that causes the BSOD or black screen halt with a system reboot. I went back to 266.58 which seem to be the most stable drivers. I see nothing new with drivers besides fixes for 3D. People really use 3D that much?

Hopefully it works but I'm not going to label this solved just yet. I also would like to mention I removed the HD AUDIO folder before installing my drivers. Audio has been known to cause this problem too.

To the fix the audio problem with nVidia, go to device manager and under System devices DISABLE NOT UNINSTALL the High Definition Audio Controller. That itself will remove the HD AUDIO in sounds and video.

I will keep you posted and hopefully this could be a fix for everyone that's been having this problem as of late.

Note:
I tested with Microsoft Flight Simulator X. Everytime I was about to leave the gate the game would crash. I'm happy to say that I flew from Chicago to San Francisco and landed safely with no system restart. I hope the problem is solved. :) 
m
0
l
July 8, 2011 11:34:51 PM

Nope, it happened it again. :( 
m
0
l
!