Computer Locking Up Again :(

[Solecord]

So several months ago I posted a thread asking for people to help with my computer freezing up.

http://www.quakeone.com/forums/showthread.php?t=2956

All of a sudden it started doing it again whenever I play videos (whether it be a game, an mpg in a media player, or a streaming video online). After 30 seconds to a minute my whole system will basically lock up, the video will stop but the sound will continue on, sometimes looping through the same 5 seconds of audio over and over. My mouse will still move around but nothing is responsive. If I load Quake, after about a minute the video will stop and the sounds will loop. If I hit the ~, type quit and hit enter in about 4 or 5 minutes the game will finally close and my system becomes responsive again.

Any thoughts/ideas?

[Canadian*Sniper]

Does your OS ever fail to load up?

"DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"??

[Solecord]

Nope, OS loads fine.

[Shadowswift]

the MCP is in your system!

[Canadian*Sniper]

How about memory? Does your screen freeze when you run out of RAM?

[IEEE 802.11]

Right click My Computer -> Manage -> Event Viewer and post any errors you see from the Application and System logs. Check the time/date. Also see if your video card has it's own log.

After you reboot from the lock up does it say you had a "Fatal System Error"?
Look in C:\WINDOWS\Minidump\ are there any files there? If so, these may give you a clue as to what happened using this tool: http://www.microsoft.com/whdc/devtoo...g/default.mspx

[Solecord]

I booted into safe mode, removed my video card driver, rebooted back into safe mode again, used driver sweeper to make sure it was completely removed, rebooted again into safe mode, and installed the very latest stable driver direct from nvidia's website.

Now when I load Quake and it freezes up about a minute or so later I get a BSOD with an error "device driver got stuck in an infinite loop" and "THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)"

The dump file that was created reads as follows:

Opened log file 'c:\debug-03.txt'
1: kd> .sympath SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
1: kd> /reload;!analyze -v;r;kv;.logclose;q
^ Syntax error in '/reload;!analyze -v;r;kv;.logclose;q'
1: kd> .reload;!analyze -v;r;kv;.logclose;q
Loading Kernel Symbols
.................................................. .................................................. .....................
Loading User Symbols
Loading unloaded module list
....................
************************************************** *****************************
* *
* 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: 89beaab8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 87c0d008, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacebcbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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




DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 3

BUGCHECK_STR: 0xEA

LAST_CONTROL_TRANSFER: from 00034004 to 8052ab42

STACK_TEXT:
a77304b0 00034004 6a73fada f90070d8 04703018 nt!READ_REGISTER_ULONG+0x6
WARNING: Frame IP not in any known module. Following frames may be wrong.
a77304b8 f90070d8 04703018 20ec0af3 ff18ff00 0x34004
a77304bc 04703018 20ec0af3 ff18ff00 30706618 0xf90070d8
a77304c0 20ec0af3 ff18ff00 30706618 18113151 0x4703018
a77304c4 ff18ff00 30706618 18113151 177038aa 0x20ec0af3
a77304c8 30706618 18113151 177038aa 3431b02d 0xff18ff00
a77304cc 18113151 177038aa 3431b02d 90661990 0x30706618
a77304d0 177038aa 3431b02d 90661990 70620618 0x18113151
a77304d4 3431b02d 90661990 70620618 3718fb00 0x177038aa
a77304d8 90661990 70620618 3718fb00 2d324531 0x3431b02d
a77304dc 70620618 3718fb00 2d324531 0df1347a 0x90661990
a77304e0 3718fb00 2d324531 0df1347a ff067018 0x70620618
a77304e4 2d324531 0df1347a ff067018 f50dff0d 0x3718fb00
a77304e8 0df1347a ff067018 f50dff0d f0c7080d 0x2d324531
a77304ec ff067018 f50dff0d f0c7080d 110dff02 0xdf1347a
a77304f0 f50dff0d f0c7080d 110dff02 77000062 0xff067018
a77304f4 f0c7080d 110dff02 77000062 91770e80 0xf50dff0d
a77304f8 110dff02 77000062 91770e80 777220b6 0xf0c7080d
a77304fc 77000062 91770e80 777220b6 30b09171 0x110dff02
a7730500 91770e80 777220b6 30b09171 9026f114 0x77000062
a7730504 777220b6 30b09171 9026f114 793303b0 0x91770e80
a7730508 30b09171 9026f114 793303b0 007aa091 0x777220b6
a773050c 9026f114 793303b0 007aa091 730f7018 0x30b09171
a7730510 793303b0 007aa091 730f7018 3fffff0e 0x9026f114
a7730514 007aa091 730f7018 3fffff0e 917f6a7f 0x793303b0
a7730518 730f7018 3fffff0e 917f6a7f 347b917d 0x7aa091
a773051c 3fffff0e 917f6a7f 347b917d 3f7f7913 0x730f7018
a7730520 917f6a7f 347b917d 3f7f7913 79e90000 0x3fffff0e
a7730524 347b917d 3f7f7913 79e90000 77fee091 0x917f6a7f
a7730528 3f7f7913 79e90000 77fee091 0cf81026 0x347b917d
a773052c 79e90000 77fee091 0cf81026 26719179 0x3f7f7913
a7730530 77fee091 0cf81026 26719179 72445103 0x79e90000
a7730534 0cf81026 26719179 72445103 30363991 0x77fee091
a7730538 26719179 72445103 30363991 00363138 0xcf81026
a773053c 72445103 30363991 00363138 312d3635 0x26719179
a7730540 30363991 00363138 312d3635 2d393762 0x72445103
a7730544 00363138 312d3635 2d393762 64663400 0x30363991
a7730548 312d3635 2d393762 64663400 66382d64 0x363138
a773054c 2d393762 64663400 66382d64 2d650038 0x312d3635
a7730550 64663400 66382d64 2d650038 66383461 0x2d393762
a7730554 66382d64 2d650038 66383461 38006232 0x64663400
a7730558 2d650038 66383461 38006232 65343732 0x66382d64
a773055c 66383461 38006232 65343732 5ac77d39 0x2d650038
a7730560 38006232 65343732 5ac77d39 f026f901 0x66383461
a7730564 65343732 5ac77d39 f026f901 5c710d78 0x38006232
a7730568 5ac77d39 f026f901 5c710d78 6219f243 0x65343732
a773056c f026f901 5c710d78 6219f243 65623039 0x5ac77d39
a7730570 5c710d78 6219f243 65623039 933f7f00 0xf026f901
a7730574 6219f243 65623039 933f7f00 00187f91 0x5c710d78
a7730578 65623039 933f7f00 00187f91 70603e00 0x6219f243
a773057c 933f7f00 00187f91 70603e00 3123f104 0x65623039
a7730580 00187f91 70603e00 3123f104 75183100 0x933f7f00
a7730584 70603e00 3123f104 75183100 7ffbe018 0x187f91
a7730588 3123f104 75183100 7ffbe018 01f531f7 0x70603e00
a773058c 75183100 7ffbe018 01f531f7 15310071 0x3123f104
a7730590 7ffbe018 01f531f7 15310071 18710b71 0x75183100
a7730594 01f531f7 15310071 18710b71 244975f1 0x7ffbe018
a7730598 15310071 18710b71 244975f1 90722d44 0x1f531f7
a773059c 18710b71 244975f1 90722d44 2673fc68 0x15310071
a77305a0 244975f1 90722d44 2673fc68 f7dbfd28 0x18710b71
a77305a4 90722d44 2673fc68 f7dbfd28 9802b190 0x244975f1
a77305a8 2673fc68 f7dbfd28 9802b190 17f30470 0x90722d44
a77305ac f7dbfd28 9802b190 17f30470 b0a97f30 0x2673fc68
a77305b0 9802b190 17f30470 b0a97f30 a97fefa6 0xf7dbfd28
a77305b4 17f30470 b0a97f30 a97fefa6 17ffa97b 0x9802b190
a77305b8 b0a97f30 a97fefa6 17ffa97b 70802d73 0x17f30470
a77305bc a97fefa6 17ffa97b 70802d73 ff90ff05 0xb0a97f30
a77305c0 17ffa97b 70802d73 ff90ff05 0cf58d0c 0xa97fefa6
a77305c4 70802d73 ff90ff05 0cf58d0c 7f02f070 0x17ffa97b
a77305c8 ff90ff05 0cf58d0c 7f02f070 40000025 0x70802d73
a77305cc 0cf58d0c 7f02f070 40000025 58f60d40 0xff90ff05
a77305d0 7f02f070 40000025 58f60d40 90ff0030 0xcf58d0c
a77305d4 40000025 58f60d40 90ff0030 13572064 0x7f02f070
a77305d8 58f60d40 90ff0030 13572064 3117750e 0x40000025
a77305dc 90ff0030 13572064 3117750e f0b0de7d 0x58f60d40


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!READ_REGISTER_ULONG+6
8052ab42 c20400 ret 4

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!READ_REGISTER_ULONG+6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

FAILURE_BUCKET_ID: 0xEA_nt!READ_REGISTER_ULONG+6

BUCKET_ID: 0xEA_nt!READ_REGISTER_ULONG+6

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

eax=8002fc1b ebx=8a076008 ecx=8a076008 edx=b65c7604 esi=8a08a100 edi=8a076008
eip=8052ab42 esp=a77304b4 ebp=00002604 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
nt!READ_REGISTER_ULONG+0x6:
8052ab42 c20400 ret 4
ChildEBP RetAddr Args to Child
a77304b0 00034004 6a73fada f90070d8 04703018 nt!READ_REGISTER_ULONG+0x6 (FPO: [1,0,0])
WARNING: Frame IP not in any known module. Following frames may be wrong.
a77304b8 f90070d8 04703018 20ec0af3 ff18ff00 0x34004
a77304bc 04703018 20ec0af3 ff18ff00 30706618 0xf90070d8
a77304c0 20ec0af3 ff18ff00 30706618 18113151 0x4703018
a77304c4 ff18ff00 30706618 18113151 177038aa 0x20ec0af3
a77304c8 30706618 18113151 177038aa 3431b02d 0xff18ff00
a77304cc 18113151 177038aa 3431b02d 90661990 0x30706618
a77304d0 177038aa 3431b02d 90661990 70620618 0x18113151
a77304d4 3431b02d 90661990 70620618 3718fb00 0x177038aa
a77304d8 90661990 70620618 3718fb00 2d324531 0x3431b02d
a77304dc 70620618 3718fb00 2d324531 0df1347a 0x90661990
a77304e0 3718fb00 2d324531 0df1347a ff067018 0x70620618
a77304e4 2d324531 0df1347a ff067018 f50dff0d 0x3718fb00
a77304e8 0df1347a ff067018 f50dff0d f0c7080d 0x2d324531
a77304ec ff067018 f50dff0d f0c7080d 110dff02 0xdf1347a
a77304f0 f50dff0d f0c7080d 110dff02 77000062 0xff067018
a77304f4 f0c7080d 110dff02 77000062 91770e80 0xf50dff0d
a77304f8 110dff02 77000062 91770e80 777220b6 0xf0c7080d
a77304fc 77000062 91770e80 777220b6 30b09171 0x110dff02
a7730500 91770e80 777220b6 30b09171 9026f114 0x77000062
Closing open log file c:\debug-03.txt

[Shadowswift]

IEEE's avitar made me giggle

[spooker]

please post more incomprehensible code.
you know, after a while, you dont even see the code anymore. you just see blonde, red-head, ......

[Paradi$e]

It could be that your video card is defect. For how long have you had it, and buy ATI next time. Trust me.

[foq]

Maybe the graphics card is overheating. Download ATiTool, run Scan for Artifacts, and watch the temps. IMO anything over 80C is dangerous, although they supposedly take up to 120c...

Isn't this a prebuilt computer? Send it back to them.

[IEEE 802.11]

I booted into safe mode, removed my video card driver, rebooted back into safe mode again, used driver sweeper to make sure it was completely removed, rebooted again into safe mode, and installed the very latest stable driver direct from nvidia's website.

Now when I load Quake and it freezes up about a minute or so later I get a BSOD with an error "device driver got stuck in an infinite loop" and "THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)"

The dump file that was created reads as follows:

...

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

FAILURE_BUCKET_ID: 0xEA_nt!READ_REGISTER_ULONG+6

BUCKET_ID: 0xEA_nt!READ_REGISTER_ULONG+6

Followup: MachineOwner

...

Now: http://www.google.com/search?hl=en&q...=Google+Search

[IEEE 802.11]

So, what happened?

[foq]

his computer imploded

[Solecord]

I reformatted last night. Once I play around with it tonight I'll let you know. I need to reinstall all my shit and test