943,946 Members | Top Members by Rank

Ad:
You are currently viewing page 1 of this multi-page discussion thread
Jul 14th, 2005
0

windows xp pro stop error, happens after only a few minutes of loading up

Expand Post »
hello there...

My brother has asked me to ask you this question on his behalf as he isn't subscribed to daniweb

ok down to the boiling point... my brother is running xp professional on a new pc (i built for him) over the last two or three days my brother has been experiencing BSODS and computer freezing shortly beforehand. i have looked at his pC myself and it looks to me as if it might be an error within windows itself. i am not certain on that though. here is the technical info that i managed to obtain from a BSOD that came up twice in the space of about half hour.

STOP 0x0000008E (0xC0000005, 0xBF8016FA, 0xB8697A88, 0x00000000)
Win32k.sys - Address BF8016FA base at BF800000, Datestamp 422511a2

What does this mean and will i have to refort his hard disk for him again??
Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 14th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

Hi Janine,

You can find info on the possible causes (and fixes) for that particular Stop Code error in the links returned by the following Google search:

http://www.google.com/search?hl=en&l...05&btnG=Search

Give some of those a try and let us know the results.
DMR
Team Colleague
Reputation Points: 221
Solved Threads: 369
Wombat At Large
DMR is offline Offline
6,439 posts
since Dec 2003
Jul 15th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

Quote originally posted by DMR ...
Hi Janine,

You can find info on the possible causes (and fixes) for that particular Stop Code error in the links returned by the following Google search:

http://www.google.com/search?hl=en&l...05&btnG=Search

Give some of those a try and let us know the results.
hi DMR.

thanks for the help on this particular stop error i think i might have located one problem from this. however i switched the particular pc on last night to see if anything different came up and unfortunately it brought up something about USB.sys (i cannot recall the exact error). Resulting from this i booted the particular machine into safe mode and accessed device manager. Looking into the device properties for the fast ethernet adaptor and the graphics card adaptor i looked and noted that the IRQ was the same and was the same for the usb as per other things. if it gives me a chance i might be able to save a print screen image to put up here.:-| any more ideas meanwhile.
Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 15th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up





Bus No
Device No

Func No

Vendor/Device

Class

Device Class

IRQ

0

15

0

1106

3149 0104

Raid Controller

11

0

15

1

1106

0571 0101

IDE Controller

14

0

16

0

1106

3038 0C03

USB 1.0/1.1 VHCI Controller

10

0

16

1

1106

3038 0C03

USB 1.0/1.1 VHCI Controller

10

0

16

2

1106

3038 0C03

USB 1.0/1.1 VHCI Controller

11

0

16

3

1106

3038 0C03

USB 1.0/1.1 VHCI Controller

11

0

16

4

1106

3104 0C03

USB 2.0 ECHI Controller

5

0

17

5

1106

3059 0401

Multimedia Device

5

0

18

0

1106

3065 0200

Network Controller

10

1

0

0

1002

5960 8300

Display Controller

10











ACPI Controller
9

Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 15th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

Quote originally posted by JANINE ...





Bus No




Device No







Func No







Vendor/Device







Class







Device Class







IRQ







0







15







0







1106







3149 0104







Raid Controller







11







0







15







1







1106







0571 0101







IDE Controller







14







0







16







0







1106







3038 0C03







USB 1.0/1.1 VHCI Controller







10







0







16







1







1106







3038 0C03







USB 1.0/1.1 VHCI Controller







10







0







16







2







1106







3038 0C03







USB 1.0/1.1 VHCI Controller







11







0







16







3







1106







3038 0C03







USB 1.0/1.1 VHCI Controller







11







0







16







4







1106







3104 0C03







USB 2.0 ECHI Controller







5







0







17







5







1106







3059 0401







Multimedia Device







5







0







18







0







1106







3065 0200







Network Controller







10







1







0







0







1002







5960 8300







Display Controller







10

















ACPI Controller




9






this post didnt come out as planned
please view nxt post
Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 15th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

next post

Bus No Device No Vendor/device class Device class
0 15 1106 3149 0104 raid controller
0 15 0571 0101 ide controller
0 16 and 3038 0c03 usb 1.0/1.1 vhci controller
0 16 same ''
0 16 until and same ''
0 16 end til end ''
0 16 usb2 echi controller
0 17 3059 0401 multimedia device
0 18 3065 0200 network controller
1 0 1002 5960 8300 display controller
acpi controller

IRQs as follows in order of listed device
11
14
10
10
11
11
5
5
10
10
9

how do i reassign IRQs as i think this is what might be the cause. i got this from pressing pause/break at the right time on the start up.

mail me if this doesnt make sense and i'll mail u the document
Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 15th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

1. If you can give us the exact "usb.sys" error that might be helpful. You might find more specific info for that, and perhaps the other problems, by doing the following:

Open the Event Viewer utility in your Administrative Tools control panel.

In the Event Viewer, look through the System and Application logs for entries flagged as "Warning" or "Error"; double-clicking on any of those entries will open a "details" window with more information about the error/warning. If you find any entries that seem to relate to the hangs/crashes that you're having, post the full and exact contents given in the detail windows.


2. The sharing of IRQs isn't usually a problem anymore, although it definitely was back in the days before PCI, "Plug-N-Play", and ACPI technologies were invented.

Since you haven't indicated that any recent hardware changes have been made to the system, the PCI/IRQ resource allocations of your installed hardware shouldn't have changed, but if you want to eliminate that possibility:

A) You can sometimes force a given device to use a specific IRQ or memory address range via the Resources tab in the device's Properties in Device Manager, but for the most part this rarely works. The issue is that modern operating systems and BIOSes do PCI resource allocation automatically, as opposed to the old (and pretty much manual) way that allocation was done with ISA devices.

B) There's one procedure which can often force a reallocation of resources though, and that is to physically change the slot ordering of the cards plugged into you PCI bus. When you start your computer, both the BIOS and Windows will enumerate (initialize) PCI devices based (to some extent) on the actual PCI slots in which the devices are installed; in "shuflfing" that order, you may be able to force the system to re-evaluate and reassign resources such as IRQs.

A couple of things to keep in mind regarding the placement/installation of devices (and Yoiks... just when did I decide that this should turn into a dissertation on PC architecture?!):

Some resources, including IRQs, are "reserved" by the system for use by core devices (keyboard, mouse, IDE drives/controllers, etc.). This is normal, and the system won't normally share those resources with another device if there's a possibility of conflict.

Additionally, your AGP graphics card (whether built into the motherboard or an actual AGP add-in card) usually shares resources with one of the PCI slots. The shared PCI slot is often, although not always, the slot closest to the AGP slot. It is a good idea not to install resource-intensive devices such as network cards or RAID controller cards in that shared PCI slot.
DMR
Team Colleague
Reputation Points: 221
Solved Threads: 369
Wombat At Large
DMR is offline Offline
6,439 posts
since Dec 2003
Jul 16th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

Quote originally posted by DMR ...
1. If you can give us the exact "usb.sys" error that might be helpful. You might find more specific info for that, and perhaps the other problems, by doing the following:

Open the Event Viewer utility in your Administrative Tools control panel.

In the Event Viewer, look through the System and Application logs for entries flagged as "Warning" or "Error"; double-clicking on any of those entries will open a "details" window with more information about the error/warning. If you find any entries that seem to relate to the hangs/crashes that you're having, post the full and exact contents given in the detail windows.


2. The sharing of IRQs isn't usually a problem anymore, although it definitely was back in the days before PCI, "Plug-N-Play", and ACPI technologies were invented.

Since you haven't indicated that any recent hardware changes have been made to the system, the PCI/IRQ resource allocations of your installed hardware shouldn't have changed, but if you want to eliminate that possibility:

A) You can sometimes force a given device to use a specific IRQ or memory address range via the Resources tab in the device's Properties in Device Manager, but for the most part this rarely works. The issue is that modern operating systems and BIOSes do PCI resource allocation automatically, as opposed to the old (and pretty much manual) way that allocation was done with ISA devices.

B) There's one procedure which can often force a reallocation of resources though, and that is to physically change the slot ordering of the cards plugged into you PCI bus. When you start your computer, both the BIOS and Windows will enumerate (initialize) PCI devices based (to some extent) on the actual PCI slots in which the devices are installed; in "shuflfing" that order, you may be able to force the system to re-evaluate and reassign resources such as IRQs.

A couple of things to keep in mind regarding the placement/installation of devices (and Yoiks... just when did I decide that this should turn into a dissertation on PC architecture?!):

Some resources, including IRQs, are "reserved" by the system for use by core devices (keyboard, mouse, IDE drives/controllers, etc.). This is normal, and the system won't normally share those resources with another device if there's a possibility of conflict.

Additionally, your AGP graphics card (whether built into the motherboard or an actual AGP add-in card) usually shares resources with one of the PCI slots. The shared PCI slot is often, although not always, the slot closest to the AGP slot. It is a good idea not to install resource-intensive devices such as network cards or RAID controller cards in that shared PCI slot.
i havent been made aware of any hardware changes that may have taken place recently but i do know that the radeon catalyst drivers have recently been updated. could that cause problems. regarding the AGP and PCI cards there is not one directly below the AGP card but there is one in the 2nd PCI slot.

regarding errors in the system and application logs... where do you want me to start.

here are some that come up frequently
event agent - tracelevel parameter not located in registry. default trace level used is 32
loadperf (whatever that means)

here are the system errors that i located in event viewer
error code 1000008e, parameter1 c0000005,parameter2 804ebfd9, parameter3 eddb2b2c parameter4 00000000
(error code 10000008e) parameter 1 c0000005, param2 804ecad5, param3 f58e7694, parameter4 00000000
(error code 10000008e) parameter 1 c0000005, param2 804ecad5, param3 f58e7694, parameter4 00000000
(error code 10000008e) parameter 1 c0000005, param2 804ecad5, param3 f58e7694, parameter4 00000000
there are hundreds of variations of the same error code coming up here (i have 2 pages worth printed off. please let me know if you want all the errors posted up.

it looks to me like the registry might have gotten corrupted for a start and secondly the paramenters have all been messed up. this looks like a job for a microsoft pro. whats your opinion here??:!:

Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005
Jul 17th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

The update to the video drivers would definitely be a prime suspect. Go into video card's Properties windows in Device Manager, click on the Driver tab, and try the "Roll back dirver" option.

If that doesn't work, you may be able to use System Restore to roll the entire system back to a date just prior to when you started getting the STOP errors.
DMR
Team Colleague
Reputation Points: 221
Solved Threads: 369
Wombat At Large
DMR is offline Offline
6,439 posts
since Dec 2003
Jul 18th, 2005
0

Re: windows xp pro stop error, happens after only a few minutes of loading up

Quote originally posted by DMR ...
The update to the video drivers would definitely be a prime suspect. Go into video card's Properties windows in Device Manager, click on the Driver tab, and try the "Roll back dirver" option.

If that doesn't work, you may be able to use System Restore to roll the entire system back to a date just prior to when you started getting the STOP errors.
i have tried to roll back the driver and rolling the system back to a previous state (just after xp was installed on it). No joy as the errors still keep coming.
i have even tried a reformat only to have a STOP error occur when attempting the reformat. i dont think that this is software related more like hardware now. any suggestions.
Reputation Points: 51
Solved Threads: 21
Practically a Posting Shark
JANINE is offline Offline
869 posts
since Mar 2005

This thread is solved

Either the thread starter or a moderator has marked this thread as solved. You can most likely trust the responses and answers given. There is most likely no reason for any further responses to be posted here. If you have a related question, please start a new thread in this forum instead.

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Message:
Previous Thread in Troubleshooting Dead Machines Forum Timeline: Compaq R3000 DEAD, NO NOTHING...
Next Thread in Troubleshooting Dead Machines Forum Timeline: no screen signal on booting





About Us | Contact Us | Advertise | Acceptable Use Policy
Forum Index | Build Custom RSS Feed


Follow us on Twitter


© 2011 DaniWeb® LLC