BSOD when computer initializes

ClassyCanadian · 24 Jul 2011

Hi guys,

Recently I've been getting odd BSOD on my machine. When I turn off my machine (or put it to sleep mode) for about 6+ hours, usually overnight, it sometimes get BSOD when it starts up. If this happens, I usually turn off my computer by holding the power button and trying again. After maybe 2-3 tries, it will work fine and properly again.

I was wondering if anyone knows what the problem might be?

usasma · 25 Jul 2011

perfmon shows disabled/malfunctioning devices. Are any of these deliberate?

Ethernet adapter is disabled (x2) If this is a USB device, please enable the device, uninstall the software, then remove the device from your system.
LogMeIn is having configuration issues. Uninstall it.
2 network services are abnormally stopped (? due to disabled devices ?)

Here's the problem devices from msinfo32:

Broadcom 802.11n Network Adapter PCI\VEN_14E4&DEV_4329&SUBSYS_00601737&REV_01\4&278CCF74&0&08F0 This device is disabled.

LogMeIn Kernel Information Provider ROOT\LEGACY_LMIINFO\0000 This device is not present, is not working properly, or does not have all its drivers installed.

Daemon Tools is also present. It's sptd.sys driver is a known cause of BSOD's in Win7 systems. Please uninstall the program and then use this free tool to ensure that the sptd.sys driver is removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

If that doesn't fix things, my next suspicion would be malware. Here's a link to various free antimalware scans: Free Online AntiMalware Resources

OLDER 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 update these 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:


