Solved Random BSODs

[TheCratcher]

Hi!

I got a new computer a couple days ago and have been experiencing random BSODs, the computer starts up just fine and can go uninterrupted for a couple of hours but then suddenly just BSODs.

My computer specs are:
MSI Z77A-S01 ATX
Intel Core i5 3570K (Ivy Bridge)
Corsair Vengeance 8GB
EVGA GeForce GTX 560
Windows 7 Home Premium 64bit OEM

If anyone could help me with this I would be most grateful!

 

[HonorGamer]

Hello TheCratcher, Welcome to SF!

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

Please disable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Also looks like possible memory corruption. After you disable driver verifier please run a http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

After please post back results.

-Justin

 

[mgorman87]

Uninstall any MSI programs you have. It appears your MSI update utility is causing some problems. Also, if the computer is brand new and it is already crashing then I would get it exchanged.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul 26 17:40:25.466 2012 (UTC - 4:00)
System Uptime: 0 days 0:12:56.714
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+499 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+499
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 06:37:08.073 2012 (UTC - 4:00)
System Uptime: 0 days 0:35:41.963
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+499 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+499
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 08:49:21.170 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:22.685
*** WARNING: Unable to verify timestamp for amifldrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for amifldrv64.sys
Probably caused by : amifldrv64.sys ( amifldrv64+1d6f )
BUGCHECK_STR:  0xC1_24
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  AEFUWIN64.exe
FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_amifldrv64+1d6f
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 08:27:03.523 2012 (UTC - 4:00)
System Uptime: 0 days 1:10:29.023
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+499 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+499
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 04:59:48.059 2012 (UTC - 4:00)
System Uptime: 0 days 0:18:20.308
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 07:06:55.589 2012 (UTC - 4:00)
System Uptime: 0 days 0:29:29.089
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+499 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  launcher.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+499
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 03:17:58.921 2012 (UTC - 4:00)
System Uptime: 0 days 0:20:50.170
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+115 )
BUGCHECK_STR:  0x1a_8885
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 04:10:21.092 2012 (UTC - 4:00)
System Uptime: 0 days 0:43:47.966
Probably caused by : memory_corruption ( nt!MiInvalidateCollidedIos+198 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiInvalidateCollidedIos+198
BiosReleaseDate = 02/08/2012
SystemManufacturer = MSI
SystemProductName = MS-7752
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[TheCratcher]

So how high are the chances that I'll have to replace the memory?

 

[TheCratcher]

It seems to have fixed itself... I'll leave the thread open for a couple of days just in case.