Search
Sign in with
Sign up | Sign in

Corrupt Graphic Card (HD 4850 X2)?

Last response: in Graphics & Displays
Share

Hey guys,

I'm looking for some help or advice.

I notice that if I play certain games the game would then freeze after a while (15-45min). It would make this buzzing sound then freeze.

First I thought it's something with the game, but experiencing this with a few other games makes me believe the problem is my pc. Probably my graphic card.

System Specs:
Processor: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4 CPUs), ~2.8GHz
Memory: 8192MB RAM
Video Card: ATI Radeon HD 4850 X2
Sound Card: Realtek High Definition Audio
Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Motherboard: P5Q-E
Power Supply: Be Quiet Dark Power Pro P7-PRO-850w

My OS runs on a SSD Drive and I have 3 data drives running in RAID5.

I've updated the drivers, run memtest, chkdsk.

I think it has something to do with PFN_LIST_CORRUPT rather VISTA_DRIVER_FAULT. I've really updated every components I could find and I still have this problem.

I've found this but using the methods there didn't solve my problem.

http://www.tomshardware.com/forum/568-63-bsod-pfn_list_corrupt

Here's the latest crash dump file.

  1. PFN_LIST_CORRUPT (4e)
    

  2. Typically caused by drivers passing bad memory descriptor lists (ie: calling
    

  3. MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    

  4. available get the stack trace.
    

  5. Arguments:
    

  6. Arg1: 0000000000000099, A PTE or PFN is corrupt
    

  7. Arg2: 000000000012889d, page frame number
    

  8. Arg3: 0000000000000000, current page state
    

  9. Arg4: 0000000000123add, 0
    

  10.  
  11. Debugging Details:
    

  12. ------------------
    

  13.  
  14.  
  15. BUGCHECK_STR:  0x4E_99
    

  16.  
  17. DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    

  18.  
  19. PROCESS_NAME:  plugin-contain
    

  20.  
  21. CURRENT_IRQL:  2
    

  22.  
  23. LAST_CONTROL_TRANSFER:  from fffff80002b532bc to fffff80002ac3600
    

  24.  
  25. STACK_TEXT:  
    

  26. fffff880`07dccfe8 fffff800`02b532bc : 00000000`0000004e 00000000`00000099 00000000`0012889d 00000000`00000000 : nt!KeBugCheckEx
    

  27. fffff880`07dccff0 fffff800`02a673e7 : 00000000`0417f000 fffffa80`05eb7d10 00000000`00000000 fffff880`07dcd2b8 : nt!MiBadShareCount+0x4c
    

  28. fffff880`07dcd030 fffff800`02ddb155 : fffff980`212c0000 fffff8a0`0fe53200 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2c19b
    

  29. fffff880`07dcd310 fffff800`02adc447 : 00000000`04140000 fffffa80`06d80320 00000000`00000000 00000000`04200000 : nt!CcUnmapVacb+0x5d
    

  30. fffff880`07dcd350 fffff800`02ae7f57 : fffffa80`082c7101 fffff880`009f37f0 00000000`00000005 fffffa80`0af90780 : nt!CcUnmapVacbArray+0x1b7
    

  31. fffff880`07dcd3e0 fffff880`0142ff5c : 00000000`035f7000 00000000`035f7000 fffff8a0`01aaec70 fffffa80`082c7180 : nt!CcSetFileSizesEx+0x2a7
    

  32. fffff880`07dcd460 fffff880`014a76a0 : 00000000`00000000 7fffffff`ffffffff 00000000`000035f7 00000000`00000001 : Ntfs!NtfsSetBothCacheSizes+0x50
    

  33. fffff880`07dcd4c0 fffff880`014958dd : fffff880`089176f0 fffffa80`092cf450 00000000`00000001 00000000`00000000 : Ntfs!NtfsDeleteAllocation+0x2cc
    

  34. fffff880`07dcd5a0 fffff880`014a2212 : fffff880`089176f0 00000000`00000001 fffff980`169f1038 00000000`00000001 : Ntfs!NtfsDeleteAllocationFromRecord+0x16d
    

  35. fffff880`07dcd660 fffff880`014bbc0a : fffff880`089176f0 fffff8a0`01aaeb40 fffff8a0`074a6bc0 fffff880`07dcd95c : Ntfs!NtfsDeleteFile+0x346
    

  36. fffff880`07dcd8e0 fffff880`01429aa9 : fffffa80`0b02db60 fffff800`02d68a86 fffff880`08917650 fffffa80`06df6aa0 : Ntfs!NtfsCommonCleanup+0x15da
    

  37. fffff880`07dcdcf0 fffff800`02abb487 : fffff880`08917650 00000000`00000000 00000000`00000000 fffff800`02aa1b06 : Ntfs!NtfsCommonCleanupCallout+0x19
    

  38. fffff880`07dcdd20 fffff800`02abb441 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
    

  39. fffff880`08917520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    

  40.  
  41.  
  42. STACK_COMMAND:  kb
    

  43.  
  44. FOLLOWUP_IP: 
    

  45. nt!MiBadShareCount+4c
    

  46. fffff800`02b532bc cc              int     3
    

  47.  
  48. SYMBOL_STACK_INDEX:  1
    

  49.  
  50. SYMBOL_NAME:  nt!MiBadShareCount+4c
    

  51.  
  52. FOLLOWUP_NAME:  MachineOwner
    

  53.  
  54. MODULE_NAME: nt
    

  55.  
  56. DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    

  57.  
  58. IMAGE_NAME:  memory_corruption
    

  59.  
  60. FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    

  61.  
  62. BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    

  63.  
  64. Followup: MachineOwner

More about : corrupt graphic card 4850

Register or log in to remove

Tamz_msc said:
Have you monitored the temperatures?


Yeah. For testing the Video Card I used FurMark and monitoring the other components also seem ok. It's unlikely that it is a heat issue because I can play certain games without a problem.

I'd say it's either a driver not compatible with Win7 or some components might be defect which I have my doubts because like I said only for certain games the BSOD would show up. Less occasionally but the BSOD shows up in desktop mode too.

Most recently I've been playing Fallout NV for a few weeks now and never has it genereated a BSOD. But yesterday it did. Here's the crash dump file.

  1. PFN_LIST_CORRUPT (4e)
    

  2. Typically caused by drivers passing bad memory descriptor lists (ie: calling
    

  3. MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    

  4. available get the stack trace.
    

  5. Arguments:
    

  6. Arg1: 0000000000000099, A PTE or PFN is corrupt
    

  7. Arg2: 000000000003d92b, page frame number
    

  8. Arg3: 0000000000000002, current page state
    

  9. Arg4: 000000000003d920, 0
    

  10.  
  11. Debugging Details:
    

  12. ------------------
    

  13.  
  14.  
  15. BUGCHECK_STR:  0x4E_99
    

  16.  
  17. CUSTOMER_CRASH_COUNT:  1
    

  18.  
  19. DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    

  20.  
  21. PROCESS_NAME:  FalloutNV.exe
    

  22.  
  23. CURRENT_IRQL:  2
    

  24.  
  25. LAST_CONTROL_TRANSFER:  from fffff80002d5f38c to fffff80002ccf740
    

  26.  
  27. STACK_TEXT:  
    

  28. fffff880`0a10e198 fffff800`02d5f38c : 00000000`0000004e 00000000`00000099 00000000`0003d92b 00000000`00000002 : nt!KeBugCheckEx
    

  29. fffff880`0a10e1a0 fffff800`02d41cd9 : 00000000`00000000 fffffa80`0085e810 0000000f`ffffffff fffff8a0`120e16e0 : nt!MiBadShareCount+0x4c
    

  30. fffff880`0a10e1e0 fffff800`02d15ac1 : 90f00000`00000000 fffff680`002b9590 00000000`00000200 000fffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x32525
    

  31. fffff880`0a10e260 fffff800`02d10dee : 00000000`00000002 fffff880`00000000 fffffa80`06fb2980 fffffa80`06fb2d18 : nt!MiDecommitPages+0x1a1
    

  32. fffff880`0a10eaf0 fffff800`02cce993 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
    

  33. fffff880`0a10ebe0 00000000`7711ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    

  34. 00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7711ff3a
    

  35.  
  36.  
  37. STACK_COMMAND:  kb
    

  38.  
  39. FOLLOWUP_IP: 
    

  40. nt!MiBadShareCount+4c
    

  41. fffff800`02d5f38c cc              int     3
    

  42.  
  43. SYMBOL_STACK_INDEX:  1
    

  44.  
  45. SYMBOL_NAME:  nt!MiBadShareCount+4c
    

  46.  
  47. FOLLOWUP_NAME:  MachineOwner
    

  48.  
  49. MODULE_NAME: nt
    

  50.  
  51. DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    

  52.  
  53. IMAGE_NAME:  memory_corruption
    

  54.  
  55. FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    

  56.  
  57. BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    

  58.  
  59. Followup: MachineOwner
Register or log in to remove
 
Ask the community
Read discussions in other Graphics & Displays categories
!