Computing.Net > Forums > Windows XP > Another random reboot problem

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Click here to start participating now! Also, check out the New User Guide.

Another random reboot problem

Reply to Message Icon

Name: sponge14
Date: November 5, 2004 at 08:21:28 Pacific
OS: Windows XP pro SP1
CPU/Ram: Athlon 2700, 512mb SDRAM
Comment:

Hi, I am having my own random reboot problems here. Most of the times the reboots have this reported in the error log:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xe2001000, 0x000000ff, 0x00000001, 0xbf8120ef). A dump was saved in: C:\WINDOWS\Minidump\Mini110504-01.dmp.

My system:
AMD Athlon 2700+ Barton
Win XP pro SP1
512 mb ram, new ram because I thought this might have been the problem
Leadtek WinFast K7NCR18G
DVD burner
3 hard disks
Radeon 9800 pro, fairly new installation

I had this problem before the 9800pro, but it was a bad power supply. I have a nice new power supply, and new ram. I suspect its the video card but have no clue how to determine this for sure, hopefully some of you guys can tell me by the error code I have given.

Oh, I have turned off the auto reboot as you have said to do in other threads but haven't had a restart yet. When it does reset there is no BSOD, the screens go black and I am staring right at the screen when it happens. Thanks for any help you guys can give me!!!!



Sponsored Link
Ads by Google

Response Number 1
Name: sponge14
Date: November 5, 2004 at 08:23:08 Pacific
Reply:

Oh and I wanted to add I am using the dual montor feature of the 9800pro, if that means anything


0

Response Number 2
Name: Pistal
Date: November 5, 2004 at 08:54:46 Pacific
Reply:

Try this it will not hurt and it is simple, if it does not fix the probem, then other people will advise you, but I had some rebooting in the middle of things, so I ran a SFC /scannow, It will check and see if you have any windows corrupt files, I had (2) and it fixed them and I have not had any random reboots since.


0

Response Number 3
Name: Grok Lobster
Date: November 5, 2004 at 09:37:47 Pacific
Reply:

Check for swollen/leaky capacitors on the motherboard.


0

Response Number 4
Name: cpc2000
Date: November 5, 2004 at 15:47:40 Pacific
Reply:

The failing address is 0xbf8120ef which is win32k.sys. I don't think win32k.sys has software problem. Whenever XP/W2K crashes, a system event log and minidump is written. Change system event log and look for the record id 1001. Copy the the content of all the record id 1001 and repost. Let me help you to analyse what is root cause of the problem. 90% of Bugcheck D1 is related to software and 10% is related to faulty ram.

Procedure to locate system event log
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Record id 1001

Hope it can help you
Albert


0

Response Number 5
Name: sponge14
Date: November 5, 2004 at 18:37:37 Pacific
Reply:

I have 21 of them!! :-o
You are really great for helping me with this , thank you!!!

-------------
The bugcheck was: 0x000000d1 (0xc73cfffa, 0x00000002, 0x00000001, 0xf6ea2519).
-------------
The bugcheck was: 0x1000008e (0xc0000005, 0xbf87ae01, 0xf7706a30, 0x00000000).
------------
The bugcheck was: 0x0000004e (0x00000099, 0x000159c0, 0x00000003, 0x00000000).
------------
The bugcheck was: 0x0000000a (0x9980c0cc, 0x00000002, 0x00000000, 0x804e0dfb).
-------------
The bugcheck was: 0x000000d1 (0xe1e00000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe1c22000, 0x0000001e, 0x00000001, 0xbf8120ef)
------------
The bugcheck was: 0x000000d1 (0xe1e13000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe2398000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe22c3000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe1fc8000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe2272000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe2058000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe1233000, 0x000000ff, 0x00000001, 0xbf8120ef)
------------
The bugcheck was: 0x000000d1 (0xe12e8000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe1f3f000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe2095000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe204f000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe1fda000, 0x000000ff, 0x00000001, 0xbf8120ef)
------------
The bugcheck was: 0x000000d1 (0xe12b8000, 0x000000ff, 0x00000001, 0xbf8120ef).
------------
The bugcheck was: 0x000000d1 (0xe2001000, 0x000000ff, 0x00000001, 0xbf8120ef)


0

Related Posts

See More



Response Number 6
Name: cpc2000
Date: November 6, 2004 at 04:56:06 Pacific
Reply:

The abend instruction address from 5 to 21 minidumps are 0xf6ea2519. I believed that this is a software error. For faulty ram the failing instruction should be different.

The abend instruction of the first minidump is not within win32k.sys. If you use Microsoft windbg to process the dump and find out the failing module name. Most likely it is the culprit. The system event log of this entry has the minidump name.

1st minidump
The bugcheck was: 0x000000d1 (0xc73cfffa, 0x00000002, 0x00000001, 0xf6ea2519).
You can find the failing module using windbg

2nd minidump bugcheck code 8E.
3rd minidump bugcheck code 4E.

Diagnostic bugcheck code 8E and 4E requires full dump.

4th minidump
The bugcheck was: 0x0000000a (0x9980c0cc, 0x00000002, 0x00000000, 0x804e0dfb).
The failing module is ntoskrnel.exe and ntoskrnel.exe is the victim and not the culprit.

5th - 21 minidump the failing module, I beleive that it is win32k.sys and it is not the culprit. Diagnostic problem caused by win32k.sys requires full dump and you only have minidump.

The size of the minidump is below 100K.
If you upload the 1st and the last minidump into a public website, I can download and process the dump. Maybe I can find out more information.

Hope it can help you.
Albert



0

Response Number 7
Name: sponge14
Date: November 6, 2004 at 09:11:09 Pacific
Reply:

I changed the settings to do a full dump next time. I have the minidumps 1-4, and the last one picked out and just need to find a place to upload them. When I do I will post a link here for you. Thanks again so much for your help!!!


0

Response Number 8
Name: sponge14
Date: November 6, 2004 at 10:23:52 Pacific
Reply:

I have the full 511mb dump from a D1 error I just got a few minutes ago. What would be the best way to get this file to you? I also have the 4 minidumps that I told you about last post.


0

Response Number 9
Name: cpc2000
Date: November 6, 2004 at 11:43:07 Pacific
Reply:

Hi Sponge14,

Email the first 5 minidumps to me. My email is martin_ao_123@yahoo.com.hk. I will let you know my finding.

Reggards,
Albert


0

Response Number 10
Name: cpc2000
Date: November 6, 2004 at 20:32:13 Pacific
Reply:

I've received the minidump. The failing module of the 1st dump is portcls.sys. I have no idea about this module. I do quick search at Goggle there some reported case that portcls.sys caused blue screen but no solution. I have to do some research and get back to you.

From the dump, I also find out you are using Nvidia Display Card. You can say I am bias on Nvidia Display Card even my PC is also Nvidia Display Card. I've resolved a three cases this months relating nVidia Display Card crash XP, hang up XP and crash W2K. It had better to upgrade the Nvidia Display card display and it may resolve your problem.

My guest is correct. The failing module of the last dump is win32k.sys. It fails at a copy instruction. The stack trace of the minidump is limited hence I have no idea the culprit caller.

Regards,
Albert Cheng


0

Response Number 11
Name: sponge14
Date: November 6, 2004 at 20:46:41 Pacific
Reply:

You repeatedly say that you see that I am running an NVidea display. I have an NForce motherboard, which has a GeForce video card built into it. However, the video card I am actually using is the ATI Radeon 9800 PRO. If you meant to say that you saw me using NVidea hardware, this could be the problem. I am going to try and remove all the NVidea video drivers and re-install my ATI video drivers. Please give me your input on this! THANK YOU!!!!!! -Nick


0

Response Number 12
Name: cpc2000
Date: November 6, 2004 at 20:46:49 Pacific
Reply:

The the first two minidumps showed that your PC had nVidia Display Card. The last dump showed that your PC does not used nVidia Display Card. When do you change th display card? After you change do you got more blue screen than before?


0

Response Number 13
Name: sponge14
Date: November 6, 2004 at 21:16:53 Pacific
Reply:

I put the new card, the 9800 PRO in about 2 weeks ago. I rarely had a blue screen problem before. It has to be the video card right? You said that it's probably software and I am running programs to make sure I have all the old drivers removed.


0

Response Number 14
Name: cpc2000
Date: November 6, 2004 at 21:20:51 Pacific
Reply:

I think this is ATI display card driver.


0

Response Number 15
Name: sponge14
Date: November 6, 2004 at 21:34:01 Pacific
Reply:

You think that it is the ATI display driver that is causing the problems? I have uninstalled the old video drivers and am waiting to see what happens. I will try anything else you tell me to, to try and fix this damn machine! -Nick


0

Response Number 16
Name: cpc2000
Date: November 6, 2004 at 22:24:05 Pacific
Reply:

Nick, Good Luck! Repost if you have new finding.

Albert



0

Response Number 17
Name: sponge14
Date: November 7, 2004 at 11:17:02 Pacific
Reply:

I have every single old video drver off my computer and it is still crashing. You say it's the ATI driver crashing the system from those minidumps you have? What would be the next thing you would do?


0

Response Number 18
Name: cpc2000
Date: November 7, 2004 at 11:44:55 Pacific
Reply:

Email the last minidump to me


0

Response Number 19
Name: cpc2000
Date: November 7, 2004 at 12:28:37 Pacific
Reply:

Do you mean you uninstall and remove the ATI display card? Now you are using Nvidia Display card.


0

Response Number 20
Name: sponge14
Date: November 7, 2004 at 17:26:03 Pacific
Reply:

No, the Nvidia was the old card, it is built into the motherboard. I uninstalled the drivers for it last night. My card that is in the computer, and that I am using now is the ATI Radeon 9800 PRO


0

Response Number 21
Name: cpc2000
Date: November 7, 2004 at 17:56:17 Pacific
Reply:

Of course it fails, you are still the ATI display card driver. Download the latest TI display card driver from ATI Website and it will fix your problem.


0

Response Number 22
Name: sponge14
Date: November 7, 2004 at 21:54:51 Pacific
Reply:

I think you are misunderstanding me. I uninstalled the NVidia drivers, and I have the ATI drivers and the ATI card installed.


0

Response Number 23
Name: cpc2000
Date: November 7, 2004 at 22:21:13 Pacific
Reply:

Please refer response 12. I suspect ATI display card driver is the culprit. Uninstall nVidia display card does not resolved. The minidump showed that no nVidia Display card is found in the last dump and I can find ATI display card driver. Uninstall nVidia Display card does not resolve the problem. Response 10 says that a lot of XP users have problem at nVidia Display card driver and not all the XP users. If the user crashed due to Nvidia Display card drvier, they should upgrade the Nvidia Display card driver. Nvidia Display card driver is no longer in use at your Windows hence Nvidia display card driver is not culprit for the blue screens within this two weeks.

As you installed the ATI display card two weeks ago and then your PC got a lot of blue screen. Obviously ATI display card is the culprit.


0

Response Number 24
Name: sponge14
Date: November 8, 2004 at 09:45:57 Pacific
Reply:

Ahhh I see what you are saying now, thank you for clearing it up for me. So is it the drivers that are having problems, or could it be the card itself? I am pretty sure you will say its the drivers. Would reinstalling Windows XP and the video card drivers help? I am not affraid of reinstalling Windows, I do it all the time, it's just a bit of a hassle. Thank you!!!!!! -Nick


0

Response Number 25
Name: cpc2000
Date: November 8, 2004 at 14:22:57 Pacific
Reply:

It is no need to re-install Windows. Upgrade the ATI display card driver will resolve the problem.


0

Response Number 26
Name: sponge14
Date: November 9, 2004 at 19:17:11 Pacific
Reply:

I have installed the latest drivers, and I needed to reinstall Windows anyways so I have:
1) Formatted the HD that windows is installed on, and formatted another HD that is just for extra storage

2)Installed the latest drivers for the ATI card.

I will see how these new drivers work. I have heard alot of bad things about them and their compatibility with the games I play, hopefully it wont effect me. Thanks for all your help! -Nick


0

Response Number 27
Name: cpc2000
Date: November 9, 2004 at 20:57:37 Pacific
Reply:

Repost if you still have problems after you re-install windows and upgrade ATI display card driver. - Albert


0

Response Number 28
Name: cpc2000
Date: November 28, 2004 at 23:21:33 Pacific
Reply:

This was because the nVidia drivers mess with some of the windows installed files, making it impossible to get rid of the nVidia drivers. Format and reinstall of windows. Install ATI Radeon 9800 PRO directly and no more blue screen.


0

Sponsored Link
Ads by Google
Reply to Message Icon

IE Error - Page cannot be... suddenly distored missing...



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows XP Forum Home


Sponsored links

Ads by Google


Results for: Another random reboot problem

Random Rebooting www.computing.net/answers/windows-xp/random-rebooting/9521.html

Random Reboots www.computing.net/answers/windows-xp/random-reboots/83527.html

Random Rebooting www.computing.net/answers/windows-xp/random-rebooting/21818.html