Windows Forum

Ask something
Discussion Locked

ARRRRRGH!!!! BSOD!

0 helpful
7 replies

by oz_media

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

ok before I finally get down to a major backup/reformat, I figured I'd trry ONE MORE resource.

I few weeks ago, I started gettnig an error on boot that HIMEM.SYS was already loaded and CONFIG.SYS had errors on line 9.

I fixed it by manually editing the config.sys and commenting out the second HIMEM reference, then extracted a nwe copy of HIMEM.sys. Errors, GONE! YAY!!

Now, during boot, just after the windows start sound finishes, I rendomly get a BSOD with the fatal exception error "0028:C005A123 in VxD ---".

Now the VxD has no program reference following it in order to help me debug it?!? I have done online, manual and registry scans to find a possible worm/trojan of some sort, nada.

The error is intermittent, sometimes after the windows sound plays, and other times when playing Ghost Recon in mid play.

It does seem to be some sort of memory issue when using accelerated memory, but that's just MY guess, don't let me mislead you.

I've removed, swapped and replaced all RAM which seems to be fine. I've removed and reinstaled sound and graphics card (onboard SoudMax drivers with 64MB Visiontek Geforce2MMX card).

At my wiwts end, the PC runs OK other than when multi-tasking, once booted but these errors are getting tiring.

Any ideas?!?

7 replies

by duster52

Ok...some questions first:

1. What operating system? And was it recently upgraded?
2. Do you only get the error at bootup and when running Ghost Recon?
3. What Anit-Virus protection are you running and have you done a full scan recently?
4. Is the OS fully patched with all of the security patches and updates?
5. Did you recently install some new software or hardware?

Troubleshooting stuff:
When you do it get it to boot up, have you changed the screen resolution to something simple and generic like 600x480?

Have you disabled all of the programs and 'features' that start automatically? If that works, then try adding them back one at a time to see if you can isolate which one is causing the problem...

And one other thought...Have you checked the config.sys for syntax errors? Sometimes its the stupidest thing....

by oz_media

Good answers, I have tried most of them, which surprises me.

Perhaps I've stated to learn from you guys.

Thanks for your help, if it is hardware related, I still have 2 yrs onsite service with this machine. It came with 5 yrs new, I'll run their own diagnostics on hardware and see how it looks.

by oz_media

Good points!

Just when you think you remembered everything, WIN98SE, up to date, tweaked and running like clockwork for three years without error (yes WIn98 no errors).

No new software OTHER than e-Trust Antivirus, which I have uninatalled (still same prob) and commented out from startup after reinstalling.

Problem happens whenever I run two graphics progs ex. Having Illustrator open and opening Fireworks in the background, which always USED to work. Ghost Recon when things get busy or too much is drawn on screen.

When booting it will happen two times after/during the Windows start sound, third time always boots properly.

Have tried all your other suggestions, however don't remember if I tried screen resolution or not, although I have tried reducing hardwae acceleration to none.

I think it is memory related because it happened after resolving a HIMEM issue where HIMEM was already loaded and config.sys was trying to reload it. I commented out the HIMEM reference using 'rem' but didn't change other parts of config.sys, from what I can see, syntax is OK. If you think you may see something I didn't (I'm a novice there) I'd be happy to send you a copy of the config.sys

After fixing the HIMEM errors, I now get this problem with the BSOD/Fatal Exception Error.

This is making me think it is memory related, everything is fine until I multitask or place a demand on graphics acceleration by multitasking.

by hereinoz

If it is intermittent, that changes things. Just a couple of thoughts.

I have had BSODs that were supposed to be memory related, but weren't. Given that the thing has been spinning along for 3 years, I would do two things.

1. Re-seat the processor. Not a bad idea when you re-seat it, (don't listen to this, Chas) partially close the zif socket so the pins have a little bit of resistance going in, and gently (very gently and carefully) push the processor in and out a few times against the resistance. This will help clear any guff that is on the pins. (Don't try this at home, kiddies).

2. After it has booted successfully, can you then re-boot it successfully straight away?? I reckon so. If you can, it is possible that the Hard Drive is a tad dodgey, so when the thing is up and running OK, ghost the Hard Drive over to another HDD and use that for a while. If problem still there, probably not drive. If problem goes away, send drive on an extended holiday.

I just hate these intermittent BSODs. I had one on an old 233MHz machine once and it drove me crazy. Memory page errors, the lot. In the end, the processor re-seat sorted it.

Good luck.

Alan

by hereinoz

You could try doing a quickie install of Win98 on another drive in that machine. If the problem goes away - it is operating system. If it is still there - it is hardware.

Better yet, ghost the original system off to another drive, and do a quickie install of Win98 on the original drive in the machine. See what happens.

Alan

by oz_media

Good answers, I have tried most of them, which surprises me.

Perhaps I've stated to learn from you guys.

Thanks for your help, if it is hardware related, I still have 2 yrs onsite service with this machine. It came with 5 yrs new, I'll run their own diagnostics on hardware and see how it looks.

NOTE: I do have an image on another 120 GIG, it runs OK though, so I'd have to agree it may be hardware related. I'll run the hardware tests and get it replaced, they are very quick to send out techs and new hardware up here. Probably within 48hrs.

Cheers,

This discussion is closed to new replies.