So, im going to explain is as much detail as I can what my problem is, I do not remember when it started, I have been coping with it for over a month now.
I do not remember if I ever downloaded anything that caused this issue and I doubt it.
Lets start with my system specifications.
Operating System:Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Processor: AMD Athlon 64 Processor 3500+, MMX, 3DNow, ~2.2GHz
Memory: 1024MB RAM
DirectX Version: DirectX 9.0c (4.09.0000.0904)
Card name: NVIDIA GeForce 7800 GT
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.6371 (English)
Driver Date/Size: 9/17/2007 01:07:00, 5783040 bytes
DDI Version: 9 (or higher)
DirectDraw Acceleration: Enabled
Direct3D Acceleration: Enabled
AGP Texture Acceleration: Enabled
If you do need any more feel free to ask, also if you need more of my dxdiag log thing, I can post this as well.
Other techies seemed to be interested in asking me what my motherboard was, it's a nForce4.
These crashes usually freeze my applications though the mouse can still move, but nothing works. So I am forced to hold down the power button to turn it off.
I do know how to debug minidump files, so heres what it said (The driver running in an infinite loop part is important):
Now then, Every time it crashes you would normally just turn it back on right?
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.
Arg1: 858db798, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 864f93f8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f78becb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
LAST_CONTROL_TRANSFER: from 804f8e6e to 80540b9f
f1451a10 804f8e6e f78beb40 f78beb70 00000000 nt!KiUnlockDispatcherDatabase+0x77
f1451a24 f0473a67 f78beb94 00000000 00000000 nt!KeSetEvent+0x74
f1451d18 804fd18b f78beb40 f1451d64 f1451d58 watchdog!WatchdogKernelApc+0x13b
f1451d68 806d0c35 00000000 00000000 f1451d80 nt!KiDeliverApc+0xb3
f1451d68 805272d6 00000000 00000000 f1451d80 hal!HalpApcInterrupt+0xc5
f1451df0 f5e85d7b ed56e400 f5ea871b 863ef6a0 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
f1451df8 f5ea871b 863ef6a0 855be9e8 00009400 nv4_mini+0x69d7b
f1451dfc 863ef6a0 855be9e8 00009400 855be9e8 nv4_mini+0x8c71b
f1451e00 855be9e8 00009400 855be9e8 855be9e8 0x863ef6a0
f1451e04 00000000 855be9e8 855be9e8 00001388 0x855be9e8
STACK_COMMAND: .thread 0xffffffff858db798 ; kb
f5e85d7b ?? ???
But, when I just turn it back on, it apparently can't find the drive/the driver won't start because it goes to a black screen with Nvidia boot manager trying to find the drive (I think) and after waiting, it to says drive not found insert disk and press enter or something along the lines of that. If needed I could attempt to take a picture of this.
But after this, I have to turn it back off, and after waiting about 6-10 minutes it works again.
Now about the grinding noise, when turning on the computer it normally beeps (Alienware comp) after getting past the windows logo screen, about at the blue login screen it starts to grind a bit (when its going on a 2nd layer of loading). If I react too fast (Open firefox, etc) too quick It freezes again sometimes. So pushing the right side of the case lowers the sound of the grinding though.
Event viewer likes to put little "disk" errors in the system part.
It puts warnings, of event 51, that just says the source is disk.
If you need me to post anything from the data box part, just ask.
An error was detected on device \Device\Harddisk0\D during a paging operation.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Well you might think this could be a power problem, but when the drive "Runs its infinite loop" the computer is still on and the mouse is movable, and the fan is still running, so it cannot be a power problem.
Thats pretty much it, if you need any info to aid you, feel free to post it here and ill try to help as soon as possible. I do hope you can fix/aid me with my problem, thanks for your time.
Edited by Xene, 18 May 2008 - 12:35 PM.