Jump to content
Posted 21 November 2006 - 03:41 PM
Posted 21 November 2006 - 10:46 PM
Posted 22 November 2006 - 04:07 PM
Posted 22 November 2006 - 07:48 PM
STOP 0xD1: http://aumha.org/win5/kbestop.php#0xd1
Most likely a bad device driver - but can also be caused by faulty or mismatched RAM, or a damaged pagefile.
What have you done to the system lately (either when this started happening or just before it)? The littlest thing can help us to figure it out.
After that, I'd start with testing the RAM and recreating the pagefile (because it's easier than searching for the driver). If that didn't turn up anything, then we'd start looking for a suspect driver.
With your system specs, I'd suspect that you're doing a bit of tweaking or overclocking. If so, you'll have to shut it all off and return everything to default values for the troubleshooting (to include any BIOS tweaks, custom drivers, etc).
Posted 23 November 2006 - 05:12 AM
Posted 23 November 2006 - 08:21 AM
0 members, 0 guests, 0 anonymous users