Tech Support Forum banner
Status
Not open for further replies.
1 - 4 of 4 Posts

· Registered
Joined
·
3 Posts
Discussion Starter · #1 ·
I have problem with my compaq presario v3500 notebook pc, when I try to play a game specifically Frozen Throne I got bsod saying

stop 0x0000008E (0x80000004, 0x80729AF5, 0xA0CE965C, 0x00000000)

OS: Windows Xp Professional
Memory: 1046mb ram
DirecX Version: DirectX 9.0c


Please Help Me T T
 

Attachments

· TSF Team Emeritus
Joined
·
6,274 Posts
Re: Compaq Presario help!! T T

Hi,

Code:
[font=lucida console]
BugCheck 1000008E, {80000004, 80729af5, f5a3965c, 0}
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000008E, {80000004, 80729af5, a0ce965c, 0}
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000008E, {80000004, 80729af5, 9f1fb65c, 0}
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000008E, {80000004, 80729af5, 9d2e965c, 0}
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 100000EA, {84f8a020, 854a8bb8, f7a46cbc, 1}
Probably caused by : igxpdv32.DLL ( igxpdv32+abf )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000008E, {80000004, 80729af5, f691465c, 0}
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
[/font]
5 out of 6 blaming pci.sys, an OS driver. However when I did some more investigating . . .
Code:
[font=lucida console]
[B][U]STACK_TEXT: [/U][/B] 
f5a396cc 8072714f 00000cf8 80001090 8072e420 hal!WRITE_PORT_ULONG+0x9
f5a396e0 80726f0b 8072e420 f5a39700 f5a3982c hal!HalpPCIWriteUlongType1+0x23
f5a39714 80727333 f5a39700 00000002 f5a3982c hal!HalpPCIConfig+0x4d
f5a39734 80728149 f5a39758 00000002 f5a3982c hal!HalpWritePCIConfig+0x2d
f5a397c4 f75abae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33
f5a397e8 f75abb74 863e79a0 00000002 f5a3982c pci!PciReadWriteConfigSpace+0x38
f5a39808 f75abfcc 86349268 f5a3982c 00000090 pci!PciWriteDeviceConfig+0x1e
f5a39930 f75aecbd 86349268 f5a399b8 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
f5a39954 f75ab34d 86349268 00000000 f5a399b8 pci!PciWriteDeviceSpace+0x5d
f5a39974 f62e3212 86349268 00000000 f5a399b8 pci!PciWriteAgpConfig+0x1d
f5a39990 f6303a11 8589b358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
f5a399c4 f631738d 8589b358 000000ea 00000000 [B][COLOR=Red]igxpmp32[/COLOR][/B]+0xda11
f5a39a14 f62e335b 8589b358 000000ea 856bb000 [B][COLOR=Red]igxpmp32[/COLOR][/B]+0x2138d
f5a39a38 f62f0114 f5a39ad0 00000000 85720218 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
f5a39af8 804e13eb 854d8790 84e5ee40 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
f5a39b38 bf93da33 854d8790 0023002c 00000000 nt+0xa3eb
f5a39b60 bf961dc0 00000000 00000000 e3936e38 win32k!DrvPrepareForEARecovery+0x26
f5a39b80 bf8bf9cc e1a55008 00000000 e2a6d370 win32k!HandleStuckThreadException+0x24
f5a39bb4 bf8053c5 e1292940 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
f5a39bc8 bf864ecf e1292940 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
f5a39c0c bf864c83 e2410008 030106c4 00000000 win32k!bSpUpdateSprite+0x19f
f5a39c60 bf8657fe e2410008 000200e2 00000000 win32k!GreUpdateSprite+0xe7
f5a39cac bf86607d bbea0170 030106c4 00000000 win32k!_UpdateLayeredWindow+0x60
f5a39d38 804dd99f 000200e2 030106c4 00000000 win32k!NtUserUpdateLayeredWindow+0x114
f5a39d64 7c90e514 badb0d00 0012f9d8 00000000 nt+0x699f
f5a39d68 badb0d00 0012f9d8 00000000 00000000 0x7c90e514
f5a39d6c 0012f9d8 00000000 00000000 00000000 0xbadb0d00
f5a39d70 00000000 00000000 00000000 00000000 0x12f9d8
[/font]
. . . I found that your Graphics Driver (surprise, surprise.. ) were actually the cause.

Code:
[font=lucida console][B]igxpmp32.sys[/B] Sat Jun 28 03:46:47 [COLOR=Red]2008[/COLOR][/font]
Hopefully there is an update for your chipset.

Run the Driver Update Utility from Intel here: http://downloadcenter.intel.com/Default.aspx

If that fails to fix it then you are looking at a possible hardware fault.

Regards,
Reventon
 
1 - 4 of 4 Posts
Status
Not open for further replies.
Top