[RESOLVED] STOP : 0x0000 etc

Hi peeps .... ltns

I am just about ready to throw this heap out of the window ... a little history first .. I have 4gb of 3ds max files sitting on this computer, they are all needed desperately for assignment hand-in at uni in two weeks.

now the problem .... I was getting occasional crashes caused (so windows says) by a device driver. These were few and far between so were ignored. Sometimes the system would have difficulties in rebooting and get caught in a loop during restart.

Now ..... my system crashed during rendering processes in 3dmax ... and keeps either looping within the reboot process or coming all the way into a STOP: 0x0 error .... I know that these errors are specific but they are not always the same? this doesn't help when trying to work out what the problem is. Here are the last three stop errors in more detail

1.
BAD_POOL_HEADER
STOP: 0x00000019 (0x00000020, 0x81E42880, 0x81E42880, 0x0A00003C

2.
win32k.sys ... an attempt was made to write to read only memory
STOP: 0x0000000BE (0xBFAD6A0, 0x0B747021, 0xF8614B0C, 0x0000000C)

win32k.sys - Address BF8AA672 base at BF00000, datestamp 43446a58

3.
STOP: 0x000000C5 (0x00000000, 0x00000002, 0x00000001, 0x80550AE2)

ok .... I have searched the forums here as I always do when I get a problem and cannot find anything to help specifically, I have spent hours in the knowledge base following links from other posts.

The problem seems to be getting worse, if that's possible, as I try to get the system running. The most recent successful boot of the system required that I activate Windows, which is strange considering this was done 2yrs ago when I got this machine. it took me 6hrs to get the system booted that time.

Another problem I have come across during my attempts to fix this is the Recovery Console, I tried to use this to repair the XP installation and found that it will not accept my adminstrators password and so locks me out. I am the only user on this pc so there are no other passwords to try. I found article that says I can disable the password for the Recovery module by accessing the local security settings in Administration Tools, but the local settings referred to appear not to exist on my system.

Any help or pointers will be gratefully received ?

VP

This so looks like dodgy RAM (or other hardware, but probably RAM). Try the hard drive in another machine (as a data drive, not booting from it) and see how it goes.

www.memtest.org would definitely be worth giving a run.

You can get a second opinion with this one too:

Windows Memory Diagnostic

first of all thanks for the replies and sorry I took a while to get back ...

ok I know have a computer that won't boot .... I tried repair console and it won't accept my password..... I have been trying to overwrite windows and it stops half way through ... so the set up is only half done. I have tried a different power supply. I took out the ram and tried one at a time ... before I messed with windows but still it made no difference.

I have followed advice and am running memtest86 v1.65 .... this has been running now for almost 4 hours ...23 tests so far no errors. How long does this take and how many tests will it run? It is amazing that the computer has actually showed any sign of life for that amount of time, I am assuming that it is because it isn't using most of the resources.

I have been told that this may be a motherboard problem or a processor problem ... how do I go about finding out? The motherboard is Fujitsu Siemens - D1625-C and the processor is a 3033 megahertz Intel Pentium 4.

Any more ideas?

VP

ok ... I left the memory test running for 18 hours ... no errors were found. I used the memtest86 as referred to in my previous post ... I assume this checks all kinds of memory? Does it test the ram?

I am totally lost now .... how do I find out if my motherboard is faulty or if the processor is dead or dying?

VP

Unfortunately you cannot easily tell, all you can do is substitute a known working CPU for the suspect one.

If you have any computer repair shops near you, it wouldd be worth getting your RAM sticks tested with a hardware memory tester. Software testers such as Memtest have their limitations unfortunately, and so it giving a clean bill of health doesn't absolutely prove that there isn't a problem with the memory.

are you having trouble posting at all? or does it have no problems with bios. if it gets through bios every time, and then errors, id say it was the ram that is the issue. with my laptop it was actually the memory port, the ram wont seat correctly anymore in the port, so i got random reboots stops and sometimes it wouldnt post, sometimes it would.

if it gets through bios and memtest came out ok, the ram is probably ok, though not absolute of course...

have you tried booting from the windows cd and repairing the install? this saved me hardcore.

http://aumha.org/win5/kbestop.htm

thanks for the further replies. I am hoping to convince the local pc shop to take a look at my ram just to put that off the list of possibilites.

As for how far I get on boot ... that changes everytime ... but I usually get as far as the win logo and sometime all the way to the desktop before the system powers off .... errors are rarely seen because the system shuts down


I tried the repair console and was unable to get past the password.
I tried to run the repair from the set up and it didn't work.
I am halfway through setup installing a new XP in a different folder ... it gets as far as networking and then powers off. each time I reboot it goes back to the same stage of set up ... runs as far as the network at the most and then turns off again.

any more ideas?

VP

Are you getting the message described in the following Microsoft link when you try to use the Recovery Console?

http://support.microsoft.com/kb/308402/en-us

Are you plugged into a Local Area Network or using a wireless network?

Have you tried entering the BIOS/CMOS and checking options?

Ah, now is it actually turning off and staying off or is it restarting?

http://support.microsoft.com/kb/318018/en-us

The computer was originally trying to reboot every time it crashed ... but I changed the settings so that it would give me a chance to see any errors produced. This was advised as part of the process to find the stop codes produced by the system when possible. Unfortunately the system rarely boots far enough to get an error message now ... it just stops and the power turns off.

VP

p.s. I took the computer back to the place I bought it and had the hard drive removed and the orginal Adminstrator password reset. I am using the original recovery disk to try to reinstall windows XP to a new folder... it is not an upgrade and has never had a different operating system on it.

Well now, that could be a power supply problem then. If you have, or can borrow, a multimeter, here's how to test a power supply:

Testing PSU voltages

Or alternatively you can buy a proper PSU tester, they don't cost much:

PSU Tester

Hi Supersparks .... sorry but when I was at the shop having the passwords wiped they tried a different power supply on it ... didn't make any difference ... is it still worth checking with a tester?

VP