Windows 7 Random BSOD's - dumps included

[Dunglebion]

Hello!

I'm experiencing BSOD's everyday. Example when I start a game (i.e. CS:GO, BF3) I will get BSOD in the first 1min of the game, everytime. When I boot the pc, sometimes it says overcloking failed, or just goes to windows error recovery... After this BSOD I go back to play the same game, it crashes sometimes again and again, and sometimes it lets me play for like 30-60min before the next BSOD. Also happend once in YouTube, but beside that always ingame.

I have run memtest overnight without errors and also FurMark burn a while, but it didnt bsod.

Rig (everything should be @ stock):
AMD Phenom II 965BE + Mugen 2
M4A79XTD EVO
2x2GB Kingston HyperX 1600mhz DDR3 CL9
MSI GTX480-TI 448 TwinFrozr III
Samsung SpinPoint F3 1TB
SF GoldenKing Platinium 550W


Minidumps, CPU-Z, RAMMon included.

Thanks for your time helping me.

 

[usasma]

Uploaded files don't include systeminfo report and MSINFO32 report. Please rerun the collection tool again and include these reports for a more complete analysis.

Please stop running Driver Verifier. It's not needed any longer and it will cause your system to crash.

If overclocking, please stop the overclock while we're troubleshooting. Feel free to resume it once the BSOD's have stopped.

If you're using a wireless USB networking device, please un-install it's software and remove the device from your system in order to test to see if this is the cause. Either use a very long cord, move the computer nearer to the router/modem, or use a wireless PCI/PCIe card that plugs into your motherboard.

Here's my rant on wireless USB network devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Regardless of what you're using, the following driver is blamed by several of the memory dumps. Please remove it from your system and then test for further BSOD's.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

DlinkUDSMBus.sys Tue Nov 11 02:01:28 2008 (49192DC8)
TCP UDS Master Bus of Kernel USB Software Bus
Link Removed



Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Mon Dec 10 14:25:11.043 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121012-18954-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:05:28.198[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+5a11 )[/B]
BugCheck [B]24, {1904fb, fffff88008ff3478, fffff88008ff2cd0, fffff8800129a914}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000001904fb
Arg2: fffff88008ff3478
Arg3: fffff88008ff2cd0
Arg4: fffff8800129a914
PROCESS_NAME: [B]csgo.exe[/B]
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
FAILURE_BUCKET_ID: [B]X64_0x24_VRF_Ntfs!_??_::NNGAKEGL::_string_+5a11[/B]
  BIOS Version                  2102   
  BIOS Release Date             06/17/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 10 13:55:52.499 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121012-21122-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 4:57:03.686[/B]
*** WARNING: Unable to verify timestamp for WmBEnum.sys
*** ERROR: Module load completed but symbols could not be loaded for WmBEnum.sys
Probably caused by :[B]WmBEnum.sys ( WmBEnum+37f8 )[/B]
BugCheck [B]C9, {24c, fffff880130337f8, fffff98016f1ed30, 103}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
    call to IoMarkIrpPending.
