Frequent BSOD

[vin]

I have a Thinkpad X41 Tablet running XP and frequently experience BSOD with the following Stop: 0x0000008E (0xC0000005, 0x805B2FFF, 0xF8A63924, 0x00000000). I've tested the memory (Prime95), reseated the memory, updated drivers, updated BIOS, cleaned the registry (Registry Mechanic), checked for viruses and spyware (Norton, Ad-Aware, Spybot, SpywareBlaster), defragged, checked for and corrected errors on the disk, ... ...some of these I've done many times. After a hibernation I will sometimes get BSOD or sometimes be invited to log on. After I enter pw, I see my wallpaper but no icons or taskbar show. I can see the disk working on and off. I've let this go for hours or minutes, but have to do the same thing: I press the off button, wait a while and then press on. Sometimes this will startup normally, and sometimes BSOD. Once I get BSOD, I cycle through the startup process several times before success. Sometimes (desperation?) I'll select safe mode. It doesn't always load either, but when I finally get there I'll simply restart or sometimes clean the registry and then restart. Eventually (I might cycle throught safe mode several times), I'll start normally. I've not been able to detect a pattern that works consistently or suggests the root problem. I've been experiencing this for a few weeks now. Am getting by because once I'm succcessfully on I stay on as long as I can.

Would appreciate any suggestions.

I've read that a clean install of XP is probably my best bet. Before embarking on that journey, I wanted to check for other suggestions. (Throwing it out the window at 90 mph has already been suggested.)

Thank you.

[bujie]

fresh copy of windows. format the drive. U might wanna format the entire HDD, deleting the partitions, and create them again.
Let us know.
Cheers!

[mazzinia]

Actually, as a test to rule out the possibility that the problem lies here, would be worth to try removing 1 of the dimms and working for some time, to see if the problem appears again.
If so, taking away the dimm and replacing it with the one that was taken away before.
Then working normally...

If the problem is still there, at least you can for sure say that it's not a memory problem due to a slightly bad dimm or some kind of incompatibility between the 2 dimms due to different latency(sometimes sw tests are not trustable)

[vin]

Thanks for the suggestions. Since my original post, I tried a few more things. I was running Rescue and Recovery 2.02.0178 and after trying to update it I learned that you had to uninstall before installing 4.0. So I did so and everything went fine until restart which resulted in a blank screen with flashing cursor in the top left. IBM suggested bringing it for service, which I did. The technician detected a clicking sound on the disk and now I'm waiting to get it back with a new disk and image.

It's been a great machine; it went around the world twice with me last year, plus many other trips. Love the size and while I wish it was faster it's served me well. I'll update when I get it back.

[egibbs]

According to the MSDN aritcle on 0X8E errors, the parameter 0xC0000005: STATUS_ACCESS_VIOLATION indicates that "A memory access violation occurred. "

If it still has problems after you get it back I'd look closely at the memory.

Ed Gibbs

[tomh009]

Actually a memory access violation doesn't indicate a memory problem. In itself, it indicates that an application or (in this case) a driver attempted to access an invalid memory location, often location 0x0000000. Usually that would be caused by an application or driver bug.

[vin]

A technician called to confirm the hard drive had died ...completely. (Fortunately, I have a backup of my user files.) I've asked to get the machine back without an image and in the meantime I've received CDs from IBM. I like what I've been reading about installing a clean image so that's the plan. Of course, when I pickup the machine I might be tempted to do some shopping ...maybe I'll just bite the Vista bullet.

I'd welcome thoughts and advice on Vista on X41 Tablet (1.5 Gb).

[ragefury32]

Yeah, during these situations you would almost always want to run eventvwr.msc (The Windows event manager) and see if you can eyeball disk controller errors. If you see some, it's time to call it in.

[jonnnny]

Maybe this isn't the same as your situation, but I have a X41 Tablet running NHC to undervolt.

It runs fine most of the time but sometimes when I bring the pen to the screen, I get BSOD. I guess it is because of a sudden jump in voltage. I have since increased my voltage to create a safe 'buffer' zone and everything has been fine.