DIGIT-ARC read-only archive · snapshot: July 23, 2026

Windows xp crash reasons

35 posts · originally from https://geek.digit.in/community/threads/windows-xp-crash-reasons.196986/

B
billubakra Original post #1
Apr 15, 2016 at 4:10 PM
Hi Guys,

We have a pc at home. We are using XP SP3 in it from the past many years. From the past couple of months it is crashing/getting bugged after a month or two. Say we shut the pc down properly and the next day when we start it, it will have a black screen which says start windows normally, in safe mode, with cmd or with the last settings or something. If we click on start normally then it will keep on restarting, if we click on safe mode or cmd we get these errors-

*oi68.tinypic.com/2n7gvif.jpg

*oi64.tinypic.com/wl3i9e.jpg

*oi65.tinypic.com/nozr0o.jpg

What does those driver errors etc. mean?

When we click on start with last settings or something, nothing happens.

This pc is used for typing documents in ms word and pagemaker. It has a K7 anti virus, we scan the pc once in a while. The ups is new, so power backup is fine. The fan makes a bit of noise when the pc boots up and then it goes back to normal after few minutes, this thing is going on from the past many years, hope that is normal. The driver or the windows does not give any type of error when it is working fine. So, why is the pc crashing after few months? What could be done to prevent it? The computer repair guy has used different XP SP3 cd's just to be on the safe side in the past couple of months.

Thanks
dashing.sujay
Apr 15, 2016 at 5:06 PM
Your OS is going for a ride. You'll either need to repair or better reinstall it otherwise someday it'll render itself non-bootable.
M
Minion #3
Apr 15, 2016 at 5:17 PM
Repair windows some files are missing that is why your OS is not able to boot.
rhitwick
Apr 15, 2016 at 5:34 PM
Can you check the RAM and CMOS battery?

Seems your OS is not able to recognize it's last state. These two could be causing the issues.
Zangetsu
Apr 15, 2016 at 8:44 PM
I recommend using at least Windows 7 as XP is getting old like Windows 95
B
Apr 15, 2016 at 9:31 PM
Your OS is going for a ride. You'll either need to repair or better reinstall it otherwise someday it'll render itself non-bootable.

Repair windows some files are missing that is why your OS is not able to boot.

Can you check the RAM and CMOS battery?

Seems your OS is not able to recognize it's last state. These two could be causing the issues.

I recommend using at least Windows 7 as XP is getting old like Windows 95

Thanks for replying everyone. This thing happens after every month or two. What could cause this so frequently? We had to call the computer repair guy who would reinstall the windows from scratch after this screen shows up. I have a Win XP SP2 disc with me. Can I repair SP3 with the same?

How and what to check with RAM and CMOS battery? And pagemaker and regional fonts don't work that well with 7 so we had to stick with XP.
dashing.sujay
Apr 15, 2016 at 9:51 PM
Check RAM by running memtest. CMOS battery can be just checked if your windows Date/Time remains correct after reboot.
B
Apr 16, 2016 at 1:38 PM
Check RAM by running memtest. CMOS battery can be just checked if your windows Date/Time remains correct after reboot.

Date/Time remains correct so I guess that the battery is fine. Regarding memtest, is this the correct file (less than 100 KB :confused_NF:) *www.memtest.org/download/5.01/memtest86+-5.01.iso.zip ? So, I burn it on a cd and then boot via it and then run it and post the screenshots here or will it repair the RAM itself? Moreover can I repair XP SP3 with SP2's cd?
B
Apr 17, 2016 at 3:03 PM
Guys should I try repair via SP2 cd?
sling-shot
Apr 17, 2016 at 5:59 PM
If you repair via SP2 CD, you will have to install SP3 again. And all the updates.
M
Minion #11
Apr 17, 2016 at 5:59 PM
Try it if it works then good else reinstall windows.
sling-shot
Apr 17, 2016 at 6:44 PM
Keep on reinstalling each month or two is not a viable solution. Better try to find out the cause.

Is it a hardware error like failing hard disk?
B
Apr 17, 2016 at 10:12 PM
If you repair via SP2 CD, you will have to install SP3 again. And all the updates.

Try it if it works then good else reinstall windows.

Keep on reinstalling each month or two is not a viable solution. Better try to find out the cause.

