bugcheck

Topic

New Reply

On a 3 month old PIII 733 I built for a little old man at the church using Windows 2000 (hey it was that or Win 95), 256MB RAM He is getting an error I have not come across before. The system ran 3 weeks at my house fine. He installed Juno for internet and had some neighbors install some Christian screen savers and a Christian research program.
The PC reboots now at random times. There is a quick Blue screen which I tracked down to state “The PC has rebooted from a bugcheck. blah blah blah 0x00000001e (a bunch of memory addresses and more useless stuff. It did point to a minidump folder that had 65 minixx.dmp files I have not found a program to open them.
I checked and watched power. The power supply is fine. Circulation is great. There is a CPU fan (that came with the CPU), a front case 80mm fan and of course the power supply fan. There was no dip in the power or fan speeds during the reboots that happened while I was there. Yes the unit has a new surge protector. No the line voltage did not drop.
There are no event logs or .chk files of any kind just these dmp files. Any ideas?

Reply | Quote

Replies

Does this kb article, http://support.microsoft.com/default.aspx?…;EN-US;Q266221&[/url] sound like the problem?

Reply | Quote

Similiar but not it. I am not very good a using the MS knowledge base. I found nothing with the complete stop code.
0x000001E (0x0000005, 0xa00179F7, 0x0000000, 0x0000000.
I did try to run some updates I had burned on CD (Qxxxxx) but I had been building another PC at my house and left all my updates disks. I will try to run all updates I have and then have him connect to the net and run the critical updates. He is in the “woods” and only gets 26.6 if he is lucky.

Reply | Quote

Another idea is to look at some of the pages returned by a google search on bugcheck.

I don’t use MS’s search on the KB, I use either Google or http://www.freeanswers.com[/url%5D

Reply | Quote

I had tried google to no avail and totally forgotten about freeanswers (they were in my favorites, just forgotten).
Still no luck using them though.

Reply | Quote

Whatexactly is the stop code’s error text?

BTW, the DUMP files you’re referring to are physical RAM dumps onto the harddrive. You can disable that option in the System control panel applet and I’d delete them – there will likely be nothing of use to ever come of them and there is nothing that you can use to open them.

Try booting with the WIndow 2000 CD and selecting the Repair option. Allow repair to check everything, top to bottom. And tell the guy to smack anyone’s hands who attempts to install software in the future.

Reply | Quote

Stop text. Unfortunately there was none what was reported that I have not already shown was the last line after the … 0x0000000): Microsoft Windows 2000 v15.2195. Dump saved in c:winntminidumpmini08.dmp.

Reply | Quote

Sorry Kent, what I meant by stop text was the message that appears on-screen, such as IRQL_NOT_LESS_OR_EQUAL – something along those lines – which is then followed by the hex addresses you already noted. More often than not these do not appear in the event viewer, they only appear on-screen when the STOP actually occurs.

Reply | Quote

Unfortunately the Blue Screen flashes on and off before the reboot. The screen is only up about 1/4 of a second.

Reply | Quote

Can you disable the “Automatically reboot” option to prevent this? It’s located in System Properties, under the Advamced tab – click on Startup and Recovery and you should see a dialog as in the attached screen shot.

Reply | Quote