BSOD when idle and under general use

EDG3 94 · 04 Feb 2012

Hi ive been having real problems with BSOD even when my computer is left alone, i have already reinstalled windows 7 home premium 64bit and the BSOD has kept on happening, i have updated all my drivers to the most recent versions to the best of my knowledge. I built the system myself and i really need some help i have tried everything i know of.

Ive attached the files the sticky says to, so hopefully someone can help

Thanks

usasma · 04 Feb 2012

10 memory dumps today! Wow!

Only 62 updates since SP1 - most systems have more than 70. Please visit Windows Update and get all available updates.

We've seen a number of BSOD issues with SSD's recently. Here's the information that I've compiled:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

System is slightly overclocked (100 mHz). If this is the result of a "turbo" setting, or some other overclocking device, please stop using it. Some of these devices have been known to have BSOD issues.

Other than that, I'd have to suggest running Driver Verifier to try and pin down the cause. Please run Driver Verifier according to these directions: Driver Verifier Settings If it BSOD's fairly quickly, let it happen 2 or 3 times before gathering the memory dumps and uploading them.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


jraid.sys         Thu May 19 03:55:18 2011 (4DD4CCE6)
AiChargerPlus.sys Mon Nov 08 01:48:26 2010 (4CD79D3A)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
mv91xx.sys        Fri Aug 27 05:49:22 2010 (4C778A22)
mvxxmm.sys        Wed Oct 12 01:44:06 2011 (4E952926)
mvs91xx.sys       Wed Oct 12 01:44:21 2011 (4E952935)
aswSnx.SYS        Mon Nov 28 12:54:05 2011 (4ED3CABD)
aswTdi.SYS        Mon Nov 28 12:52:18 2011 (4ED3CA52)
aswRdr.SYS        Mon Nov 28 12:52:20 2011 (4ED3CA54)
ICCWDT.sys        Wed Aug 18 04:27:45 2010 (4C6B9981)
aswSP.SYS         Mon Nov 28 12:53:57 2011 (4ED3CAB5)
AsUpIO.sys        Mon Aug 02 22:47:59 2010 (4C57835F)
AsIO.sys          Mon Aug 23 21:53:02 2010 (4C7325FE)
e1c62x64.sys      Wed Jan 11 15:30:54 2012 (4F0DF17E)
asmtxhci.sys      Tue Nov 22 02:09:18 2011 (4ECB4A9E)
SaiBus.sys        Mon Jan 23 12:29:11 2012 (4F1D98E7)
btath_bus.sys     Tue Jul 19 22:59:56 2011 (4E2644AC)
SaiMini.sys       Mon Jan 23 12:29:11 2012 (4F1D98E7)
nvhda64v.sys      Thu Jul 07 12:21:14 2011 (4E15DCFA)
SaiK0728.sys      Fri Jan 18 13:28:04 2008 (4790EFB4)
SaiK0CFA.sys      Mon Sep 19 08:41:43 2011 (4E773887)
btfilter.sys      Sun Oct 23 23:37:08 2011 (4EA4DD64)
SaiU0CFA.sys      Mon Sep 19 08:41:38 2011 (4E773882)
RTKVHD64.sys      Tue Dec 13 05:24:54 2011 (4EE727F6)
asmthub3.sys      Tue Nov 22 02:09:29 2011 (4ECB4AA9)
ASUSFILTER.sys    Tue Sep 20 11:46:33 2011 (4E78B559)
aswMonFlt.sys     Mon Nov 28 12:52:10 2011 (4ED3CA4A)
aswFsBlk.SYS      Mon Nov 28 12:51:52 2011 (4ED3CA38)
btath_rcp.sys     Thu Aug 25 06:26:33 2011 (4E562359)
btath_avdt.sys    Wed Oct 19 01:50:49 2011 (4E9E6539)
btath_a2dp.sys    Wed Oct 19 01:50:36 2011 (4E9E652C)
btath_hcrp.sys    Tue Jul 19 22:59:43 2011 (4E26449F)
btath_flt.sys     Tue Jul 19 22:59:52 2011 (4E2644A8)
btath_lwflt.sys   Wed Oct 19 01:50:44 2011 (4E9E6534)
IOMap64.sys       Thu Feb 04 20:55:34 2010 (4B6B7A96)
HECIx64.sys       Wed Nov 09 19:52:25 2011 (4EBB2049)
nvlddmkm.sys      Sat Oct 15 02:07:55 2011 (4E99233B)
mvxxmm.sys        Fri Aug 27 05:49:03 2010 (4C778A0F)
jraid.sys         Tue Aug 10 05:28:44 2010 (4C611BCC)
btath_bus.sys     Thu Jun 24 02:17:43 2010 (4C22F887)
asmtxhci.sys      Wed Sep 14 03:36:09 2011 (4E705969)
RTKVHD64.sys      Tue Nov 23 05:14:08 2010 (4CEB93F0)
asmthub3.sys      Wed Sep 14 03:36:19 2011 (4E705973)
btfilter.sys      Tue Mar 08 01:15:22 2011 (4D75C97A)
btath_hcrp.sys    Tue Jun 29 05:30:43 2010 (4C29BD43)
btath_a2dp.sys    Mon Feb 14 20:47:47 2011 (4D59DB43)
btath_flt.sys     Thu Jun 24 02:17:38 2010 (4C22F882)
btath_lwflt.sys   Mon Sep 13 04:26:54 2010 (4C8DE04E)
btath_rcp.sys     Thu Jun 24 02:17:21 2010 (4C22F871)
e1c62x64.sys      Tue Sep 21 17:34:15 2010 (4C9924D7)
HECIx64.sys       Tue Oct 19 19:33:43 2010 (4CBE2AD7)
nvhda64v.sys      Tue Jan 17 07:45:46 2012 (4F156D7A)
nvlddmkm.sys      Thu Jan 26 05:19:23 2012 (4F2128AB)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-6396-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 12:02:18.201 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:41.028
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-6739-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 11:59:59.951 2012 (UTC - 5:00)
System Uptime: 0 days 0:08:02.779
Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+20a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpQueueIoCompletionPort+20a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030ab52a fffff880`09bcbc30 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-6052-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 09:08:43.283 2012 (UTC - 5:00)
System Uptime: 0 days 0:02:28.110
Probably caused by : ntkrnlmp.exe ( nt!RtlEqualUnicodeString+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wininit.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlEqualUnicodeString+26
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`033ce676 fffff880`03efcb00 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-5444-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 05:53:46.595 2012 (UTC - 5:00)
System Uptime: 0 days 0:20:42.797
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-5569-02.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 05:08:16.698 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:08.900
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+10a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KeReleaseSemaphore+10a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030ecd5a fffff880`096add00 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-4851-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 05:07:00.488 2012 (UTC - 5:00)
System Uptime: 0 days 0:59:32.690
Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+20a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpQueueIoCompletionPort+20a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030b952a fffff880`02bc6c30 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-5506-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 03:54:48.126 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:04.954
Probably caused by : nvlddmkm.sys ( nvlddmkm+23a7dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+23a7dc
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0f4c27dc fffff880`09354d60 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-6084-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 03:48:05.159 2012 (UTC - 5:00)
System Uptime: 0 days 0:23:24.986
Probably caused by : fltmgr.sys ( fltmgr!GetContextFromStreamList+99 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msiexec.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!GetContextFromStreamList+99
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`011b2039 fffff880`08612760 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-5569-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 03:24:02.800 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:09.002
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueue+fe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertQueue+fe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03088d3e fffff880`02c7fe20 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-4914-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 03:23:01.424 2012 (UTC - 5:00)
System Uptime: 0 days 0:03:10.251
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

EDG3 94 · 04 Feb 2012

Thanks for the reply,

I know to many haha, atm my system has been running for nearly 2 and half hours and i havnt had a crash and ive been using it, im putting it down to luck and still anticipating a bsod, so when it does i will look into my ssd and taking it out of my system and reinstalling windows on my hdd, effort but has got to be done.

Then failing that i will run driver verifier and i will look into updating drivers straight after the next crash because if for any reason something i have done in the last couple of hours has fixed the issue i dont want to mess it up haha

Thanks for the reply it will hopefully get me somewhere :)

And on the windows update amount i havnt installed internet explorer 9 i think it is or any subsequent updates for it so that may account for the difference