BSOD On Shutdown With XP

Status
Not open for further replies.
I get a BSOD on shutdown with Windows XP

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/1/2009
Time: 7:21:17 PM
User: N/A
Computer: ARCLAPTOP
Description:
Error code 00000019, parameter1 00000020, parameter2 89d2b040, parameter3 89d2b2d0, parameter4 18522fc0.


Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 39 64 32 62 30 34 30 89d2b040
0040: 2c 20 38 39 64 32 62 32 , 89d2b2
0048: 64 30 2c 20 31 38 35 32 d0, 1852
0050: 32 66 63 30 2fc0

I can't attach the minidump files cause I don't have 5 posts.
All help is greatly appreciated.

Thanks!
 
The things you attached are the minidump files which is fine.

Your errors are as follows:

0x8E (x2) and these are almost always caused by hardware and are especially a strong indicator of corrupted memory.

Another is 0xA and these also are strong indicators of hardware issues though they also point to drivers attempting to access IRQ Levels they shouldn't.

Your remaining error is 0x19: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers.

The thing is all cite Windows drivers and they are too general to be of much help.

However, in the mix of the 0x8E errors the following drivers were shown not able to be loaded: igxpmp32.sys, igxpgd32.dll, and igxprd.dll and they are Intel graphics drivers/miniport drivers.

Do you have onboard graphics? If so, update your onboard graphics drivers.
 
Hey Thanks for the quick reply. I will check the disk for errors and I updated the driver on the intel chip set. Hopefully, that will take care of it.

Thanks Again!
 
Status
Not open for further replies.
Back