Solved Random BSOD

[rukh]

Hi,

as many before me I am experiencing BSOD's with unknown nature. Sometimes it is two weeks without even a single BSOD and sometimes it can crash like 10 times a day with several different blue screen. I tried playing with drivers, BIOS updates, temperature monitoring and many others and can't get to the source of the problem, so here I am.

Besides I did about 4-5 all night memory tests with memtestx86 (no errors). Tested the OS with AIDA64, OCCT and something for the GPU itself (no crashes). Made a Windows scandisk check (no bad sectors). Made the the CPU sweat with SuperPI (no problems)

What may be important is that 95% of those crashes occured while playing League of Legends that has a client based on Adobe Air tech.

Please advice, I have placed system information in the attachment.

Is Windows 7 . . .
- x86 (32-bit) or x64 ?

x64

- the original installed OS on the system?

HDD after a full format and then Win7 installed, one partition, 500GB

- an OEM or full retail version?

OEM (but I was re-installing it)

- What is the age of system (hardware)?

4 months

- What is the age of OS installation (have you re-installed the OS?)

4 months (I did re-install the OS)

Regards,
R.

 

[usasma]

Daemon Tools has a driver (sptd.sys) that is known to cause BSOD's in Win7 systems. FYI - Alcohol 120% has the same driver.
Please do the following:
- uninstall Daemon Tools
- use this free tool to ensure that the offending sptd.sys driver is completely removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

I'm pretty sure that Daemon Tools is the cause, but I'll post more in the morning (after the memory dumps finish running).......

 

[usasma]

