Announcement

**Ian (PassMark)** · Sep-12-2007, 11:04 PM

If you are using BurnInTest PRo (rather than Standard) then I would suggest moving to BurnInTest Pro V5.3.1011 which better handles Access Violations (such as is cased by faulty device drivers).

I would update the graphics card device driver from the manufacturers website.

Does the problem occur if you only specify 2 3D test windows?

Regards,
Ian

**Jimmy** · Sep-20-2007, 12:11 PM

burn in 5.3.1011

Thank you very much,lan.
Now,I use Burn-in 5.3.1011 version to check the issue,open 3 3D windows,it can run without any error.but after 24 hours,the major process can stop,there are 5 windows include 3 3D windows can not be close.I don't know why?
As before,after run for 24 hours,all the dialog box can stop,but now,there are 5 windows can not be close,please help to check ang give your comment,thanks.

**Ian (PassMark)** · Sep-21-2007, 12:18 AM

Jimmy,

1) Did you check and update the graphics device driver?
2) Do you see the problem on a single system, or have you seen it on multiple systems. If multiple systems, is the graphics card the same?
3) Does the problem occur if you run a single 3D test only and no other tests?
4) Can you take a screenshot (Printscreen) showing all of the open windows when this problem occurs and send it to us at:
help [at] passmark [dot] com

Thanks.
Ian

**Jimmy** · Sep-24-2007, 03:37 AM

Thank you,Lan.
For I use intel On-board VGA,driver:6.14.10.4847
I have checked on two project(the same On-board VGA and driver),Also have the issue.
I have not checked if only run 3D test.
And the VBIOS version is 1417.
Sorry,I can not find the solution to give you the PIC.

**Ian (PassMark)** · Sep-24-2007, 04:48 AM

Without more information I would have to say that this is most likely a 3D graphics device driver related bug. As the problem only occurs after 24 hours of testing, I would have to suspect it is related to a resource leak in the device driver.

Which 5 windows remained open and what did each have displayed?

Also note that I checked the problems reported to Microsoft and I do not see this problem (i.e. access violation 0x4FEC01FB). Where possible, please send error reports to Microsoft (ie. the standard Windows Error Reports) and we will then get information from them to help our investigation.

Is a window displayed with the text:
"BurnInTest has encountered an error during testing\nand will close.
...[snipped]"?

Thanks.
Ian

**Jimmy** · Sep-24-2007, 11:19 AM

Thank you .Lan
Do you mean that is relate the On-board VGA driver?
The 5 windows I can not give you the PIC,but the 5 windows include 3 3D windows.
Lan,I want to know how to give you the Pic?I can not find the way to upload the PIC.Thanks

**pcsmo** · Sep-24-2007, 02:44 PM

My issue is like this but I receive a STOP error instead of an Access Violation. The lastest Intel onboard graphics driver (6.14.10.4864) and the previous one listed in a prior post give me STOP errors when running the burnin test yet nothing else causes one. I'm forced to go back to a driver release from months prior to have a stable burnin test. Drivers appear to be the bad guy here but it is odd it only happens in the burnin test. I'm using Pro 5.3.1005 and I just downloaded build 1011 so I'll try that and post my results.

Here is the debugging information on the STOP Error

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini092407-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Sep 21 17:35:38.500 2007 (GMT-5)
System Uptime: 0 days 2:05:44.053
Loading Kernel Symbols
.................................................. .................................................. ...........................................
Loading User Symbols
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000004, 806eaad1, a6d23708, 0}
Unable to load image \SystemRoot\system32\DRIVERS\igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: 806eaad1, The address that the exception occurred at
Arg3: a6d23708, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported
FAULTING_IP:
hal!WRITE_PORT_ULONG+9
806eaad1 c20800 ret 8
TRAP_FRAME: a6d23708 -- (.trap 0xffffffffa6d2370

Unable to read trap frame at a6d23708
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 806e8151 to 806eaad1
STACK_TEXT:
a6d23778 806e8151 00000cf8 80001090 806ef3a0 hal!WRITE_PORT_ULONG+0x9
a6d2378c 806e7f0d 806ef3a0 a6d237ac a6d238d8 hal!HalpPCIWriteUlongType1+0x23
a6d237c0 806e8335 a6d23800 00000002 a6d238d8 hal!HalpPCIConfig+0x4d
a6d237e0 806e914b a6d23804 00000002 a6d238d8 hal!HalpWritePCIConfig+0x2d
a6d23870 b9f68ae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33
a6d23894 b9f68b74 89e4ebe0 00000002 a6d238d8 pci!PciReadWriteConfigSpace+0x38
a6d238b4 b9f68fcc 89e13d28 a6d238d8 00000090 pci!PciWriteDeviceConfig+0x1e
a6d239dc b9f6bcbd 89e13d28 a6d23a64 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
a6d23a00 b9f6834d 89e13d28 00000000 a6d23a64 pci!PciWriteDeviceSpace+0x5d
a6d23a20 b8efd0d2 89e13d28 00000000 a6d23a64 pci!PciWriteAgpConfig+0x1d
a6d23a3c b8f1d2e1 89baa740 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
a6d23a70 b8f2512d 89baa740 000000ea 0fd5f000 igxpmp32+0xd2e1
a6d23ac0 b8efd21b 89baa740 000000ea 898e5000 igxpmp32+0x1512d
a6d23ae4 b8f09b06 a6d23b7c 00000000 897daca8 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
a6d23ba4 804ef095 89963040 88e554d8 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
a6d23bb4 bf859e44 00000000 00000000 00000000 nt!IopfCallDriver+0x31
a6d23be4 bf93c075 89963040 0023002c 00000000 win32k!GreDeviceIoControl+0x93
a6d23c0c bf95ffbb a6d23c68 001ea1e4 001ea368 win32k!DrvPrepareForEARecovery+0x26
a6d23c2c bf960fec e1afe9c0 00000020 00000098 win32k!HandleStuckThreadException+0x24
a6d23c68 bf000663 a6d23ce4 a6d23d64 026cf09c win32k!WatchdogDdDrawPrimitives2+0x76
a6d23d40 8054086c 01400008 01400009 00184260 dxg!DxD3dDrawPrimitives2+0x1b9
a6d23d40 7c90eb94 01400008 01400009 00184260 nt!KiFastCallEntry+0xfc
026cf0ac 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb
FOLLOWUP_IP:
pci!PciReadWriteConfigSpace+38
b9f68ae0 3b4518 cmp eax,dword ptr [ebp+18h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: pci!PciReadWriteConfigSpace+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pci
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d31
FAILURE_BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
Followup: MachineOwner

**Ian (PassMark)** · Sep-25-2007, 12:07 AM

PCSMO,

These problems don't look related (it is possible however). This Bugcheck is an unhandled exception in the Operating System, (most likely) in the PCI device driver pci.sys. It is a "A single step or trace operation has just been completed" exception. As the crash appears to occur on a low level write, it could be a hardware error (like a faulty RAM module) or a device driver bug problem.

1) Which version of BurnIntest were you using?
2) Does the problem occur if you only run the 3D test?
3) How long into the test does the problem occur?
4) have you seen the problem on a sngle PC, single PC type or multiple PC types?

Thanks.

Regards,
Ian

**Ian (PassMark)** · Sep-25-2007, 12:11 AM

Jimmy,

Do you mean that is relate the On-board VGA driver?
>>>Yes, that would be my first suspicion. As you are using onboard graphics, you might also try swapping your RAM to just rule faulty RAM hardware in or out. Does this make a difference?

The 5 windows I can not give you the PIC,but the 5 windows include 3 3D windows. Lan,I want to know how to give you the Pic?I can not find the way to upload the PIC.
>>> You can email it to help [at] passmark [dot] com

Can you answer the other questions I have asked in previous posts?

Regards,
Ian

Update: See also this post dealing with the same error. Possibility blaming the screen saver for provoking the issue on Intel motherboards with onboard graphics.

**pcsmo** · Nov-02-2007, 03:52 AM

Originally posted by Ian (PassMark) View Post

PCSMO,

These problems don't look related (it is possible however). This Bugcheck is an unhandled exception in the Operating System, (most likely) in the PCI device driver pci.sys. It is a "A single step or trace operation has just been completed" exception. As the crash appears to occur on a low level write, it could be a hardware error (like a faulty RAM module) or a device driver bug problem.

