crashing problem

K

KingTKS

Limp Gawd
Joined
Aug 16, 2004
Messages
148
ok i've been having this problem for a while. My hard drive would crash whenever i was doing harddrive intensive tasks. like copying large amounts of files or zipping stuff.
so i thought it was my Hard drive. RMA's it but still had the same problem. then i thought it was the power supply. so i bought a really nice enermax 485. it fixed it for a while but now its doing it again. reformatting doesn't fix it either. so what could be the problem?
 
What do you mean by "hard drive crash"? I think you'd notice a real hard drive crash ( head crash) a lot more, and it'd never work again. I'd check for memory problems with Memtest86.
 
When i say hard drive crash i mean BSOD and must restart
I checked the ram and it works fine
besides i got it like 4 months ago its corsair xms 2x1gb corsair DDR2 800mhz
could it be the mobo?
 
Is it a SATA hard drive? If it is, swap out the SATA cable with another. I'm not sure if this would cause BSOD in Windows, but I've seen problems in Linux servers at work that were solved completely by switching the cable. Some SATA cables are just bad.
 
KingTKS said:
When i say hard drive crash i mean BSOD and must restart
I checked the ram and it works fine
besides i got it like 4 months ago its corsair xms 2x1gb corsair DDR2 800mhz
could it be the mobo?
Click to expand...

Doesn't really matter how long ago you got the RAM. Computer hardware are somewhat unpredictable when it comes to longevity. Just run Memtest on each stick of RAM for at least 2 hours. Althought it is recommended to run Memtest for a full 24 hours.
 
i wish it was the ram so i could finally figure this problem out but test came out as the ram is fine. no errors
 
Some other things to look for, first line of defence type things before you go RMA'ing more hardware.

Could be CPU heat related, compression and massive file transfers are pretty heavy on CPU usage, CPU heat beyond operating temps (~70c depending on the CPU) will cause BSODs. It'd be helpful if you could provide at least the stop code for your Blue Screens to help narrow it down.

It could also be your RAM timings in the BIOS are too fast for the RAM you have. Sometimes those timing issues do not to show up on memtests. If your motherboard has "TURBO" or "LUDICROUS" speed settings, try stepping back to normal or slow.
 
77 would make more sense, 7d is pretty much only seen at boot of the OS (it's install more memory because we can't load windows).

Anyhoo, 77's are pretty broad in scope for causes. Most I've seen are often caused by bad HD sector (the sector the particular page lives in), motherboard issues (voltage spikes/dips), CPU heat causing the registers to become corrupted (or do other bad things to the data in the pipeline) or bad RAM. But there are other things that can cause them though. If you're consistently getting the same BSOD Stop Code, it really helps narrow it down. Random codes tend to expose more of the CPU heat and RAM timing issues. That said, those aren't hard and fast rules. Just Sherlock Holmes-ian points.

The KERNEL_STACK_INPAGE_ERROR bug check has a value of 0x00000077. This indicates that the requested page of kernel data from the paging file could not be read into memory.

You've done some work in limiting the HD and RAM itself, but it's never a bad thing to run chkdsk and have it look for bad sectors. Do check your RAM timings, and do check your CPU temps.
 
You must log in or register to reply here.
Back
Top