Is it a hardware error like failing hard disk?

The cd of SP2 didn't work at all, maybe due to scratches or something. Footi kismat. Google also said that it would mess up the system.
[MENTION=139416]sling-shot[/MENTION] Exactly what I am thinking. HDD seems fine because it does not give any hard disk or any error related to that. Just those errors which I posted in the screenshots in the first post. How to find out the cause?

As [MENTION=86068]dashing.sujay[/MENTION] has suggested, CMOS Battery seems to be fine. Regarding RAM, is this the correct file (less than 100 KB ) to run memtest? www.memtest.org/download/5.01/memtest86+-5.01.iso.zip will this repair the RAM for errors or something if I boot via it?

This crashing of windows causes lots of trouble. First it is a time waste, second the computer repair guys take Rs. 500 to install windows in our city. Ye mehangayi kab kam hogi.
sling-shot
Apr 17, 2016 at 10:25 PM
RAM cannot be repaired. Only be checked for defects.

I think that memtest should work.

When this happens next time, before going for a reinstall, physically remove components connected one by one such as printer or bluetooth mouse or whatever and recheck at each step for a successful boot.

Cleaning the contacts of RAM, graphics card etc using Isopropyl Alcohol before reinstalling might help if it is dust/rust and moisture that is causing this.
sling-shot
Apr 17, 2016 at 10:27 PM
By the way, I have just seen the screenshots you posted above and they look like a normal safeboot to me and not errors.

Just select safe mode and wait. Sometimes it takes a few minutes to complete loading and those messages are normal.
B
Apr 18, 2016 at 12:13 AM
RAM cannot be repaired. Only be checked for defects.

I think that memtest should work.

When this happens next time, before going for a reinstall, physically remove components connected one by one such as printer or bluetooth mouse or whatever and recheck at each step for a successful boot.

Cleaning the contacts of RAM, graphics card etc using Isopropyl Alcohol before reinstalling might help if it is dust/rust and moisture that is causing this.


By the way, I have just seen the screenshots you posted above and they look like a normal safeboot to me and not errors.

Just select safe mode and wait. Sometimes it takes a few minutes to complete loading and those messages are normal.

I removed the lan cable and it didn't help. I also removed the mouse and keyboard but then the computer showed an error that no keyboard is there or something. I will run memtest and post a photo of the results here.

I will retry in safe mode and will wait, what if it does start what to do next? BTW what exactly does "normal safeboot" mean and why is it showing up? And those screenshots why is it showing important files from system 32/partition etc. on black screen? Considering this pc is only used for typing, not even an audio file is there so we can rule out the software errors/faults.
sling-shot
Apr 18, 2016 at 12:21 AM
When Windows is not able to shutdown properly, the next time it assumes something went wrong somewhere and tries to load minimum drivers and programs needed to get it started. Safe mode is a minimum environment for troubleshooting.

Those lines are the individual files as they are being loaded. Any errors happening will show up on screen and you will know which is causing it.

Once safe mode is up, using menu restart the computer. Watch what happens.
B
Apr 18, 2016 at 1:01 AM
When Windows is not able to shutdown properly, the next time it assumes something went wrong somewhere and tries to load minimum drivers and programs needed to get it started. Safe mode is a minimum environment for troubleshooting.

Those lines are the individual files as they are being loaded. Any errors happening will show up on screen and you will know which is causing it.

Once safe mode is up, using menu restart the computer. Watch what happens.

Thanks for the info. Will wait after clicking on safe more. Check A.User and Sirluke-'s reply here

*answers.microsoft.com/en-us/window...nwindows/2b3423cd-cf5a-4823-bcdd-4661c24b89b6

Windows XP won't load and safe mode freezes

Worth a try?
Desmond
Desmond #19
Apr 18, 2016 at 11:10 AM
How old is your machine? It could be possible that your hardware is beginning to malfunction. In that case, it would be better to upgrade your machine as these problems will only increase in frequency in the future until your machine stops working altogether.

If you still want to use XP, you can always use a VM software like VirtualBox to run Windows XP over any modern machine with no difference in compatibility or operation.
B
Apr 18, 2016 at 11:31 AM
I waited after clicking on safe mode but eventually it restarted. There was no file with 0 bytes size as mentioned in those two links in system 32>drivers folder. I opened up the cpu and it was clean, I even took out the RAM and reinserted it. Finally I called the repair guy, he said that re-installation is needed. I told him to repair as mentioned in those links, but he didn't know the command for that, he only knew how to clean format so I gave him the command and now the windows seems to be working. IDK but I have a feeling that it will crash again. A friend of mine had an original SP3 disc which he purchased for himself, he has given me the serial key of the same. A question, from where can I download the SP3 setup file and the drivers for this computer so that I can install the windows myself instead of spending Rs. 500 bucks everytime? Still not able to find the reason for this hassle.

- - - Updated - - -

How old is your machine? It could be possible that your hardware is beginning to malfunction. In that case, it would be better to upgrade your machine as these problems will only increase in frequency in the future until your machine stops working altogether.

If you still want to use XP, you can always use a VM software like VirtualBox to run Windows XP over any modern machine with no difference in compatibility or operation.

We bought this machine in 2014. It has decent specs considering our need, Win 7 can run smoothly but the fonts which we need don't work that properly in 7. Here's the CPU-Z report of the machine-
TinyUpload.com - best file hosting solution, with no limits, totaly free
And the people who will be using this system will have no idea regarding VB, they just know about typing, designing and simple xp interface.
Desmond
Desmond #21
Apr 18, 2016 at 12:01 PM
That link is blocked at my workplace. Will check it later.

Using a VM is not hard, you just start it and it runs fullscreen on top of your host OS.

Also, which fonts are you having trouble with? Perhaps we can help you find alternatives.
B
Apr 18, 2016 at 1:28 PM
That link is blocked at my workplace. Will check it later.

Using a VM is not hard, you just start it and it runs fullscreen on top of your host OS.

Also, which fonts are you having trouble with? Perhaps we can help you find alternatives.

The file is attached, I was sending you the same in pm but your mailbox quota is full. Please check and confirm whether the hardware needs any upgrade or not. We only need it for typing and nothing else.

Well please guide me on a VM i.e. how exactly to use it, I highly doubt that the folks will try it. Will try to convince them.

I am having trouble with Hindi, Punjabi fonts. Also with softwares like Summit script manager, 4clipika etc. in 7 and above editions of Windows OS.
Desmond
Desmond #23
Apr 18, 2016 at 1:38 PM
Code:
CPU-Z TXT Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

CPU-Z version			1.60.1

Processors
-------------------------------------------------------------------------

Number of processors		1
Number of threads		2

APICs
-------------------------------------------------------------------------

Processor 0	
	-- Core 0	
		-- Thread 0	0
	-- Core 1	
		-- Thread 0	1

Processors Information
-------------------------------------------------------------------------

Processor 1			ID = 0
	Number of cores		2 (max 2)
	Number of threads	2 (max 2)
	Name			Intel Pentium E5400
	Codename		Wolfdale
	Specification		Pentium(R) Dual-Core  CPU      E5400  @ 2.70GHz
	Package (platform ID)	Socket 775 LGA (0x0)
	CPUID			6.7.A
	Extended CPUID		6.17
	Core Stepping		R0
	Technology		45 nm
	TDP Limit		65 Watts
	Core Speed		2715.5 MHz
	Multiplier x FSB	13.5 x 201.1 MHz
	Rated Bus speed		804.6 MHz
	Stock frequency		2700 MHz
	Instructions sets	MMX, SSE, SSE2, SSE3, SSSE3, EM64T, VT-x
	L1 Data cache		2 x 32 KBytes, 8-way set associative, 64-byte line size
	L1 Instruction cache	2 x 32 KBytes, 8-way set associative, 64-byte line size
	L2 cache		2048 KBytes, 8-way set associative, 64-byte line size
	FID/VID Control		yes
	FID range		6.0x - 13.5x
	Max VID			1.288 V

It says here that your CPU is a Intel Pentium Dual-Core E5400. This was released in 2009 according to Intel's information site and is currently in "End-of-life" status. Did you get this CPU brand new in 2014? If you got it new, then I doubt that it would be faulty. It could be a problem with some other component. Also, let's not rule out viruses or malware.

As for creating VM, you can find detailed steps on the VirtualBox site. You can refer this page: Chapter*1.*First steps
B
Apr 18, 2016 at 3:08 PM
We told the computer shop from where we purchased the computer that we just need the pc for typing and according to our budget he assembled the best components. No, virus's as we are scanning the pc with K7 almost every week. Malware, IDK I think I should scan it via Malwarebytes.

Thanks for VM, I will check that out. Any last piece of advice so that I could save it from crashing next time.

Code:
CPU-Z TXT Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

CPU-Z version			1.60.1

Processors
-------------------------------------------------------------------------

Number of processors		1
Number of threads		2

APICs
-------------------------------------------------------------------------

Processor 0	
	-- Core 0	
		-- Thread 0	0
	-- Core 1	
		-- Thread 0	1

Processors Information
-------------------------------------------------------------------------

Processor 1			ID = 0
	Number of cores		2 (max 2)
	Number of threads	2 (max 2)
	Name			Intel Pentium E5400
	Codename		Wolfdale
	Specification		Pentium(R) Dual-Core  CPU      E5400  @ 2.70GHz
	Package (platform ID)	Socket 775 LGA (0x0)
	CPUID			6.7.A
	Extended CPUID		6.17
	Core Stepping		R0
	Technology		45 nm
	TDP Limit		65 Watts
	Core Speed		2715.5 MHz
	Multiplier x FSB	13.5 x 201.1 MHz
	Rated Bus speed		804.6 MHz
	Stock frequency		2700 MHz
	Instructions sets	MMX, SSE, SSE2, SSE3, SSSE3, EM64T, VT-x
	L1 Data cache		2 x 32 KBytes, 8-way set associative, 64-byte line size
	L1 Instruction cache	2 x 32 KBytes, 8-way set associative, 64-byte line size
	L2 cache		2048 KBytes, 8-way set associative, 64-byte line size
	FID/VID Control		yes
	FID range		6.0x - 13.5x
	Max VID			1.288 V

It says here that your CPU is a Intel Pentium Dual-Core E5400. This was released in 2009 according to Intel's information site and is currently in "End-of-life" status. Did you get this CPU brand new in 2014? If you got it new, then I doubt that it would be faulty. It could be a problem with some other component. Also, let's not rule out viruses or malware.

As for creating VM, you can find detailed steps on the VirtualBox site. You can refer this page: Chapter*1.*First steps
Desmond
Desmond #25
Apr 18, 2016 at 3:16 PM
The VM won't save you from crashing. It will only allow you to run Windows XP over another newer OS such as Windows 7 and above.

Since your hardware appears to be alright, I am not really sure what is really causing your machine to crash.
sling-shot
Apr 18, 2016 at 3:24 PM
Who shuts down the pc at night?
B
Apr 18, 2016 at 3:48 PM
The VM won't save you from crashing. It will only allow you to run Windows XP over another newer OS such as Windows 7 and above.

Since your hardware appears to be alright, I am not really sure what is really causing your machine to crash.

Damm bro. IDK what's up with the computer.

Who shuts down the pc at night?

People who type. They shut it down the way it is supposed to be shut down. Did you check my reply above? Waited after clicking safe mode, but it was restarting.
sling-shot
Apr 18, 2016 at 4:21 PM
I read it alright. I am looking for specific answer, not a generic one.

I am thinking like - do everyone diligently wait till all the fans stop turning or does someone just give a shutdown command and turn off the mains? So each time you see the screen like you have posted in the first page, thr first thing you need to do is track down who turned off at night and ask them specific questions.

Also you said that the computer just restarts after safe boot. I need to know if there was a message just before the computer restarted. It is important to know.
rhitwick
rhitwick #29
Apr 18, 2016 at 4:32 PM
I read it alright. I am looking for specific answer, not a generic one.

I am thinking like - do everyone diligently wait till all the fans stop turning or does someone just give a shutdown command and turn off the mains? So each time you see the screen like you have posted in the first page, thr first thing you need to do is track down who turned off at night and ask them specific questions.

Also you said that the computer just restarts after safe boot. I need to know if there was a message just before the computer restarted. It is important to know.

Agreed!

As we are already looking into s/w issues and h/w ones.
Let's not rule out human error. If possible just be there one day when the PC shut down at night. Just to verify the process is followed properly.

b/w also note down if this safe mode is an everyday issue or has a pattern.

Like every Mon, Wed and Fri it happens etc. Try to take log of at least 2-3 weeks and compare what were different in those days.
B
Apr 18, 2016 at 11:13 PM
I read it alright. I am looking for specific answer, not a generic one.

I am thinking like - do everyone diligently wait till all the fans stop turning or does someone just give a shutdown command and turn off the mains? So each time you see the screen like you have posted in the first page, thr first thing you need to do is track down who turned off at night and ask them specific questions.

Also you said that the computer just restarts after safe boot. I need to know if there was a message just before the computer restarted. It is important to know.

I asked about this and everyone said that they waited for the fans to stop before turning the mains off. I will make sure that the shutting down is done as it should be.
No message dear, after showing the last line of mup.sys it just restarted.

Agreed!

As we are already looking into s/w issues and h/w ones.
Let's not rule out human error. If possible just be there one day when the PC shut down at night. Just to verify the process is followed properly.

b/w also note down if this safe mode is an everyday issue or has a pattern.

Like every Mon, Wed and Fri it happens etc. Try to take log of at least 2-3 weeks and compare what were different in those days.

We do not get the safe mode/black screen until and unless we are screwed. It happens within 20-30 days.
sling-shot
Apr 18, 2016 at 11:38 PM
That mup.sys gives a better clue as I search the internet. See the details are important.

The possibilities now look like the following for me (since they continue to occur beyond total reinstalls they are hardware related)

1. Faulty power supply - ask your computer guy to test the PSU or replace it with a new better one. Go for a reputed brand rather than Chinese.
2. Faulty peripherals - list everything that is connected by cable to your computer. The next time your computer does this, pull out the cables and see if the computer boots into safe mode rather than restarting. USB based things are the most important but check everything anyway.

EDIT:
Here are some links for your reading pleasure
Xp hangs at mup.sys on startup - Microsoft Communit
Unable to boot XP [Solved
Windows XP hangs at isapnp.sys

Good overview about such booting problems - Troubleshoot Windows startup with the Diagnostics and Recovery Toolset and Windows PE

Finally, here is my original search - windows restarts after mup.sys - Google Searc
B
Apr 18, 2016 at 11:53 PM
Thanks for the help dear.

That mup.sys gives a better clue as I search the internet. See the details are important.

The possibilities now look like the following for me (since they continue to occur beyond total reinstalls they are hardware related)

1. Faulty power supply - ask your computer guy to test the PSU or replace it with a new better one. Go for a reputed brand rather than Chinese.

Intex is the one which is in the cpu, the fan makes noise when we boot it and after few minutes it goes back to normal, this thing is happening from years. Will replace the power supply though. Any need to replace side fans too?

2. Faulty peripherals - list everything that is connected by cable to your computer. The next time your computer does this, pull out the cables and see if the computer boots into safe mode rather than restarting. USB based things are the most important but check everything anyway.

PS2 wired keyboard, usb mouse, a scanner & printer(only when needed) and a lan wire. I removed keyboard and mouse wire but it didn't boot.


EDIT:
Here are some links for your reading pleasure
Xp hangs at mup.sys on startup - Microsoft Communit
Unable to boot XP [Solved


Windows XP hangs at isapnp.sys>> didn't find any 0 byte .sys file in drivers folder.

Good overview about such booting problems - Troubleshoot Windows startup with the Diagnostics and Recovery Toolset and Windows PE

Finally, here is my original search - windows restarts after mup.sys - Google Searc
Desmond
Desmond #33
Apr 19, 2016 at 12:13 AM
Dude, you need to at least get a Corsair VS450 PSU and it will save you tons of headache in the long run.

Also, it is normal behaviour for the machine to not boot without the keyboard attached, that is a BIOS function.
sling-shot
Apr 19, 2016 at 12:50 AM
Keep the keyboard, disconnect the mouse and printer.
B
Apr 19, 2016 at 4:22 PM
Keep the keyboard, disconnect the mouse and printer.

Dude, you need to at least get a Corsair VS450 PSU and it will save you tons of headache in the long run.

Also, it is normal behaviour for the machine to not boot without the keyboard attached, that is a BIOS function.


Will keep your points in mind the next time it happens. Thanks a lot.