LMouFilt.Sys        Tue Aug 24 13:21:43 2010 (4C73FFA7)
vmbus.sys           Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys           Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA) - update through Windows Update
LHidFilt.Sys        Tue Aug 24 13:21:36 2010 (4C73FFA0)
atikmpag.sys        Thu Nov 25 21:16:47 2010 (4CEF188F)
seehcri.sys         Wed Jan 09 03:41:35 2008 (478488BF)
atikmdag.sys        Thu Nov 25 21:46:44 2010 (4CEF1F94)
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
Rt64win7.sys        Thu Feb 26 04:04:13 2009 (49A65B0D)
GEARAspiWDM.sys     Mon May 18 08:17:04 2009 (4A1151C0)
lmimirr.sys         Tue Apr 10 18:32:45 2007 (461C108D)
AtihdW76.sys        Wed Nov 17 07:02:04 2010 (4CE3C43C)
xusb21.sys          Thu Aug 13 18:10:17 2009 (4A848F49)
cpuz135_x64.sys     Tue Nov 09 08:33:36 2010 (4CD94DB0)
LMIRfsDriver.sys    Mon Jul 14 12:26:56 2008 (487B7E50)
avipbb.sys          Tue Jun 14 09:57:13 2011 (4DF768B9)
VBoxNetFlt.sys      Thu Feb 17 11:21:06 2011 (4D5D4AF2)

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072311-9921-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 23 21:49:55.961 2011 (UTC - 4:00)
System Uptime: 4 days 15:16:20.351
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7a_c00000c0
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  avguard.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
Bugcheck code 0000007A
Arguments fffff6fc`40009908 ffffffff`c00000c0 00000000`78cb0860 fffff880`01321c08
BiosVersion = FB 
BiosReleaseDate = 05/04/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3331
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\071411-9297-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070911-8174-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul  9 16:52:59.517 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:14.017
BugCheck F4, {3, fffffa800503ab30, fffffa800503ae10, fffff8000218df40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0503ab30 fffffa80`0503ae10 fffff800`0218df40
BiosVersion = FB 
BiosReleaseDate = 05/04/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3330
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070311-8548-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul  3 20:46:35.694 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.194
Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x74
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a
Bugcheck code 00000074
Arguments 00000000`00000002 fffff880`051fab20 00000000`00000002 ffffffff`c000014d
CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3331
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070311-8252-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul  3 17:07:50.155 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:40.655
BugCheck F4, {3, fffffa80050ddb30, fffffa80050dde10, fffff8000219df40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`050ddb30 fffffa80`050dde10 fffff800`0219df40
BiosVersion = FB 
BiosReleaseDate = 05/04/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3331
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ClassyCanadian · 25 Jul 2011

Thanks a bunch usasma! I'll give these a try as soon as I get home.

ClassyCanadian · 25 Jul 2011

I have removed the Broadcom driver and unplugged it from the PCI slot of my PC. I also have removed Daemon Tools as well.

As for LogMeIn, I don't even have it installed. I re-downloaded it from the website, installed it and then uninstalled it. I was wondering if this will properly remove it?

usasma · 26 Jul 2011

Great work! Yes, that should remove it. But you can go to C:\Windows\System32\drivers and look for them there.
DON'T delete them from there if you do find them.

The procedure that I recommend is:
- set a System Restore Point (in case the system won't boot due to the work we're doing)
- make sure you have a bootable System Repair disk/installation disk (so you can perform System Repair)
- rename the LogMeIn drivers from .sys to .BAK
- reboot and check to be sure that the drivers don't reinstall themselves
If unable to boot, use Startup Repair to access System Restore - and restore the system using the restore point that you set in the first step.

ClassyCanadian · 26 Jul 2011

Thanks!

Also, I have noticed that most of the drivers on that list says that the reference info is "Windows Update". How would I update the driver if it is like so?

usasma · 26 Jul 2011

When it says Windows Update all you have to do is visit Windows Update and get all updates.
If they don't update, then Windows doesn't have an update for them (in other words, they're good the way that they are).

Just FYI, there is a 0driver named secdrv.sys that's updated through Windows Update - and it's dated from 2006. So it'll always show up as needing an updated (since we routinely highlight anything from 2007 and earlier). But that's the most recent version of the driver, so it'll never get any newer. This is, in short, because we scan for driver dates rather than driver versions.

ClassyCanadian · 15 Aug 2011

Hi guys,

I haven't had the problem for a while and then today, as I was starting my machine from sleep mode, I got a BSOD again!

I have attached all of the files that are required.

Thanks!

usasma · 16 Aug 2011

Have you been using a system cleaner such as CCleaner? If so, please customize the actions so that it leaves event logs and dump files on the computer. Also, please don't let it clean the registry as that can cause more problems in the long run.

This BSOD points to an error with your disk hardware. We have seen a lot of hard drive issues (although not this exact one) with SSD's, so I have to wonder about the SSD in your system. Because of the number of issues that we've seen, I'm holding off on getting an SSD until the technology matures further (likely after Win8 comes out).

There's not a whole bunch available to test SSD's. Here's what I suggest:
- Update the SSD's firmware to the latest available version
- 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)
- 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.

For your motherboard, you can get the Intel chipset drivers from Intel ( http://downloadcenter.intel.com )
You have 2 or 3 different storage controllers (I'm not sure if the Gigabyte one is an actual device or not) - so it depends on which one the SSD is connected to (but it's probably safer/better to update them all - in case of conflicts).
Intel storage controller: http://downloadcenter.intel.com
Gigabyte storage controller: GIGABYTE - Motherboard - Socket 1366 - GA-X58A-UD3R (rev. 2.0)
Marvel storage controller: Marvell - Support

Please update/remove these older drivers - I'm particularly concerned with the Blackberry and Sony Ericsson phone drivers that date from 2008:
OLDER 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 update these 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:


vmbus.sys           Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys           Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmpag.sys        Thu Nov 25 21:16:47 2010 (4CEF188F)
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
seehcri.sys         Wed Jan 09 03:41:35 2008 (478488BF)
GEARAspiWDM.sys     Mon May 18 08:17:04 2009 (4A1151C0)
atikmdag.sys        Thu Nov 25 21:46:44 2010 (4CEF1F94)
AtihdW76.sys        Wed Nov 17 07:02:04 2010 (4CE3C43C)
xusb21.sys          Thu Aug 13 18:10:17 2009 (4A848F49)
cpuz135_x64.sys     Tue Nov 09 08:33:36 2010 (4CD94DB0)
Rt64win7.sys        Thu Feb 26 04:04:13 2009 (49A65B0D)

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\081511-9765-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Aug 15 18:35:15.929 2011 (UTC - 4:00)
System Uptime: 1 days 8:15:27.429
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000000e
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  avguard.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
Bugcheck code 0000007A
Arguments fffff6fc`400097e8 ffffffff`c000000e 00000000`b8f5a860 fffff880`012fdc08
BiosVersion = FB 
BiosReleaseDate = 05/04/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3331
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``