Arg2: fffff880130337f8, The address in the driver's code where the error was detected.
Arg3: fffff98016f1ed30, IRP address.
Arg4: 0000000000000103, Status code.
BUGCHECK_STR:  0xc9_24c
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xc9_24c_VRF_WmBEnum+37f8[/B]
  BIOS Version                  2102   
  BIOS Release Date             06/17/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 14:04:17.988 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-21871-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_91919191`91919191
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_91919191`91919191
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:27.518[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_91919191`91919191
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_91919191`91919191
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]1A, {5003, fffff70001080000, 98b, 98d00001300}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000098b
Arg4: 0000098d00001300
BUGCHECK_STR:  0x1a_5003
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 10:32:07.209 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-22635-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_87878787`87878787
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_87878787`87878787
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 4:41:11.364[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_87878787`87878787
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_87878787`87878787
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]C1, {fffff98015514fe0, fffff98015514708, 934028, 23}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff98015514fe0, address trying to free
Arg2: fffff98015514708, address where bits are corrupted
Arg3: 0000000000934028, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
BUGCHECK_STR:  0xC1_23
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec  6 09:05:27.371 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120612-17737-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039818c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`039818c0
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:06:42.916[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039818c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`039818c0
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039818c0
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`0397e8c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`0397e8c0
Probably caused by :[B]Unknown_Image ( Unknown_Module_fffffa80_0397e8c0+22877e8 )[/B]
BugCheck [B]C4, {13f, fffff980383f8fe0, 1c, fffffa8004bd8410}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 000000000000013f, Number of memory bytes being freed is different from the number of bytes tracked by Verifier.
Arg2: fffff980383f8fe0, Address of the pool block being freed.
Arg3: 000000000000001c, Number of bytes being freed.
Arg4: fffffa8004bd8410, Pointer to the number of bytes tracked by Verifier.
BUGCHECK_STR:  0xc4_13f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec  6 08:14:20.962 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120612-18423-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:14.492[/B]
*** WARNING: Unable to verify timestamp for DlinkUDSMBus.sys
*** ERROR: Module load completed but symbols could not be loaded for DlinkUDSMBus.sys
Probably caused by :[B]DlinkUDSMBus.sys ( DlinkUDSMBus+6a31 )[/B]
BugCheck [B]C2, {9d, 4e7, 0, fffff88000de1a31}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000009d, Attempt to allocate pool with a tag that does not contain any letters or digits.
    Using these tags makes tracking pool issues very hard.
Arg2: 00000000000004e7, Incorrect pool tag used.
Arg3: 0000000000000000, Pool type
Arg4: fffff88000de1a31, Caller's address.
BUGCHECK_STR:  0xc2_9d
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xc2_9d_VRF_DlinkUDSMBus+6a31[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec  6 07:37:58.926 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120612-18813-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:17.472[/B]
*** WARNING: Unable to verify timestamp for DlinkUDSMBus.sys
*** ERROR: Module load completed but symbols could not be loaded for DlinkUDSMBus.sys
Probably caused by :[B]DlinkUDSMBus.sys ( DlinkUDSMBus+6a31 )[/B]
BugCheck [B]C2, {9d, 4e7, 0, fffff88013dcaa31}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000009d, Attempt to allocate pool with a tag that does not contain any letters or digits.
    Using these tags makes tracking pool issues very hard.
Arg2: 00000000000004e7, Incorrect pool tag used.
Arg3: 0000000000000000, Pool type
Arg4: fffff88013dcaa31, Caller's address.
BUGCHECK_STR:  0xc2_9d
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xc2_9d_VRFK_DlinkUDSMBus+6a31[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec  3 09:31:23.963 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-17737-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:14.118[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1dae55 )[/B]
BugCheck [B]19, {20, fffffa800888ad60, fffffa800888ae30, 40d0006}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800888ad60, The pool entry we were looking for within the page.
Arg3: fffffa800888ae30, The next pool entry.
Arg4: 00000000040d0006, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME: [B]dwm.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x19_20_nvlddmkm+1dae55[/B]
  BIOS Version                  2102   
  BIOS Release Date             06/17/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  1 09:38:55.901 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120112-17503-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 4:34:39.415[/B]
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
Probably caused by :[B]VBoxNetFlt.sys ( VBoxNetFlt+659b )[/B]
BugCheck [B]D1, {22, 2, 0, fffff8800143c5a0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000022, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800143c5a0, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Steam.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VBoxNetFlt+659b[/B]
  BIOS Version                  2102   
  BIOS Release Date             06/17/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Mon Dec 10 14:25:11.043 2012 (UTC - 5:00)**************************
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
Rt64win7.sys                Thu Aug 20 12:05:06 2009 (4A8D7432)
nvoclk64.sys                Tue Sep 15 17:59:25 2009 (4AB00E3D)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys                Tue Apr 27 16:09:26 2010 (4BD74476)
WmBEnum.sys                 Tue Apr 27 16:10:19 2010 (4BD744AB)
viahduaa.sys                Sat May 15 06:22:39 2010 (4BEE75EF)
cpuz135_x64.sys             Tue Nov  9 08:33:36 2010 (4CD94DB0)
nvhda64v.sys                Wed Apr 18 13:07:54 2012 (4F8EF4EA)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec  6 08:14:20.962 2012 (UTC - 5:00)**************************
[COLOR=RED][B]DlinkUDSMBus.sys            Tue Nov 11 02:01:28 2008 (49192DC8)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  1 09:38:55.901 2012 (UTC - 5:00)**************************
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
VBoxDrv.sys                 Tue Jun  5 10:02:20 2012 (4FCE116C)
VBoxNetFlt.sys              Tue Jun  5 10:02:20 2012 (4FCE116C)
VBoxUSBMon.sys              Tue Jun  5 10:02:21 2012 (4FCE116D)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Dunglebion]

Here are the missing infos.

Driver Verifier is stopped now, tried to troubleshoot with it by myself, didnt work out so well

No overclokings. Default options in BIOS now, the only I had there were the memory dimms set manually to 9-9-9-27 and 1600MHz, because the auto option put them 9-9-9-24 and 1333MHz.

I'm not using / I don't have usb network devices, so that driver can be uninstalled, the problem is how to uninstall it if I don't know the program?
Only thing I can think of could be Dlink Shareport Utility in my last router, but I have uninstalled that program a while ago, because I've had Cisco router for some time now.

 

[usasma]

Try this to remove the DLink driver:

1) Create a Restore Point using System Restore
2) Create a Repair disc by going to Start...All Programs...Maintenance...Create a System Repair Disc
3) Test the System Repair disc to make sure that you can get to the System Restore entry when you boot from the disk (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns) and use it to disable any instances of DlinkUDSMBus.sys that are starting (or any other DLink entries) (DO NOT DELETE - only disabled by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of DlinkUDSMBus.sys (or any other DLink entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of DlinkUDSMBus.sys or any other DLink entries are disabled.
7) Go to C:\Windows\System32\drivers and rename the DlinkUDSMBus.sys driver to DlinkUDSMBus.BAD


In the event that the system doesn't boot:

1) Boot from the System Repair disc and use the Command Prompt option to rename DlinkUDSMBus.BAD to DlinkUDSMBus.sys
2) Boot from the System Repair disc and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

