Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Comp Crashes While Playing WoW for quite some time


  • Please log in to reply
2 replies to this topic

#1 jswan08

jswan08

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:43 PM

Posted 25 December 2008 - 03:11 PM

Hey I'm new here and was wondering if I could possibly get some help with this issue I have been experiencing. When I've been in World Of Warcraft for quite some time, or any other game for that matter, my computer totally locks up, and until now I never noticed that I received a BSOD after it reboots itself.

I built my system myself and the specs are as follows
MoBo: Asus A8N-SLI Premium Socket 939
CPU: AMD 4000+ 2.4 ghz
PSU: ULTRA 550w
RAM: Patriot 2 x 1GB PC 3200 DDR 184 Pin D400
Drive: WD 320g 7200 RPM
GFX Card: eVGA 7950 GX2 512MB

I debugged the BSOD and in return I got:


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\jswan08\My Documents\Mini122508-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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Thu Dec 25 00:20:28.583 2008 (GMT-5)
System Uptime: 0 days 5:02:19.671
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {8a203a30, 89d74928, bacd3cb4, 1}

*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+7b6ab )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8a203a30, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 89d74928, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacd3cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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


FAULTING_THREAD: 8a203a30

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from 806d2ca4 to 805418bf

STACK_TEXT:
b9baf790 806d2ca4 00000000 ffdff980 80541086 nt!KiDispatchInterrupt+0x7f
b9baf79c 80541086 00000000 000000d1 00009400 hal!HalEndSystemInterrupt+0x54
b9baf79c 80527efa 00000000 000000d1 00009400 nt!KeUpdateSystemTime+0x13e
b9baf81c b9d4e6ab b89b6400 b9d70a92 8a34c4a8 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b9baf824 b9d70a92 8a34c4a8 8a349008 00009400 nv4_mini+0x7b6ab
b9baf828 8a34c4a8 8a349008 00009400 8a345308 nv4_mini+0x9da92
b9baf82c 8a349008 00009400 8a345308 8a349008 0x8a34c4a8
b9baf830 00000000 8a345308 8a349008 00000000 0x8a349008


STACK_COMMAND: .thread 0xffffffff8a203a30 ; kb

FOLLOWUP_IP:
nv4_mini+7b6ab
b9d4e6ab ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nv4_mini+7b6ab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48ebd3e6

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2008_10_07

BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2008_10_07

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8a203a30, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 89d74928, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacd3cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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


FAULTING_THREAD: 8a203a30

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from 806d2ca4 to 805418bf

STACK_TEXT:
b9baf790 806d2ca4 00000000 ffdff980 80541086 nt!KiDispatchInterrupt+0x7f
b9baf79c 80541086 00000000 000000d1 00009400 hal!HalEndSystemInterrupt+0x54
b9baf79c 80527efa 00000000 000000d1 00009400 nt!KeUpdateSystemTime+0x13e
b9baf81c b9d4e6ab b89b6400 b9d70a92 8a34c4a8 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b9baf824 b9d70a92 8a34c4a8 8a349008 00009400 nv4_mini+0x7b6ab
b9baf828 8a34c4a8 8a349008 00009400 8a345308 nv4_mini+0x9da92
b9baf82c 8a349008 00009400 8a345308 8a349008 0x8a34c4a8
b9baf830 00000000 8a345308 8a349008 00000000 0x8a349008


STACK_COMMAND: .thread 0xffffffff8a203a30 ; kb

FOLLOWUP_IP:
nv4_mini+7b6ab
b9d4e6ab ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nv4_mini+7b6ab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48ebd3e6

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2008_10_07

BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2008_10_07

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

P.S Ive Also included a copy of my DxDiag if it helps

Attached Files



BC AdBot (Login to Remove)

 


#2 jswan08

jswan08
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:43 PM

Posted 25 December 2008 - 03:18 PM

also I am now getting another error with dthtml.exe with the module nvcpl.dll, but It didnt create a log for me to post to you guys.

#3 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:43 AM

Posted 25 December 2008 - 05:39 PM

Try reinstalling your video driver.

How to update a Windows hardware driver
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users