• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

4870 X2 Vista64 Error need help please!

Z

Zepharus

Gawd
Joined
Sep 6, 2008
Messages
644
First the history. I have been using a MSI 4870 X2 OC, which I purchased from Newegg 9/24 without any issues at all. I have been using the 8.11 drivers since they came out with NO issues. I have NOT upgraded to 8.12 yet.

Now here is the issue. For the last 3 days I have been getting Random reboots where the screen freezes for a split second and then goes black with some wacky artifacting at the top 1/3 of the display and then the system reboots. when it comes back up Vista 64 is displaying a video hardware error and giving me this...


Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Files that help describe the problem
WD-20081221-2347.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: FFFFFA8003CEF010
BCP2: FFFFFA6002212378
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1




No remember I have been perfectly find with no issues from 9/24 to now. It is seemingly random, but always seems to accompany the fan ramping up to 100% on the card. I use ati tray tools and have used riva tuner to control the fans. I have tried "clean" using just the cat drivers also and it still does it.

Do I mee to RMA this card to MSI? and if so anyone have experience with this? Merry friggin Xmas to me ! Grrrrrr
 
New info also... I downloaded Whocrashed it and it is telling me this....


Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled for your computer.


On Mon 12/22/2008 6:26:51 PM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA8008F99040, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.


On Mon 12/22/2008 5:54:27 PM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA8008496BB0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.


On Mon 12/22/2008 5:02:47 PM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA80085A3BB0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.


On Mon 12/22/2008 5:01:34 AM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA800838DBB0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.


On Mon 12/22/2008 4:53:06 AM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA80044BC3A0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.


On Mon 12/22/2008 4:42:55 AM your computer crashed
This was likely caused by the following module: atikmdag.sys
Bugcheck code: 0x3B (0xC0000094, 0xFFFFFA6002470DFB, 0xFFFFFA600960F7C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In the case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




Now I have tried reinstalling everything including DX HELP!
 
If you're already uninstalled, re-downloaded, and reinstalled your GPU drivers, then yes, it's probably time to RMA to MSI. What are temps like on the card? Abnormally high? Is there any visible damage -- blown capacitors / voltage regulators?

It could be your PSU, but is more likely the card itself.
 
Do you have another pc, or a friends pc that you can throw the card into? if it artifacts in another pc, then yea, it's the card. If it runs fine, then it could be the psu, or maybe even some corrupted driver remnants.
 
I dont have another PC to try but I DO have a 4870 That I am going to try and pop in. Im using a Silverstone Zues 850 Watt Supply that has been very good to me ... Ill see how this regular flavor 4870 does... Im trying NOt to have to reinstall my system... This takes me like DAYS to get it right..
 
Moral of the story: Pay the $70 or so for Norton Ghost or Acronis True Image, install Vista once, get everything up to date, image it. Reinstalls take 15 minutes from then on.
 
I heard that systems with Vista 64 and more than 4GB of RAM have issues with the HD 4870X2.
 
Be sure your motherboard BIOS is up to date. I had issues with my 4870X2 until I did that. Random reboots.
 
Update -


I tried a Vanilla Sapphire HD4870 and it runs like a top. In fact I used to notice a screen flicker on dark backround (which I thought was my new XHD3000! ) which is now gone as well. Looks like it absolutely was the MSI 4870 X2.

Looks as if I will also be without my card for weeks while I wait on the RMa :(
 
Vista X64 + 6GB DDR3 + ASUS P6T + ATI 8.12 Catalyst = no problems here so far.

And I am currently folding GPU wise so loading the 4870 X2 hard!

Also play Crysis and Crysis warhead without an issue.
 
crawlgsx said:
Vista 64
4870 X2
6GB of DDr2 1066 overclocked to 1010


Not 1 problem, from 8.8-8.12
Click to expand...

Wouldn't that be a 56MHz UNDERclock?

8GB 1066 P5E here. Not prob with stock clock 4870X2.
It's probably the factory OC that killed the card.
 
Hypernova said:
Wouldn't that be a 56MHz UNDERclock?

8GB 1066 P5E here. Not prob with stock clock 4870X2.
It's probably the factory OC that killed the card.
Click to expand...


It could be, as with anything else. SOmeone is bound to get a dud card or a card that will not be as great. Pure statistical manufacturing errors alone will gaurantee that.
 
You must log in or register to reply here.
Back
Top