If the problems continue, please start with these free diagnostics: Link Removed

 

[Dunglebion]

Still having the problem, I started doing those hardware diagnostics:

Memtest ran overnight without erros.
SeaTools for Windows - Long Generic pass, S.M.A.R.T pass,
Malware MS Security Essentials - Trendmicro - Bitdefender - F-secure without infections found

Furmark burn-in test bluescreened after <10min, max gpu temperature 67c
2nd try like 30min

Prime95 - max CPU temp 56c
"Small FFTs"
1st ran 2s before bluescreen.
2nd try about 3h without errors
3rd try 1min and bluescreen
4th try 1min and bluescreen
"Blend"
1st try 10s bluescreen
2nd try 10s bluescreen
3rd try 60min bluescreen
4th try 1min bluescreen
"Large FFTs"
1st try 10s bluescreen
2nd try 1min bluescreen

There's no dumps generated from these.

Does this look like a CPU problem?

 

[GeneralHiningII]

possibly - have you checked that the CPU fan is plugged into the CPU Fan Socket correctly (ie: Fully inserted), the CPU is inside the socket correctly, etc etc.

IMO, RAM is real cheap nowadays, I don't see why you're only running 4GB of total memory - 4GB is ok, but why not go 8GB, 16GB, 32GB, 64, 128 (yeah cant actually go that high, but you get the point) - there is a possibility that you may not have enough memory in your system (possibly).

 

[usasma]

Great work on the tests!!!

Prime95 basically tests 3 things:
- RAM
- Memory Controller (either on the mobo, or built into the CPU - yours is built into the CPU)
- CPU Cache

Since your memory controller is built into your CPU we have 2 possibilities:
- RAM
- CPU

Run several of the CPU stress tests further down on the diagnostic page. If the CPU passes, then you can presume it's the RAM (but we'll need to look more at the video card at this point).
BTW - you can run the Prime95 tests (use the Blend test) on individual sticks/slots to see if that'll help point out the faulting stick(s)/slot(s)

