D
Dave Navarro
I built a new computer with a Gigabyte Motherboard using the INTEL
chipset with a 2.4GHz P4 HT processor and two gigabytes of RAM. I have
a 120 GB Western Digital IDE boot drive and a 200 GB Western Digital IDE
data drive.
Whenever I do anything that is hard drive intensive (writes/reads lots
of temp files) my system will reboot. This typically happens when I run
programs like DVDLab (building a DVD) with a large project, TMPGenc with
a large file, Alcohol 120% (writing a DVD image to the hard drive).
When the system reboots it sends an error report to Microsoft and then
pops up a message telling me that the reboot was caused by a device
driver, but it doesn't tell me which device driver it is.
So, I turned off automatic reboot so that I could read the BSOD and it
still doesn't tell me which device driver is causing the problem.
I am running Windows XP SP2 with all updates (including driver updates)
installed.
The BSOD info is:
STOP 0x0000000A (0x0992F778,0x00000002,0x804F8675)
but it doesn't give me a filename or device name.
Any ideas on how I can figure out what the problem is and fix it?
--Dave
chipset with a 2.4GHz P4 HT processor and two gigabytes of RAM. I have
a 120 GB Western Digital IDE boot drive and a 200 GB Western Digital IDE
data drive.
Whenever I do anything that is hard drive intensive (writes/reads lots
of temp files) my system will reboot. This typically happens when I run
programs like DVDLab (building a DVD) with a large project, TMPGenc with
a large file, Alcohol 120% (writing a DVD image to the hard drive).
When the system reboots it sends an error report to Microsoft and then
pops up a message telling me that the reboot was caused by a device
driver, but it doesn't tell me which device driver it is.
So, I turned off automatic reboot so that I could read the BSOD and it
still doesn't tell me which device driver is causing the problem.
I am running Windows XP SP2 with all updates (including driver updates)
installed.
The BSOD info is:
STOP 0x0000000A (0x0992F778,0x00000002,0x804F8675)
but it doesn't give me a filename or device name.
Any ideas on how I can figure out what the problem is and fix it?
--Dave