1) Which version of BurnIntest were you using?
2) Does the problem occur if you only run the 3D test?
3) How long into the test does the problem occur?
4) have you seen the problem on a sngle PC, single PC type or multiple PC types?

Thanks.

Regards,
Ian

Sorry about the lateness of my reply, I've been away for awhile.
1. I'm using Pro 5.3.1005
2. Yes
3. 15min to several hours
4. It seems to happen on laptops with intel integrated graphics that I've used.

**pcsmo** · Dec-06-2007, 03:11 PM

It isn't limited to laptop IGP's as desktop IGP have the same exact issue. Here is another dump file.

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: 806eaad1, The address that the exception occurred at
Arg3: a8460708, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported
FAULTING_IP:
hal!WRITE_PORT_ULONG+9
806eaad1 c20800 ret 8
TRAP_FRAME: a8460708 -- (.trap 0xffffffffa846070

ErrCode = 00000000
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806ef3a0 edi=a8460804
eip=806eaad1 esp=a846077c ebp=a846078c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
hal!WRITE_PORT_ULONG+0x9:
806eaad1 c20800 ret 8
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: bit.exe
LAST_CONTROL_TRANSFER: from 806e8151 to 806eaad1
STACK_TEXT:
a8460778 806e8151 00000cf8 80001090 806ef3a0 hal!WRITE_PORT_ULONG+0x9
a846078c 806e7f0d 806ef3a0 a84607ac a84608d8 hal!HalpPCIWriteUlongType1+0x23
a84607c0 806e8335 a8460800 00000002 a84608d8 hal!HalpPCIConfig+0x4d
a84607e0 806e914b a8460804 00000002 a84608d8 hal!HalpWritePCIConfig+0x2d
a8460870 b9f68ae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33
a8460894 b9f68b74 89c16620 00000002 a84608d8 pci!PciReadWriteConfigSpace+0x38
a84608b4 b9f68fcc 89c564c8 a84608d8 00000090 pci!PciWriteDeviceConfig+0x1e
a84609dc b9f6bcbd 89c564c8 a8460a64 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
a8460a00 b9f6834d 89c564c8 00000000 a8460a64 pci!PciWriteDeviceSpace+0x5d
a8460a20 b98130d2 89c564c8 00000000 a8460a64 pci!PciWriteAgpConfig+0x1d
a8460a3c b9833201 89b84358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
a8460a70 b9843183 89b84358 000000ea 0fd5f000 igxpmp32+0xd201
a8460ac0 b981321b 89b84358 000000ea 89923000 igxpmp32+0x1d183
a8460ae4 b981fb06 a8460b7c 00000000 89909468 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
a8460ba4 804ef095 89adc330 895ba538 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
a8460bb4 bf859e44 00000000 00000000 00000000 nt!IopfCallDriver+0x31
a8460be4 bf93c075 89adc330 0023002c 00000000 win32k!GreDeviceIoControl+0x93
a8460c0c bf95ffbb 00000000 00000000 a8460c68 win32k!DrvPrepareForEARecovery+0x26
a8460c2c bf960fec e100acf0 00000020 00000098 win32k!HandleStuckThreadException+0x24
a8460c68 bf000663 a8460ce4 a8460d64 0242fb84 win32k!WatchdogDdDrawPrimitives2+0x76
a8460d40 8054086c 01400006 01400007 001815a0 dxg!DxD3dDrawPrimitives2+0x1b9
a8460d40 7c90eb94 01400006 01400007 001815a0 nt!KiFastCallEntry+0xfc
0242fb94 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb
FOLLOWUP_IP:
pci!PciReadWriteConfigSpace+38
b9f68ae0 3b4518 cmp eax,dword ptr [ebp+18h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: pci!PciReadWriteConfigSpace+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pci
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d31
FAILURE_BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806ef3a0 edi=a8460804
eip=806eaad1 esp=a846077c ebp=a846078c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286

**pcsmo** · Dec-06-2007, 03:14 PM

hal!WRITE_PORT_ULONG+0x9:
806eaad1 c20800 ret 8
ChildEBP RetAddr Args to Child
a8460778 806e8151 00000cf8 80001090 806ef3a0 hal!WRITE_PORT_ULONG+0x9 (FPO: [2,0,0])
a846078c 806e7f0d 806ef3a0 a84607ac a84608d8 hal!HalpPCIWriteUlongType1+0x23 (FPO: [Non-Fpo])
a84607c0 806e8335 a8460800 00000002 a84608d8 hal!HalpPCIConfig+0x4d (FPO: [Non-Fpo])
a84607e0 806e914b a8460804 00000002 a84608d8 hal!HalpWritePCIConfig+0x2d (FPO: [Non-Fpo])
a8460870 b9f68ae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33 (FPO: [Non-Fpo])
a8460894 b9f68b74 89c16620 00000002 a84608d8 pci!PciReadWriteConfigSpace+0x38 (FPO: [Non-Fpo])
a84608b4 b9f68fcc 89c564c8 a84608d8 00000090 pci!PciWriteDeviceConfig+0x1e (FPO: [Non-Fpo])
a84609dc b9f6bcbd 89c564c8 a8460a64 00000090 pci!PciExternalWriteDeviceConfig+0x1ac (FPO: [Non-Fpo])
a8460a00 b9f6834d 89c564c8 00000000 a8460a64 pci!PciWriteDeviceSpace+0x5d (FPO: [Non-Fpo])
a8460a20 b98130d2 89c564c8 00000000 a8460a64 pci!PciWriteAgpConfig+0x1d (FPO: [Non-Fpo])
a8460a3c b9833201 89b84358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be wrong.
a8460a70 b9843183 89b84358 000000ea 0fd5f000 igxpmp32+0xd201
a8460ac0 b981321b 89b84358 000000ea 89923000 igxpmp32+0x1d183
a8460ae4 b981fb06 a8460b7c 00000000 89909468 VIDEOPRT!pVpGeneralBugcheckHandler+0x61 (FPO: [Non-Fpo])
a8460ba4 804ef095 89adc330 895ba538 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa (FPO: [Non-Fpo])
a8460bb4 bf859e44 00000000 00000000 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
a8460be4 bf93c075 89adc330 0023002c 00000000 win32k!GreDeviceIoControl+0x93 (FPO: [Non-Fpo])
a8460c0c bf95ffbb 00000000 00000000 a8460c68 win32k!DrvPrepareForEARecovery+0x26 (FPO: [Non-Fpo])
a8460c2c bf960fec e100acf0 00000020 00000098 win32k!HandleStuckThreadException+0x24 (FPO: [Non-Fpo])
a8460c68 bf000663 a8460ce4 a8460d64 0242fb84 win32k!WatchdogDdDrawPrimitives2+0x76 (FPO: [Non-Fpo])
start end module name
804d7000 806e2000 nt ntkrpamp.exe Wed Feb 28 02:38:53 2007 (45E53F9D)
806e2000 80702d00 hal halmacpi.dll Wed Aug 04 00:59:09 2004 (41107B2D)
a83e0000 a8420280 HTTP HTTP.sys Thu Mar 16 19:33:09 2006 (441A03C5)
a8791000 a87a5400 wdmaud wdmaud.sys Wed Jun 14 04:00:44 2006 (448FD03C)
a87a6000 a87c8080 RDPWD RDPWD.SYS Thu Jun 09 18:52:39 2005 (42A8D647)
a8871000 a887fd80 sysaudio sysaudio.sys Wed Aug 04 01:15:54 2004 (41107F1A)
a89f9000 a8a4a480 srv srv.sys Mon Aug 14 05:34:39 2006 (44E051BF)
a8a9b000 a8ac7400 mrxdav mrxdav.sys Wed Aug 04 01:00:49 2004 (41107B91)
a8e38000 a8e4f480 dump_atapi dump_atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
a8e50000 a8ebea00 mrxsmb mrxsmb.sys Fri May 05 04:41:42 2006 (445B1DD6)
a8ebf000 a8ee9a00 rdbss rdbss.sys Fri May 05 04:47:55 2006 (445B1F4B)
a8eea000 a8f0bd00 afd afd.sys Wed Aug 04 01:14:13 2004 (41107EB5)
a8f0c000 a8f2cf00 ipnat ipnat.sys Wed Sep 29 17:28:36 2004 (415B3714)
a8f2d000 a8f54c00 netbt netbt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
a8f6d000 a8f70280 ndisuio ndisuio.sys Wed Aug 04 01:03:10 2004 (41107C1E)
a8f7d000 a8fd4d80 tcpip tcpip.sys Thu Apr 20 06:51:47 2006 (444775D3)
a8fd5000 a8fe7400 ipsec ipsec.sys Wed Aug 04 01:14:27 2004 (41107EC3)
a90d0000 a90f1700 portcls portcls.sys Tue Mar 16 13:58:17 2004 (40574E49)
a90f2000 a94d7000 RtkHDAud RtkHDAud.sys Fri Sep 23 05:56:25 2005 (4333DF59)
b9597000 b95efe80 update update.sys Mon Apr 23 05:32:54 2007 (462C8B56)
b95fc000 b95fe900 Dxapi Dxapi.sys Fri Aug 17 15:53:19 2001 (3B7D843F)
b9618000 b9648100 rdpdr rdpdr.sys Wed Aug 04 01:01:10 2004 (41107BA6)
b9649000 b9659e00 psched psched.sys Wed Aug 04 01:04:16 2004 (41107C60)
b965a000 b9670680 ndiswan ndiswan.sys Wed Aug 04 01:14:30 2004 (41107EC6)
b9671000 b9693680 ks ks.sys Wed Aug 04 01:15:20 2004 (41107EF

b9694000 b96a7900 parport parport.sys Wed Aug 04 00:59:04 2004 (41107B2.8
b96a8000 b96cae80 USBPORT USBPORT.SYS Wed Aug 04 01:08:34 2004 (41107D62)
b97c2000 b97ed000 b57xp32 b57xp32.sys Fri Feb 16 17:46:40 2007 (45D64260)
b97ed000 b9812000 HDAudBus HDAudBus.sys Fri Jan 07 19:07:15 2005 (41DF3243)
b9812000 b9825780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 01:07:04 2004 (41107D0.8
b9826000 b9da4460 igxpmp32 igxpmp32.sys Mon Apr 16 16:16:25 2007 (4623E7A9)
b9dc1000 b9dc3280 rasacd rasacd.sys Fri Aug 17 15:55:39 2001 (3B7D84CB)
b9ded000 b9e07580 Mup Mup.sys Wed Aug 04 01:15:20 2004 (41107EF

b9e08000 b9e34a80 NDIS NDIS.sys Wed Aug 04 01:14:27 2004 (41107EC3)
b9e35000 b9ec1400 Ntfs Ntfs.sys Fri Feb 09 05:10:31 2007 (45CC56A7)
b9ec2000 b9ed8780 KSecDD KSecDD.sys Wed Aug 04 00:59:45 2004 (41107B51)
b9ed9000 b9eeaf00 sr sr.sys Wed Aug 04 01:06:22 2004 (41107CDE)
b9eeb000 b9f0a780 fltMgr fltMgr.sys Mon Aug 21 04:14:57 2006 (44E97991)
b9f0b000 b9f22480 atapi atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
b9f23000 b9f48700 dmio dmio.sys Wed Aug 04 01:07:13 2004 (41107D11)
b9f49000 b9f67880 ftdisk ftdisk.sys Fri Aug 17 15:52:41 2001 (3B7D8419)
b9f68000 b9f78a80 pci pci.sys Wed Aug 04 01:07:45 2004 (41107D31)
b9f79000 b9fa6d80 ACPI ACPI.sys Wed Aug 04 01:07:35 2004 (41107D27)
ba0a8000 ba0b0c00 isapnp isapnp.sys Fri Aug 17 15:58:01 2001 (3B7D8559)
ba0b8000 ba0c2500 MountMgr MountMgr.sys Wed Aug 04 00:58:29 2004 (41107B05)
ba0c8000 ba0d4c80 VolSnap VolSnap.sys Wed Aug 04 01:00:14 2004 (41107B6E)
ba0d8000 ba0e0e00 disk disk.sys Wed Aug 04 00:59:53 2004 (41107B59)
ba0e8000 ba0f4200 CLASSPNP CLASSPNP.SYS Wed Aug 04 01:14:26 2004 (41107EC2)
ba188000 ba190d00 intelppm intelppm.sys Wed Aug 04 00:59:19 2004 (41107B37)
ba198000 ba1a7d80 serial serial.sys Wed Aug 04 01:15:51 2004 (41107F17)
ba1a8000 ba1b4e00 i8042prt i8042prt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
ba1b8000 ba1c2380 imapi imapi.sys Wed Aug 04 01:00:12 2004 (41107B6C)
ba1c8000 ba1d4180 cdrom cdrom.sys Wed Aug 04 00:59:52 2004 (41107B5.8
ba1d8000 ba1e6080 redbook redbook.sys Wed Aug 04 00:59:34 2004 (41107B46)
ba1e8000 ba1f4880 rasl2tp rasl2tp.sys Wed Aug 04 01:14:21 2004 (41107EBD)
ba1f8000 ba202200 raspppoe raspppoe.sys Wed Aug 04 01:05:06 2004 (41107C92)
ba208000 ba213d00 raspptp raspptp.sys Wed Aug 04 01:14:26 2004 (41107EC2)
ba218000 ba220900 msgpc msgpc.sys Wed Aug 04 01:04:11 2004 (41107C5B)
ba228000 ba231f00 termdd termdd.sys Wed Aug 04 00:58:52 2004 (41107B1C)
ba238000 ba241480 NDProxy NDProxy.SYS Fri Aug 17 15:55:30 2001 (3B7D84C2)
ba258000 ba266b80 drmk drmk.sys Wed Aug 04 01:07:54 2004 (41107D3A)
ba278000 ba286100 usbhub usbhub.sys Wed Aug 04 01:08:40 2004 (41107D6.8
ba298000 ba2a0700 netbios netbios.sys Wed Aug 04 01:03:19 2004 (41107C27)
ba2a8000 ba2b0880 Fips Fips.SYS Fri Aug 17 20:31:49 2001 (3B7DC585)
ba2c8000 ba2d7900 Cdfs Cdfs.SYS Wed Aug 04 01:14:09 2004 (41107EB1)
ba308000 ba310700 wanarp wanarp.sys Wed Aug 04 01:04:57 2004 (41107C89)
ba328000 ba32e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 00:59:40 2004 (41107B4C)
ba330000 ba334900 PartMgr PartMgr.sys Fri Aug 17 20:32:23 2001 (3B7DC5A7)
ba378000 ba37d000 usbuhci usbuhci.sys Wed Aug 04 01:08:34 2004 (41107D62)
ba380000 ba386800 usbehci usbehci.sys Wed Aug 04 01:08:34 2004 (41107D62)
ba388000 ba389000 fdc fdc.sys unavailable (00000000)
ba390000 ba395a00 mouclass mouclass.sys Wed Aug 04 00:58:32 2004 (41107B0.8
ba398000 ba39e000 kbdclass kbdclass.sys Wed Aug 04 00:58:32 2004 (41107B0.8
ba3a0000 ba3a4880 TDI TDI.SYS Wed Aug 04 01:07:47 2004 (41107D33)
ba3a8000 ba3ac580 ptilink ptilink.sys Fri Aug 17 15:49:53 2001 (3B7D8371)
ba3b0000 ba3b4080 raspti raspti.sys Fri Aug 17 15:55:32 2001 (3B7D84C4)
ba3c8000 ba3cd500 TDTCP TDTCP.SYS Wed Aug 04 00:58:52 2004 (41107B1C)
ba3d0000 ba3d5000 flpydisk flpydisk.sys Wed Aug 04 00:59:24 2004 (41107B3C)
ba3e0000 ba3e6180 HIDPARSE HIDPARSE.SYS Wed Aug 04 01:08:15 2004 (41107D4F)
ba3e8000 ba3ed200 vga vga.sys Wed Aug 04 01:07:06 2004 (41107D0A)
ba3f0000 ba3f4a80 Msfs Msfs.SYS Wed Aug 04 01:00:37 2004 (41107B85)
ba3f8000 ba3ff880 Npfs Npfs.SYS Wed Aug 04 01:00:38 2004 (41107B86)
ba408000 ba40c500 watchdog watchdog.sys Wed Aug 04 01:07:32 2004 (41107D24)
ba4b8000 ba4bb000 BOOTVID BOOTVID.dll Fri Aug 17 15:49:09 2001 (3B7D8345)
ba54c000 ba54fc80 serenum serenum.sys Wed Aug 04 00:59:06 2004 (41107B2A)
ba554000 ba556580 ndistapi ndistapi.sys Fri Aug 17 15:55:29 2001 (3B7D84C1)
ba574000 ba577c80 mssmbios mssmbios.sys Wed Aug 04 01:07:47 2004 (41107D33)
ba5a8000 ba5a9b80 kdcom kdcom.dll Fri Aug 17 15:49:10 2001 (3B7D8346)
ba5aa000 ba5ab100 WMILIB WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
ba5ac000 ba5ad700 dmload dmload.sys Fri Aug 17 15:58:15 2001 (3B7D8567)
ba5c0000 ba5c1100 swenum swenum.sys Wed Aug 04 00:58:41 2004 (41107B11)
ba5c6000 ba5c7280 USBD USBD.SYS Fri Aug 17 16:02:58 2001 (3B7D8682)
ba5c8000 ba5c9f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 15:49:37 2001 (3B7D8361)
ba5ca000 ba5cb080 Beep Beep.SYS Fri Aug 17 15:47:33 2001 (3B7D82E5)
ba5cc000 ba5cd080 mnmdd mnmdd.SYS Fri Aug 17 15:57:28 2001 (3B7D853.8
ba5ce000 ba5cf080 RDPCDD RDPCDD.sys Fri Aug 17 15:46:56 2001 (3B7D82C0)
ba5d0000 ba5d1100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
ba5f4000 ba5f5a80 ParVdm ParVdm.SYS Fri Aug 17 15:49:49 2001 (3B7D836D)
ba670000 ba670d00 pciide pciide.sys Fri Aug 17 15:51:49 2001 (3B7D83E5)
ba758000 ba758c00 audstub audstub.sys Fri Aug 17 15:59:40 2001 (3B7D85BC)
ba7bc000 ba7bcb80 Null Null.SYS Fri Aug 17 15:47:39 2001 (3B7D82EB)
ba7e8000 ba7e8d00 dxgthk dxgthk.sys Fri Aug 17 15:53:12 2001 (3B7D843.8
bf000000 bf011580 dxg dxg.sys Wed Aug 04 01:00:51 2004 (41107B93)
bf012000 bf024000 igxprd32 igxprd32.dll Mon Apr 16 16:16:07 2007 (4623E797)
bf024000 bf04e000 igxpgd32 igxpgd32.dll Mon Apr 16 16:16:01 2007 (4623E791)
bf04e000 bf1f16a0 igxpdv32 igxpdv32.DLL Mon Apr 16 16:15:46 2007 (4623E782)
bf1f2000 bf48d000 igxpdx32 igxpdx32.DLL Mon Apr 16 16:16:52 2007 (4623E7C4)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 07:47:34 2007 (45F013F6)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 02:56:56 2004 (411096C.8

**Ian (PassMark)** · Dec-06-2007, 10:34 PM

The crash address is in the function WRITE_PORT_ULONG in the Hardware abstraction layer in Windows on trying to write a value to the mapped memory range in I/O space. It would appear to have occured as a result of a device driver (DRIVER_FAULT) issuing an unsupported operation. All 3 of your Bugchecks posted appear to be the same problem.

1) Does this happen on all systems of this type? If not, then it could be faulty video RAM.
2) Does it happen everytime you run just the 3D test?
3) Please just confirm you are using the latest graphics device driver and latest DirectX 9.0c?

Thanks.
Ian

**pcsmo** · Dec-12-2007, 03:17 PM

1) Does this happen on all systems of this type? If not, then it could be faulty video RAM.
It happens on all systems with Intel onboard graphics

2) Does it happen everytime you run just the 3D test?
I run cpu, disk, network, and graphics tests at the same time. If I take out the graphics tests, the system never crashes. I haven't tried just the 3d test but I doubt the results with change.

3) Please just confirm you are using the latest graphics device driver and latest DirectX 9.0c?
I'm using the latest driver and directx 9.0c and the addon the software(BIT) runs when starts for the first time.

Announcement

BurnTn v5.3 test error WinXP - Access violation 0x4FEC01FB with onboard video

BurnTn v5.3 test error WinXP - Access violation 0x4FEC01FB with onboard video

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment