My computer has been crashing lately - either a bluescreen with ambiguous error, or INPAGE_KERNEL_ERROR (don't remember exact string), OR just total mouse freeze and have to hard-reset (the latter seems more frequent).
I have an nForce 2 ASUS A7N8X-X motherboard (few years old)
I have ATA133 and ATA100 HDDs on it, 1 master 1 slave. on primary IDE channel. Using 5.10 nforce drivers.
The best way to reproduce the error is to run CHKDSK /f and /r on one of the slave HDD partitions. Will almost always result in a mouse freeze, with NO BSOD.
The most recent hardware change was replacing old RAM with 2 new sticks of Buffalo Select ram. Ran MS Memory Diagnostic (all 11 tests) and now running MemTest - doesn't look like it's a ram issue. CPU Burn in also seems to not be the issue. I have an Athlon XP-M 2500+ running at 200mHz x 9.5 multiplier, ram set to same frequency 8,3,3,3 timing (the CPU seems to not want to actually run at 133mHzx14 multiplier, which is really weird because that's the stock frequency!)
In any case, I don't think its a CPU/ram issue - I think it seems more like a HDD or IDE controller issue, but what is the best way to find out what's going on?
I am currently running with the slave HDD unplugged, and running CHKDSK on c: without automatic fixing hasn't crashed the computer. Could the slave drive be faulty?
I have an nForce 2 ASUS A7N8X-X motherboard (few years old)
I have ATA133 and ATA100 HDDs on it, 1 master 1 slave. on primary IDE channel. Using 5.10 nforce drivers.
The best way to reproduce the error is to run CHKDSK /f and /r on one of the slave HDD partitions. Will almost always result in a mouse freeze, with NO BSOD.
The most recent hardware change was replacing old RAM with 2 new sticks of Buffalo Select ram. Ran MS Memory Diagnostic (all 11 tests) and now running MemTest - doesn't look like it's a ram issue. CPU Burn in also seems to not be the issue. I have an Athlon XP-M 2500+ running at 200mHz x 9.5 multiplier, ram set to same frequency 8,3,3,3 timing (the CPU seems to not want to actually run at 133mHzx14 multiplier, which is really weird because that's the stock frequency!)
In any case, I don't think its a CPU/ram issue - I think it seems more like a HDD or IDE controller issue, but what is the best way to find out what's going on?
I am currently running with the slave HDD unplugged, and running CHKDSK on c: without automatic fixing hasn't crashed the computer. Could the slave drive be faulty?