Yes, it looks like Daemon Tools to me - but it's possible there may be other causes.
Plesae remove Daemon Tools as described above and monitor for further BSOD's.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080111-15100-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug  1 12:13:54.525 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:17.369
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`003574c0 73000000`3acc4025 fffffa80`046069e0
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080111-15194-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 19:10:56.441 2011 (UTC - 4:00)
System Uptime: 0 days 2:18:43.124
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e
Bugcheck code 00000050
Arguments fffff8a0`096c6d58 00000000`00000000 fffff880`0fd5dd26 00000000`00000002
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-14024-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 16:52:09.823 2011 (UTC - 4:00)
System Uptime: 0 days 9:49:39.666
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`000abca6 00000000`00000002 00000000`000abc6a
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\071311-12994-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul 13 17:35:03.051 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:42.895
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::AddCommitment+83 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::AddCommitment+83
Bugcheck code 00000050
Arguments fffffa80`0e508010 00000000`00000000 fffff880`02fa035b 00000000`00000002
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\071311-14632-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul 13 17:32:00.499 2011 (UTC - 4:00)
System Uptime: 0 days 0:55:09.717
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LolClient.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0001f3ab 00000000`00000002 00000000`0003cc2a
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\071311-13431-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul 13 16:35:37.437 2011 (UTC - 4:00)
System Uptime: 0 days 5:45:22.280
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`002314c0 5ea00000`3da6a867 fffffa80`06b2e4c0
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\063011-16411-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun 30 10:56:46.707 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.924
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck F7, {fffff880033aedc8, 2b992ddfa232, ffffd466d2205dcd, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+1d5616 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
BUGCHECK_STR:  0xF7
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xF7_MISSING_GSFRAME_nvlddmkm+1d5616
Bugcheck code 000000F7
Arguments fffff880`033aedc8 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062811-15022-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 28 16:00:16.108 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:11.951
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_62
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_62_LEAKED_POOL_IMAGE_nvlddmkm.sys
Bugcheck code 000000C4
Arguments 00000000`00000062 fffffa80`060dcbd8 fffffa80`061004a0 00000000`00000002
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062511-31683-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 24 20:05:34.109 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:10.952
Probably caused by : CI.dll ( CI!SHATransform+d4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_CI!SHATransform+d4d
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`04ab3605
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062411-14164-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 24 07:06:25.307 2011 (UTC - 4:00)
System Uptime: 0 days 1:52:00.151
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00028116 00000000`00000001 00000000`00121b16
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062311-12246-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun 23 09:18:06.797 2011 (UTC - 4:00)
System Uptime: 0 days 3:51:22.640
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+89 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_fileinfo!FIStreamLog+89
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`033932c8 fffff880`03392b20 fffff800`04ed9a5a
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062111-14383-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 17:51:17.145 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.988
Probably caused by : CI.dll ( CI!I_FindFileOrHeaderHashInCatalogs+3d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_CI!I_FindFileOrHeaderHashInCatalogs+3d7
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`04aab605
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061911-13431-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 19 08:28:13.846 2011 (UTC - 4:00)
System Uptime: 0 days 4:13:59.064
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LoLLauncher.ex
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00090d2b 00000000`00000000 00000000`000c4d2b
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061411-12885-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 14 14:30:25.476 2011 (UTC - 4:00)
System Uptime: 0 days 3:18:42.319
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0004e4c0 4f400000`04e81867 fffffa80`0728da40
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061211-25147-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 11:04:25.062 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:10.280
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`04001308 fffff980`0a162ee0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-17191-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 04:30:06.964 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.807
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`0415c308 fffff980`0a4a4ee0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-21325-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 03:01:02.058 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:18.901
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_0_tcpipreg!InterfaceAddressRegKeyChangeHandler+109
Bugcheck code 000000C4
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-17643-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 03:00:10.363 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:18.581
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_0_tcpipreg!InterfaceAddressRegKeyChangeHandler+109
Bugcheck code 000000C4
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-17253-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 02:59:31.230 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:19.073
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_0_tcpipreg!InterfaceAddressRegKeyChangeHandler+109
Bugcheck code 000000C4
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-17846-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 02:58:30.734 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:15.951
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_0_tcpipreg!InterfaceAddressRegKeyChangeHandler+109
Bugcheck code 000000C4
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061011-14773-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 10 03:24:37.697 2011 (UTC - 4:00)
System Uptime: 0 days 1:07:23.914
Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )
BUGCHECK_STR:  0xA0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA0_nt!PopWriteHiberPages+a3
Bugcheck code 000000A0
Arguments 00000000`0000000b 00000000`bf307000 00000000`00000003 00000000`195f2000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060911-12667-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun  9 15:37:56.671 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:49.888
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1a_41284_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`3c3a1001 00000000`0002c007 fffff700`01080000
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060511-15522-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun  4 20:48:35.033 2011 (UTC - 4:00)
System Uptime: 0 days 0:34:59.935
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0006078b 00000000`00000002 00000000`0005da8a
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053011-14180-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 30 16:45:19.619 2011 (UTC - 4:00)
System Uptime: 0 days 6:14:11.837
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0003c07e 00000000`00000003 00000000`000334fd
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052611-14461-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 26 10:06:54.760 2011 (UTC - 4:00)
System Uptime: 0 days 1:19:39.977
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+201
Bugcheck code 00000050
Arguments fffff8a0`0a4441a8 00000000`00000001 fffff880`0ffc1e79 00000000`00000002
BiosVersion = P1.60
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[rukh]

Thanks a lot mate. I will try it after getting back from work, great community support! If this works I'll get back here to tell everyone else looking that this was the case.

Do you have any recommendations for a replacement for Deamon Tools?

Thanks!

 

[usasma]

I use Virtual Clone Drive and Magic ISO - but dunno if they'll suit your needs (since I've never used Daemon Tools).

 

[rukh]

Unfortunately I am back...

It was OK for quite some time and today I had a crash related to MEMORY_MANAGEMENT. I have excluded old minidumps from the zip attached to this post, old ones are in the first post.

Thanks in advance!

Regards,
R.

 

[usasma]

This one points to the video sub-system on your computer - but not directly (as it blames a Windows component - dxgmms1.sys ). From your post above, you've run memory tests and FurMark along with other diagnostics and stress tests and had experienced no errors.

Have you updated Adobe Air to the latest version ( http://get.adobecom/air/ )?
Have you checked for any updates/patches for League of Legends?
Have you updated your video drivers to the latest available from the nVidia website (nVidia Poland: Pobieranie sterowników NVIDIA )?
Is this a Desktop or a Laptop?

If it's a Desktop, ensure that:
- the video card cooler is free of dust/clogs
- the video card has adequate power and that the connectors are firmly seated
- the video card cooler fan is working/moves freely
- the video card has adequate cool airflow (as it passes through the case). You can test this by opening the case and pointing a house fan at the video card.

If it's a Laptop, blow out all vents with canned air (don't use an air compressor or a vacuum as they can cause damage) and ensure that the fan is working. Place the laptop on a hard surface when using it (or use a cooling pad).

Please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

If that doesn't identify the problem app, please uninstall the AsRock utilities. I'm particularly suspicious of the AsrAppCharger and the ASRock eXtreme Tuner

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\081711-16520-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 16 18:12:19.736 2011 (UTC - 4:00)
System Uptime: 0 days 7:19:23.579
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`002574c0 4d500000`c3279805 fffff680`000262e8
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[rukh]

Basically this card isnt brand new in this PC. It was already running for couple of months in my previous PC (about 3 months or so) so I am not very suspiocious about her. I will setup the verifier.



Have you updated Adobe Air to the latest version ( http://get.adobecom/air/ )?

Yes, all up to date.

Have you checked for any updates/patches for League of Legends?

It has an auto patcher, has to be up to date to run.

Have you updated your video drivers to the latest available from the nVidia website (nVidia Poland: Pobieranie sterowników NVIDIA )?

Updating now. I think I had previous-latest WHQL drivers before.

Is this a Desktop or a Laptop?

Desktop.

If it's a Desktop, ensure that:
- the video card cooler is free of dust/clogs

Cleaned it up, changed even the PCI-E slots few times.

- the video card has adequate power and that the connectors are firmly seated

It is overpowered, 600W with OCZ PSU, all connectors seated.

- the video card cooler fan is working/moves freely

It runs fine.

- the video card has adequate cool airflow (as it passes through the case). You can test this by opening the case and pointing a house fan at the video card.

I have two additional coolers in my case and temperatures according to the BIOS/OS are looking fine. This BSOD is popping up once/two weeks sometimes so it is hard to put a house fan on it and leave it there

Thanks!

EDIT: Verifier didn't come out with anything after reboot so I will leave it for some time and look for BSODS.

 

[usasma]

Let verifier run for at least 36 hours of normal use (longer if you can stand it).

If it doesn't crash and give us a minidump, let us know and we'll switch to full memory dumps and have some other folks take a look at the large memory dump.

 

[rukh]

Verifier is on for 3 days now, I had two BSOD's since then but none of them were caused by the verifier. I can leave him turned on, it is not interrupting with normal PC usage.

BSOD PAGE_FAULT_IN_NONPAGED_AREA occured when I have noticed that youtube video is choking (sound was ok) so I tried restarting the browser (Chrome) and in the very moment I have pressed 'X' button then it crashed.

Today I did uninstall the AsrAppCharger and the ASRock eXtreme Tuner you mentioned earlier.

New minidumps attached.

Regards,
R.

 

[usasma]

If it's not crashing it doesn't need to be on.
Also, it'll unecessarily complicate things if left on - please turn it off.

Since you ran verifier according to my instructions, then it's most likely that there's not a problem with 3rd party drivers. That leaves hardware problems as the next most likely (and I suspect the video card from a previous post). Please do the following:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources - Bootable Disks

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 105ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. Two other video stress tests (may be more stressful than FurMark):
NOTE: I have had reports that some ISP's will block this website
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!

CPU Stress Tests:
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\082111-35178-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 10:09:57.863 2011 (UTC - 4:00)
System Uptime: 0 days 2:09:43.706
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObpCloseHandleTableEntry+3e
Bugcheck code 00000050
Arguments fffff8a0`0a163d18 00000000`00000000 fffff800`04d78ebe 00000000`00000002
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\082111-13509-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 04:49:27.530 2011 (UTC - 4:00)
System Uptime: 0 days 0:25:21.747
BugCheck D1, {fffffa800d658090, 2, 0, fffff88000dd583f}
Probably caused by : ataport.SYS ( ataport!IdePortTickHandler+f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdePortTickHandler+f
Bugcheck code 000000D1
Arguments fffffa80`0d658090 00000000`00000002 00000000`00000000 fffff880`00dd583f
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[rukh]

I did a HDD check with DOS Seagate Sea Tools, no errors.
I did a memtest, no errors. Screenshot in attachment.
I stressed for 15-20 min my graphics card with FurMark and memory test from here https://simtk.org/home/memtest simultaneously, memory was loaded at 80%, GPU at 100%, temperature was at about 80 degree Celsius (~180F) no artifacts and no crashes. Video was emitting a weird sound, some kind of constant beep, but it was running smoothly on the screen. Both fans on the video card were working.

I will try to stress the CPU in next couple of days.

One thing I have noticed that my CD-ROM is disappearing from time to time from windows and bios I suppose. Maybe it is disconnecting in runtime causing crashes?

 

[usasma]

Disconnect the CD-ROM (both cables) and see if that stops the BSOD's
Disconnect the cable that goes from the mobo to the CD-ROM drive from the mobo also.

 

[rukh]

Unfortunately after disconnecting the cd-rom it crashed again. Dump from this crash is in the attached zip.

 

[usasma]

If you are using some sort of cleaning tool on your system, please don't use it while we're troubleshooting - it removes needed files.

Video was emitting a weird sound,

This isn't normal behavior. Did your speakers emit the sound, or was it coming directly from the video card? I'd either try more video stress tests, or try another video card. I've had experience with an OEM nVidia card that reported normal temps - but burnt my fingers when I was poking around in the case. That's where I learned the house fan trick (but it's not appropriate for you at this time).

We're looking for clues here, and the weird sound is the only strange thing that we've found. We've also seen video problems in the BSOD's - so the video card is the most likely problem.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\082511-22198-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Aug 25 16:20:08.488 2011 (UTC - 4:00)
System Uptime: 0 days 4:54:14.705
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`000cdfc9 00000000`00000002 00000000`000cdfc5
BiosVersion = P1.90
BiosReleaseDate = 07/04/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[rukh]

If you are using some sort of cleaning tool on your system, please don't use it while we're troubleshooting - it removes needed files.

I am not using any cleanup tool right now. If you are talking about minidumps I have moved them into other location because there are like 30 of them right now. I did previously posted them so I wanted to just add the new minidump that was available.

This isn't normal behavior. Did your speakers emit the sound, or was it coming directly from the video card?

It was most certainly coming directly from the video card. I will try to stress it more, or just maybe ask for a replacement.

 

[usasma]

Not a problem with the minidumps - it's just that I often see extra minidumps that the poster hasn't noticed, so I check the older one's to ensure that I've run everything.

I've heard screeching from video cards before - most often from the fan. What this usually means to me is that there is a problem with the fan - and that it may stay running for a while and then seize up intermittently (causing the card to overheat). Also, if the card screeches, it's not normal - so the card is to blame.

If you're technically able to repair the fan and cooler, give that a try. Otherwise it's time to try another video card.

 

[rukh]

I have attached results from video memory stress test (http://nvworld.ru/utilities/vmt/), looks like this is the case. We can rely on results from this tool?

 

[usasma]

Yep, the VMT test found a pile of errors. Interestingly, it didin't find them in every resolution that it tested.
It'd be interesting to run the test several times to comparer results (to see if the resolutions that tested OK will stay OD).

So, it's time to try a new video card - BUT - purchase one that you can return for a refund, just in case this isn't the actual problem. It's most likely that this is the video card, but other problems can occasionally cause test failures.

Good luck!

 

[rukh]

I did run the tests several times more, the results were different in almost all of them. Then I did pull out the video card, cleaned the card where it goes into the socket, switched one 12V cable with a replacement 2x molex -> 1x 12V. Then I did run some tests and whats interesting two 7 hour memory tests had no memory errors at all.

I don't know what does that mean? Mobo failure? The graphics card was running in my former PC for 3 or 4 months without any errors and yet we are getting crashes from it but not directly, we get errors from memory tests but not always.. I really don't get it :/

EDIT: newest minidump in attachment.