Help with BSOD
Discussion
In my ongoing battle to fix my friend's laptop I have managed to get a running windows system on it, by restoring from the Symantec Ghost restore partition, but it continues to BSOD, or at least give some errors. Now I checked out one of the error codes and it says it is a faulty graphics driver, which I have replaced, but have yet to find out if the machine is stable.
After getting it running the computer connected to automatic updates, updated itself then BSODed again giving an error code which told me absically to reinstall windows.
Now I have gotten it running again but the question is do I install SP2? It is a Windows that ships with SP1. As I said before when I tried the updates via net it killed the computer.
NEC will not support the machine as it is out of Japan (where is was bought) and Microsoft will not support because it is an OEM copy of XP.
I have managed to get hold of a Japanese copy of XP, and I think most of the drivers (bar the mobo ones).
But anyhow these are the codes I am getting on the BSOD
0x0000008e (0xc0000005, 0x80535f7b, 0xee2df840, 0x00000000)
The only other thing I think it could be is Thermal or a bad RAM chip??
After getting it running the computer connected to automatic updates, updated itself then BSODed again giving an error code which told me absically to reinstall windows.
Now I have gotten it running again but the question is do I install SP2? It is a Windows that ships with SP1. As I said before when I tried the updates via net it killed the computer.
NEC will not support the machine as it is out of Japan (where is was bought) and Microsoft will not support because it is an OEM copy of XP.
I have managed to get hold of a Japanese copy of XP, and I think most of the drivers (bar the mobo ones).
But anyhow these are the codes I am getting on the BSOD
0x0000008e (0xc0000005, 0x80535f7b, 0xee2df840, 0x00000000)
The only other thing I think it could be is Thermal or a bad RAM chip??
If it will stay alive for any length of time you could debug it to be sure. Will it go on the net and stay there for a bit? How good are you at advanced troubleshooting?
If you're happy to get dirty with it, look up how to download/link to the debug symbols on the microsoft site and look through the .dmp file once it has crashed. You'll want to enable complete memory dumps if you choose this route.
The reason I haven't completely explained it is if you can figure out how to do it, you should be able to interpret the results. If you can't, it's too scary
Clue, !analyze -v will pretty much tell you what's wrong if it's a driver.
If you're happy to get dirty with it, look up how to download/link to the debug symbols on the microsoft site and look through the .dmp file once it has crashed. You'll want to enable complete memory dumps if you choose this route.
The reason I haven't completely explained it is if you can figure out how to do it, you should be able to interpret the results. If you can't, it's too scary
Clue, !analyze -v will pretty much tell you what's wrong if it's a driver.
Yep it will go on the net for a while and it stayed alive for around 2 hours yesterday but died after a restart. Then was very unstable for the next hour. It's very intermittent. My biggest problem is that the drivers are available in Japanese only and only via the recovery image, or I would just kill the windows system and put a new copy on it. I'm not too hot on debugging, but I think I'm about to start learning. I have kept the .dmp files from the system and am going to go through them, if I can work out how to use reader properly.
Any help is much appreciated.
edited to add, I have yet to test the ram, but I will do that when I next look at the system tomorrow.
>> Edited by Wildfire on Wednesday 25th January 11:16
Any help is much appreciated.
edited to add, I have yet to test the ram, but I will do that when I next look at the system tomorrow.
>> Edited by Wildfire on Wednesday 25th January 11:16
You actually issue the command in windbg once you've linked to the symbols. You should be able to get the majority of what you need to know from this link.
http://support.microsoft.com/kb/311503/en-us
HTH
http://support.microsoft.com/kb/311503/en-us
HTH
Sorry, missed that.
UK XP, very doubtful. MOBO drivers, highly likely. There is also a fix for hibernation type errors in XP SP2
Put 0x0000008e in the search box on http://support.microsoft.com and it'll give a list of possible resolutions.
UK XP, very doubtful. MOBO drivers, highly likely. There is also a fix for hibernation type errors in XP SP2
Put 0x0000008e in the search box on http://support.microsoft.com and it'll give a list of possible resolutions.
If you've got a floppy drive for it, I'd make a memtest86+ boot floppy from www.memtest.org/ and let it chew on that for a few hours, see if it comes up with anything?
annodomini2 said:
Have you tried installing UK XP?
I can't install a UK XP as the drivers are not accepted by a UK version and the computer needs to be in Japanese for my friend to work on it.
Finding the Mobo drivers is proving to be very difficult. I am going to check all the hardware integrity tomorrow with UBCD.
Try to isolate whether it is the hardware or the OS by using this and do a burn-in test. If the machine is stable under BartPE then you can start to investigate the XP install by doing a vanilla install and then adding in drivers one at a time until you get instability. If the machine isn't even stable under BartPE then you're going to have to investigate hardware components like RAM.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff