win 7 64 bit crash

[mushers]

hi all i built a new pc a few weeks ago and have been suffering from blue screens while playing world of warcraft surfing or streaming utube any help would be great

system is

asus m4a87td board

amd phenom 955

pny 2x 2 gig 10660

western digital green star 1tb drive

450w icute psu (voltages seem ok in bios )

saphire hd5450

tried all the usual updated all drivers then ive rolled some back tried generic drivers used driver sweeper to rid all old vga drivers even uninstalled all none esential software unplugged excess hardware took the board back to supplier got a new one still same issues

ran memtest over night no errors there tried an old x1650 gfx card still no help

will add dmp's in a sec
ps uninstalled usb3 drivers last night in a fit of add remove hoping to find the issue by chance

 

[Jonathan_King]

Hello, and welcome to SF!

Start by installing these updated Realtek Ethernet drivers: Realtek

I have to suspect a hardware problem, though. In particular, there are signs pointing to a bad graphics card. Do you have another one you can try? If not, you might RMA your card.

I think RAM is another component worth testing. See this guide: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 17:27:49.358 2010 (UTC - 5:00)
System Uptime: 0 days 0:44:12.090
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 16:42:55.907 2010 (UTC - 5:00)
System Uptime: 0 days 0:20:38.265
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 17:56:09.669 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:10.401
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 17:15:53.275 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:19.633
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xc2_7_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 17:11:48.569 2010 (UTC - 5:00)
System Uptime: 0 days 1:12:28.301
Probably caused by : tcpip.sys ( tcpip!InetDereferenceAf+9 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_tcpip!InetDereferenceAf+9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 15:25:49.862 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:44.220
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 14:28:31.221 2010 (UTC - 5:00)
System Uptime: 0 days 0:44:11.678
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 16:03:23.418 2010 (UTC - 5:00)
System Uptime: 0 days 1:04:11.776
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngFntCacheLookUp+6ab5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TurboV_EVO.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!EngFntCacheLookUp+6ab5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 11 04:05:39.561 2010 (UTC - 5:00)
System Uptime: 0 days 11:54:19.294
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Launcher.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 16:00:18.929 2010 (UTC - 5:00)
System Uptime: 0 days 0:20:18.662
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[mushers]

will give the realtek drivers one more go although i have tried disabling the onboard and using an expansion ethernet with no luck i have tried a different gfx card with no luck its an x1650 its didnt install well may try to pinch a friends for a night this weekend ram all tested ok on memtest
i shall let you know how i get on with realtek drivers later

 

[Jonathan_King]

Alright, sounds good.

You may also run Prime95, when you get a chance.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[mushers]

ok updated nic drivers havent had pc on very long to see if it has fixed issue ran prime and got this

[Sun Dec 19 11:34:52 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

 

[Jonathan_King]

Was "round off error checking" ticked? How long did the test run for, before it failed?

 

[mushers]

it is now and re running tests it only ran for a few minute before getting this error ill let you know if it stops this time

 

[mushers]

should amd 955 chips run at 89 degrees ?

 

[mushers]

problem sorted after checking amd's max safe temp for the chip and seeing mine go way past it under what i would not consider heavy loads i took the motherboard and chip bought as a bundle to the retailer got my money back and bought the bits elsewhere
thanks for the help looking into the blue screens i should have checked temps earlier

 

[Jonathan_King]

Good call. 89 is way high for AMD CPUs, even under high load. I hope that resolves the issue!