I'm thinking that the video test (FurMark) isn't a real good indicator of a problem with the video card - since the BSOD's took longer with it than they did with Prime95. If it comes down to a choice between RAM or the video card, I'd vote for the RAM being the problem (but I don't have to pay for the new parts!). If we reach that point, let's talk about other options (such as borrowing a video card to test with).

Good luck!

 

[Dunglebion]

I've just bought new noctua CPU fan, so that should be fine. I'll check the cpu socket installation.

I have 8GB of total memory, I've bought 4GB more like a year ago, and I was only using the newest 4GB of ram, so I could be more sure they are healthy for this troubleshooting. I can try with the 8GB too, but when the problem started I had 8GB installed, and it continues with the 4GB, so I guess the problem isn't in the memory.
There is just little difference between the new and old rams. Both are 2x2GB Kingston HyperX 1600Mhz, just that the new ones are something called XMP and the older arent.

 

[GeneralHiningII]

Its better to have 2x4GB RAM then 4x2GB RAM. Why?

RAM is storing memory. Lets say, for example, you have 4 dams (figurative for RAM sticks) that hold 2 (million) Litres each. To give water to everyone, all 4 dams have to let their water flow to the central distribution plant (ie: the CPU). You're putting more load on the staff at the Distrib. Plant, because they have to manage water flowing from 4 different places.
IF, however, you have 2 dams, each holding 4 (million) Litres each, then your workers at the distribution plant won't have as much work to do, but still distributing and receiving the same amount of water.

Apply this to your situation (if you wish), and see if that helps.

 

[usasma]

*bump*
I was posting at the same time as you were :0)
See my previous post.

 

[Dunglebion]

At this time the pc is running Prime95 Large FFTs for 4h without any problems, strange that sometimes it works and sometimes it doesnt.

Thanks for the tip Usasma, that I can test the invidual sticks with prime95, I'll try that and then move on to the other CPU tests and see what happens.

Thanks guys for all the help so far.

--------------
So much replies at the same time

Mobo and CPU were bought 11/2009 when I built the PC, so they are the oldest parts
I've bought more memory 08/2011
Better PSU bought 01/2012
Video card is the newest 05/2012, so i really hope its not the video card

 

[Dunglebion]

So i've run more CPU tests:

S&M CPU test
CPU+Memory crash in 2min
Only CPU pass
Only Memory pass

Hot CPU tester pro
pass

LinX
full memory usage bluescreened in 5s
full memory usage froze in 3min

The strange thing was that I downloaded LinX, extracted it, created desktop shortcut and started to run it, after the crash I rebooted the pc and noticed the desktop icon was missing, so it apparently roll-backs few minutes when it crashes, I have noticed this before also when I was writing results to notepad and it lost the last few lines i wrote before the crash.

 

[usasma]

Tough choice time now (IMO) - is it the CPU or not?
It seems to me that it is (from the results that you just posted) - but I'm not the one who'll buy the new CPU.

You could choose to replace the RAM instead (which will be cheaper).
Then return it if it doesn't stop the BSOD's (and then purchase a new CPU)

Good luck!

 

[Dunglebion]

Yesterday system was stable somehow, I played many hours without problems which is suprising. Once I booted my pc, and after that it started to bluescreen few times when I tried to play, and then it was stable for many hours again... So annoying that it seems to work sometimes and sometimes not

Yes it really seems tough choice... So can we be sure it is the CPU or memory? Is there possibility it would be motherboard? Well anyway if I have to get new CPU, I'm going to buy Intel and that means new mobo also, it's just going to be expensive to try, but pretty sure it'll fix the problem. Also memorys are so cheap to try... since 2x4GB costs here only 40-50€
Those parts are 3years old, so no warranty, I guess its normal nowadays that something stops working just after the warranty has expired.

Well, thank you John for all your help locating the problem. Now I just have to consider my choices, how much I wanna pay for playing pc games

 

[GeneralHiningII]

Maybe see if your friends have some spare RAM sticks lying around that you could test, just to be sure?