• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Blue Screens in XP?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
In the error line it says 0... but in the bottom it says things like... interrupt not where expected and stuff like that
 
In the error line it says 0... but in the bottom it says things like... interrupt not where expected and stuff like that
Click to expand...
That's a new one. You might want to double check all your bios settings and make sure everything is seated properly (IDE cables, PCI/AGP cards).

Also, how are your temps doing? Overheating can cause strange errors. Try to keep your system temp below 50C.
 
I was having daily BSOD on my T6000 (AMD64/WinXP Home, Pro and XP64) did not matter what OS. The system has been ok now for 3 days. Like many here I tested everything; I then did the following: FDisked the hard drive 3 times, then ran Fdisk /mbr 5 times in a row and used the recovery CDs. Then did only the critical updates from the MS site. Then installed my programs and then did the none critical updates. Then and this might be the KEY: I ran a program called BootVis. Bingo no more BSOD and I was getting about 3 of them a day. Sounds like voodo I know... 2 cents...
 
Even memtest is not to be fully trusted; In my system, since my memory is incompatible with the mobo, I get LOTS of errors in memtest(always in the 8 most significant bits and @400mhz, I didn't run memtest @333mhz). When I put the same memory modules in my brother's system, memtest shows no errors at all, even running 10+ hours. So it's just the mobo's memory controller that's not addressing or receiving the data correctly.

The best resource that we have for these errors are still the BSOD's. If you gets lots of different ones, it should be memory, or a damaged / insufficient pagefile. If it's HD or PSU related, I think you would always get the same error. But who knows for sure... we can only wait nags's memory and PSU to arrive... could you test just the memory first for a few days, and if the errors persist, then try the PSU?

Today is a very lucky day for me... I didnt get even one BSOD since yesterday!! 😀

Maybe we should write an article about all this when we finally discover... it would save much time and easy the life of many 😛
 
It's now getting ridiculous! I'm getting them non stop.. And my computer is randomly restarting by itself. Most commonly when I'm running something processor intensive like a virus scan or something like that. The computer is also being very slow
 
If you're getting only STOP 0x0A's and STOP 0x50's, it's most likely a driver.

If you're getting other STOP codes, particularly 1A's or 4E's, then it's likely RAM.

If replacing RAM hasn't solved the problem, then it's quite possibly the motherboard.

If memtest is giving you errors, then it's OBVIOUSLY hardware. Again, if replacing RAM hasn't solved the problem, it's the motherboard.

Sectoid: You either have a problem in your disk subsystem or you have a bad sector in your pagefile. I'd move my pagefile to a different disk then do a full chkdsk on the drive where it was.
 
Patient: "Doctor, it hurts when I bend my elbow like this."

Doctor: "Then don't bend your elbow like that."

In other words if something specifically is giving you trouble, stop doing it. Obviously you need to fix whatever the problem is (and as a hint, it is probably not a virus, so you can stop that anyhow for now). It seems fairly clear to me that the problem is hardware related. If replacing your RAM hasn't helped, move on. Have you tried a different power supply? If not try to do so, as was mentioned earlier this could be your problem too. If you don't have or can't borrow one, disconnect all extra devices (optical drives, extra fans, lights, etc). Basically run bare minimum hardware and see if the problem is resolved or not. If running with minimal hardware fixes the issue, replace your power supply. If not the RAM, and if not the PSU, you can check your hard drive for damage, though this is not likely to be the problem. After these things, I would say replace your motherboard.

\Dan
 
Basically right now I'm just waiting for my new memory and power supply. I'm just getting antsy and messing with other things:wine:
 
Damn I was finishing my reply when I got a BSOD. I HATE THAT!!!!

nags: If you use Norton, check it's support page or try changing your antivirus software. When I was researching about my problem, I found that it can lead to BSOD's in certain systems. They have a workaround there.

noggin: already done that. I have 2 HD's, the secondary I use only for backups. None of them has errors. Since I was already going to format the second, I created a partition with 2.5GB just for the pagefile(wich should use a bit less than 1.6GB in my case). No luck. The disk warnings that I get in eventviewer just moved to the other partition as well. No more warnings in the primary. I then tried changing the pagefile mode from "custom size"(default option) to "system managed size", as this is listed at Microsoft's site as a solution to some STOP errors(nags, you should try that too, I forgot about this before), but didn't solve my problem either. Now I'm using custom size but forced it to "1536MB-2400MB" or something like that, when the default is "2MB-1536MB". No change in situation.

If only my memory had the option of ECC checks, I could be sure it's it... but then, my mobo wouldn't support it anyway 😛
 
Now when I reboot I'm getting an error in the bios saying "CPU is Unworkable. Please check SoftMenu"

Everything looks fine in the bios though :|
 
That's strange, are you OC'ing? Did you ever get this before? If it's CPU related, I would try raising the CPU voltage just one little bit, because my ABIT mobo, for example, displays 0.1V more than it's truly using. AND it has problems in two other voltages(1.85 and 1.875 I think). Try searching for info on your board here in this forum. Give me your mobo's model too, I'll help you search, there are some really good brazillian hardware forums.

It could really be your PSU too, is it branded or generic?? How much power does it supply?

Now I don't know what to think about your case, it's surely hardware related, but I never saw bad memory leading to an error like this. Send ABIT an email, maybe they know what is causing this.
 
Nope, not OC'd or anything.. It's a very new system. My new powersupply and replacement memory got here today. I'm going to install in a bit and report back later.

Thanks so much to everyone that has helped so far.

-nags
 
Ok, just installed the PSU and memory..Started it up and immediatley got an error saying there is a problem with services.exe and the computer is shutting down. First time I've seen this one
 
man you're lucky 😛

try putting the old PSU back and see what happens... then the old memories with the new PSU.
 
Nice.. just rebooted on its own again....... it does that anytime I do anything somewhat intensive on the computer... was just transferring some files over
 
Just called Abit. I'm now awaiting a new motherboard:|

Thats the only thing I can think of to fix my processor error now.

 
well if you exchange the mobo, memory and PSU, reinstall your SO, and it still happens, you can either change your processor or throw it all through your window 😛

If I manage to sell my memories and buy new ones, I'll post here what happens.
 
I'm thinking about just calling intel now to get a replacement on the processor. That way everything will be new 😀
 
you know your system is probably getting royally screwed with all the BSOD's, you really need to format it and start fresh to properly test the new replacement hardware.
 
Originally posted by: nags
I'm thinking about just calling intel now to get a replacement on the processor. That way everything will be new 😀
Click to expand...

If your proc were bad you'd be getting STOP 0x9C blue screens most likely.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top