3D mark 2006 crashing

[THC_SsSsSnake]

The 1st time i ran 3dmark 2006 it was fine,then a week or so later i tried again and after the 3rd graphics test with the serpent imediately after instead of going to the page that says checking configuration the sceen goes dark and the monitor power light flashes,below is the microsoft answer
Error message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
View products that this article applies to.
Article ID : 293078
Last Review : April 6, 2006
Revision : 3.11
This article was previously published under Q293078
SYMPTOMS
You may receive one of the following Stop error messages:
STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
STOP: 0x100000EA THREAD_STUCK_IN_DEVICE_DRIVER_M
CAUSE
This issue may occur if the display driver is caught in an infinite loop while it waits for the video hardware to become idle. This issue typically indicates a problem with the video hardware or that the display driver cannot program the hardware correctly.
RESOLUTION
To resolve this issue, obtain and install the most current driver for your video adapter, or replace your video card.

I see from a search on google that some other 7900gtx(which I have) have had a similar problem but it seems that its the overclocked ones which this is not.

I formatted and reinstalled windows and it did exactly the same thing at the same point,tried about 6 times now.

Anybody else had a similar problem?

thanks

 

[THC_SsSsSnake]

just ran it again with 3dmark2006 settings in the display setting and when it got to the load cpu teat 1 screen it eventually came up with the message

1direct3d vertex buffer 9 lock failed d3derr_(not available)
_________________
AMD4400x2/2 gig Corsair pc3200/Point of View7900gtx/AN-8.premium sli mobo/Hitachi 80g sata2/seasonic 600wpsu/
Samsung 32" HD/LCD

 

[cokecan]

may be a display driver issue??? possibly try using some older or newer drivers??

 

[kbc]

may be a display driver issue??? possibly try using some older or newer drivers??

Yes, if I were you, do the above and if that doesn't resolve - try benching it on another system. Otherwise it might literally be a hardware fault.

 

[THC_SsSsSnake]

thanks guys will try another driver,when doing a search D3DERR_NOTAVAILABLE seems quite common

 

[THC_SsSsSnake]

tried 2 diff drivers and now i got a kmode exception not handled error

 

[MeatLoaf]

Uninstall coolbits, if you have it installed

 

[THC_SsSsSnake]

thanks meatloaf,i didnt have it installed no o/c

 

[MeatLoaf]

only reason i suggested it is i used to have it inatalled on the sli setup, and it always crashed at the 1st cpu test. Reinstalling the driver/removing coolbits always solved it.

 

[THC_SsSsSnake]

thanks mate,I RMA'd it so see how it goes