Sign in with
Sign up | Sign in
Your question

Blue screen crash

Last response: in Windows XP
Share
February 19, 2010 1:50:47 AM

I am running a 6 year old Pentium 4, 2.44 gig processor, 2 gig memory, XP Pro SP3. I have had recurring BSOD for 2 months. After running a mini-dump with BlueScreen View, the problem appeared to be a corrupted ntoskrnl.exe file. I supposidly rebuilt the Boot.ini file, which loads the ntoskrnl.exe file. Still BSOD crashes. I then purchased "Registry Booster", and ran that. Continued BSOD crashes.

I have checked my 1 1/2 year old Seagate HD, and my memory. Both check O.K.

I can send a JPEG of the BlueScreen View if any one can help me figure out the cause of these random crashes. They seem to happen more when the computer is idle.

Thanks for any help.

DK

More about : blue screen crash

a b } Memory
February 19, 2010 2:01:23 AM

If the problem is with the ntoskrnl, and you've already tried to rebuild the boot.ini, try method 3 in this link.
http://support.microsoft.com/kb/314477

If that doesn't solve the problem, try posting the screenshot of the BSOD.
m
0
l
Related resources
Can't find your answer ? Ask !
February 19, 2010 3:11:24 AM

1. Boot into recovery console from Windows XP CD.

2. Rename C:\WINDOWS\system32\ntoskrnl.exe

3. Copy ntoskrnl.exe to C:\WINDOWS\system32 from C:\WINDOWS\system32\dllcache

4. Reboot
m
0
l
February 19, 2010 1:10:48 PM

aford10 said:
If the problem is with the ntoskrnl, and you've already tried to rebuild the boot.ini, try method 3 in this link.
http://support.microsoft.com/kb/314477

If that doesn't solve the problem, try posting the screenshot of the BSOD.


Thanks so much for your suggestion. I don't know how to make a screenshot after a crash. In fact, I can't figure out how to include a jpeg in this reply.

DK
m
0
l
a b } Memory
February 19, 2010 1:20:09 PM

Sorry about that. Obviously, you can't get a screenshot of a BSOD. Bad terminology on my part.

I was simply referring to taking a picture of the screen (camera, phone..etc). You can upload it to imageshack or photobucket, and then paste the URL here.
m
0
l
February 19, 2010 6:54:31 PM

aford10 said:
Sorry about that. Obviously, you can't get a screenshot of a BSOD. Bad terminology on my part.

I was simply referring to taking a picture of the screen (camera, phone..etc). You can upload it to imageshack or photobucket, and then paste the URL here.



Attached is aJPEG of the BlueScreen View mimidump.

Thanks ---- DK

m
0
l
a b } Memory
February 19, 2010 6:56:50 PM

I'm at work right now, the image is being filtered. I'll check it out in a couple hours when I get home.
m
0
l
February 20, 2010 6:02:46 PM

aford10 said:
I'm at work right now, the image is being filtered. I'll check it out in a couple hours when I get home.


I assume you can see the JPEG I sent. I haven't had a crash lately, from which I can copy info from the BSOD.

I am an ME, and without understanding how the system files work, have trouble figuring out what the cure is.

Where can one read about the basics of the Windows operating system? Is is a deep-dark-secret?

Thanks for your help in this matter --- I am appreciative.

D Kruse
m
0
l
a b } Memory
February 20, 2010 6:24:52 PM

It looks like you're getting BSODs, for various different reasons.

They could be caused by several things.

You see in the top window, the column that says 'bug string check?' That's normally the data we would look for in the BSOD, to start looking for the cause. Here's some good reading for what they could mean, with possible fixes.
http://www.geekstogo.com/forum/Windows-XP-Blue-Screen-D...

Another good place to look, is the event viewer (control panel-->administrative tools). It logs system, security, and application errors.
m
0
l
February 20, 2010 7:40:51 PM

aford10 said:
It looks like you're getting BSODs, for various different reasons.

They could be caused by several things.

You see in the top window, the column that says 'bug string check?' That's normally the data we would look for in the BSOD, to start looking for the cause. Here's some good reading for what they could mean, with possible fixes.
http://www.geekstogo.com/forum/Windows-XP-Blue-Screen-D...

Another good place to look, is the event viewer (control panel-->administrative tools). It logs system, security, and application errors.



I looked at the "geekstogo" site. It appears there is no way to determine the exact cause of the crash? I could send you a copy of my event log if you thought it would help. I would need your e-mail, unless you know of another way to send the file.

Thanks,

D Kruse
m
0
l
a b } Memory
February 21, 2010 12:41:38 AM

Are there any errors in the event viewer?
m
0
l
February 21, 2010 2:34:12 AM

aford10 said:
Are there any errors in the event viewer?


Yes, Several errors. Does the event log file include all I see, or does one have to pick a single "error" for the log file?

D Kruse
m
0
l
a b } Memory
February 21, 2010 2:39:01 AM

The event viewer is made up of all the logs.

You can double click on the errors to open the description. Are they all the same, or different?
m
0
l
February 21, 2010 2:52:59 AM

aford10 said:
The event viewer is made up of all the logs.

You can double click on the errors to open the description. Are they all the same, or different?


The errors all appear to be the same. There are several (10 or more) of these errors today, but no crash. The error is; "The max network packet driver (maxNPF) service failed to start due to the following error: The system cannot find the file specified."

Today for the first time, when I tried to open Firefox, I received a crash window, saying "restart Firefox". When I clicked this instruction, I got the same repeat window. I gave up trying to open Firefox --- am using Google Chrome instead.

D Kruse
m
0
l
a b } Memory
February 21, 2010 3:08:01 AM

I'm not sure about the NPF error. I don't think that failed service would be causing the BSOD errors.

You could try reinstalling Firefox to resolve that issue.
m
0
l
February 21, 2010 2:22:52 PM

aford10 said:
I'm not sure about the NPF error. I don't think that failed service would be causing the BSOD errors.

You could try reinstalling Firefox to resolve that issue.


Yes, I did reinstall Firefox yesterday, and it opened 1 time. When I closed it and re-opened, it gave the same "crash" message as before. I was trying to save my bookmarks, but will have to un-install it and start over.

Regarding BSOD crashes, I haven't seen any in the past couple of days. I can't seem to locate any specific errors in the event viewer that relate to the BSOD stops --- maybe I just don't know what to look for. I see on some forum that an old video driver could be causing my problem, but I am skeptical.

When starting-up this morning, the processor was busy doing(?) and the system was very slow. I am thinking the registry is badly messed-up. I have a new hard drive on hand, so it's probably best to bite the bullet and re-load XP pro. I have integrated a current XP SP3 with my SP2 disk, and burned a new disk, using "nlite". I plan on using that disk for the new install. Will the new install pull-up the latest hardware drivers, or will I have to find those on-by-one on the web?

Has Microsoft made their operating systems so difficult to understand that we outsiders must guess at the solutions to these problems, or are they themselves perplexed? It just seems unscientific to throw solutions at problems without knowing what will actually work.

D Kruse




m
0
l
a b } Memory
February 21, 2010 5:38:07 PM

Here's a handy program that can repair your registry.
http://www.ccleaner.com/
If that is the problem, you should see some improvement.

Reinstalling XP is an option. However, yes, you will have to reinstall your drivers.

Drivers are a common cause of BSODs. If you haven't already, you may want to make sure you have the latest graphics and chipset drivers.
m
0
l
February 22, 2010 2:56:02 AM

aford10 said:
Here's a handy program that can repair your registry.
http://www.ccleaner.com/
If that is the problem, you should see some improvement.

Reinstalling XP is an option. However, yes, you will have to reinstall your drivers.

Drivers are a common cause of BSODs. If you haven't already, you may want to make sure you have the latest graphics and chipset drivers.


Just had a crash an hour ago. Computer was left alone at the time. I had previously update the nvidia driver. The BSOD Stop code was:0x--------8E (0xC-----5, 0x80563CA5, 0xF78BE820, 000000000)

The event viewer showed the same "The max network ---" as before. The error code was:
1000008e, parameter 1 c00000005, 2 80563ca5, 3 3i7be820, 4 all zeros.

Maybe this will help.

Thanks again for all your help.

D Kruse
m
0
l
a b } Memory
February 22, 2010 11:11:16 AM

I'm not a network guru, but from what I can tell, the NPF has to do with the LAN/ethernet connection.

If you are using a wireless connection, try disabling the ethernet device in the device manager. If you're using the ethernet connection, try disabling the network connection all together. If the error/BSOD stops, at least it narrows down the cause.
m
0
l
!