WinXP SP2 - BSD - Help?

[mz_]

Alright, system information is in my sig.

I was running BIOS 1901, overclocked at 3.3GHz. Started to get all kinds of program errors; Firefox, Winamp, Newsleecher.

Decided to reboot, and kept gettting BSD's that said the following;

STOP: 0x0000007E (0xC0000005, 0xF74FAA62, 0xBAFFFBD4, 0xBAFFF8D0)

or, the above, with this added;

wmxlcore.sys F757AA62 base at F7577000 datestamp 425c8225

Right before I rebooted, windows popped up saying "Corrupt c:\windows\prefetch".

After rebooting a few times, and getting those BSD's, I tried Safe Mode and Last Know Good Config, I'd get as far as the Windows Logo and then BSD again. Tried another reboot, and no POST, no beeps, no video. Cleared CMOS via the jumper, and was able to get back in using the Defauly BIOS setups, and upgraded BIOS to 2001 from 1901.

So here I am now, on 2001 and Default BIOS. Was this an issue with the overclock? System has been between 40-45C with spikes to about 55C depending on what I'm doing. Not sure why all the program errors and BSD's. Could Windows be corrupt? Thanks for any help guys.

[Gizmo]

I'd be inclined to suspect an unstable overclock. However, you may have corrupted windows with all the BSODs before you reverted back to default settings.

Will the system boot to windows now that you have gone back to default settings?

[mz_]

Yeah, I've been using it since I've posted that message. I had to reinstall WinRAR and Winamp to get them to work again.

Still using default settings with 2001 BIOS. Temps now are at 28-31C. This is all on Air Cooling. 2x120mm Front Intakes, 1x90 & 1x120mm Rear Exhaust and 1x90mm Top Exhaust. CPU Fan is a Zalman 9700.

I'll have to try and reboot again at some point and see if I get another BSD.

[Gizmo]

What did you use to test the stability of your overclock?

Most overclockers have a set of applications they use to abuse their systems to see if they are stable, because there is 'Benchmark stable' and then there is 'Usably stable'.

I generally use a combination of Prime95, SuperPI, and CPUBurn for CPU overclocks, and Memtest86 for RAM/FSB overclocks. I never run CPUBurn for less than 20 minutes, usually for more like an hour.

[Toro]

this page http://www.aumha.org/win5/kbestop.php has some good information on it,and can give you a few pointers on where to start looking. I would look at checking disk integrity as it is warning of corrupt files. Also maybe do some RAM tests as well

[YadaMaker]

hd's corrupt. boot to Windows cd; choose Install Windows on existing partition; select Repair option (not Repair Console option) that shows up on following screens.

You'll likely have to reinstall all your best drivers after you get back to Windows, but it should only take about 15 minutes to get back to there, max.

cool?

[Aedan]

As pointed out, an unstable overclock can lead to hard disk corruption. Why? Well, when the CPU/RAM is returning data that isn't quite right, and that data is located in Window's hard disk cache, it can get written out to the hard disk.

Thus, after a number of overclocking related BSODs, a Windows installation is suspect anyhow.

[Samuknow]

Another good test for a stable OC is to load up FAH. It will max you CPU(s) 100% and serve the cause as well.

But to agree, sounds like unstable OC and a corrupt drive.

[Aedan]

Originally Posted by Samuknow

Another good test for a stable OC is to load up FAH. It will max you CPU(s) 100% and serve the cause as well.

Personally, I'd not use FAH as a test for a stable OC. That's mainly because FAH is relying in accurate calculations and a marginally stable OC could cause inaccurate answers to be sent back to FAH.

[Samuknow]

I guess that is true. I do know that my OC that I thought was stable for many months bit the dust when I started Folding again. It absolutely pushes the temps and cpu to the limits.