Screen freezes and then eventually BSOD

LazyElemental · Feb 11, 2013

Started a couple of days ago, the computer will stop responding and the mouse will still be able to move. Some programs can even be interacted with but windows will eventually crash which leads to a black screen then BSOD or just BSOD.
I have tried bypassing my video card but the problem persists on built in graphics. My computer will usually work for ~45 minutes before it crashes.

OS - Windows 7
x64
Windows 7 has always been the OS
Purchased the disk separately and installed on the computer myself
· Age of system (hardware) ~1.5 years, video card is ~3 years
· Age of OS installation - have you re-installed the OS? 1.5 years

· CPU i5-2400
· Video Card -Geforce 260
· MotherBoard Z68X-UD3H-B3
· Power Supply - brand & wattage Cooler Master 600W

· System Manufacturer Self built
· Exact model number (if laptop, check label on bottom) Self built.

CPU temps have been stable around 25 C

Ran the windows memory diagnostic twice and it didn't come up with any thing. Ran disk check on my windows drive and it didn't come up with any problems either. Also tried disconnecting my video card to reduce the strain on the power supply and that didn't work. Also booted into safe mode + networking and still had the same issue.

I have included the jcgriff2 file and perfmon in the .zip, I have several network drivers from hamachi, tunggle and comodo but I've had them for awhile and disabled them after this problem started happening.

I will be running verifier and cpu diagnostics while awaiting a reply!

Thanks

LazyElemental · Feb 11, 2013

BSOD on boot with verifier active, attached the minidump files and restoring using the file i just created.

writhziden · Feb 12, 2013

Recommendations:

Crashes point to your Gigabyte utilities, specifically gdrv.sys:

gdrv.sys Thu Mar 12 21:22:29 2009 (49B9D175)
Gigabyte Easy Saver - mobo power utility driver
http://www.carrona.org/drivers/driver.php?id=gdrv.sys

First, disable Verifier:

Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

Code:

verifier /reset

-> Restart your computer.

I would recommend removing all Gigabyte utilities and updating the drivers listed below in red. The USB charging software from Gigabyte also needs to be removed. It places the USB ports in an unintended power state that can lead to instability on the system.

AppleCharger.sys Mon Jan 10 02:57:29 2011 (4D2AD809)
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge
May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys

Outdated and Problematic Drivers:

You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers.

SiWinAcc.sys Mon Nov 1 13:23:29 2004 (41868D31)
Silicon Image driver - comes with package for the SIxxxx drivers
http://www.carrona.org/drivers/driver.php?id=SiWinAcc.sys

SiRemFil.sys Wed Oct 18 16:20:39 2006 (4536A8B7)
Silicon Image driver
http://www.carrona.org/drivers/driver.php?id=SiRemFil.sys

lmimirr.sys Tue Apr 10 16:32:45 2007 (461C108D)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=lmimirr.sys

Si3132r5.sys Fri Jun 1 11:08:28 2007 (4660528C)
Silicone Image storage drivers
http://www.carrona.org/drivers/driver.php?id=Si3132r5.sys

RaInfo.sys Fri Jan 4 11:57:14 2008 (477E818A)
LogMeIn/RemotelyAnywhere Kernel Information Provider
http://www.carrona.org/drivers/driver.php?id=RaInfo.sys

LMIRfsDriver.sys Mon Jul 14 10:26:56 2008 (487B7E50)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys

hamachi.sys Thu Feb 19 03:36:41 2009 (499D3639)
LogMeIn Hamachi Virtual network interface driver
http://www.carrona.org/drivers/driver.php?id=hamachi.sys

dtsoftbus01.sys Fri Jan 13 06:45:46 2012 (4F10358A)
Daemon Tools driver
Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if possible.

Uninstall or change a program

Open Device Manager

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

**************************Mon Feb 11 13:06:41.854 2013 (UTC - 7:00)**************************
SiWinAcc.sys                Mon Nov  1 13:23:29 2004 (41868D31)
SiRemFil.sys                Wed Oct 18 16:20:39 2006 (4536A8B7)
lmimirr.sys                 Tue Apr 10 16:32:45 2007 (461C108D)
Si3132r5.sys                Fri Jun  1 11:08:28 2007 (4660528C)
RaInfo.sys                  Fri Jan  4 11:57:14 2008 (477E818A)
LMIRfsDriver.sys            Mon Jul 14 10:26:56 2008 (487B7E50)
hamachi.sys                 Thu Feb 19 03:36:41 2009 (499D3639)
gdrv.sys                    Thu Mar 12 21:22:29 2009 (49B9D175)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
netr28ux.sys                Mon Sep 14 22:36:45 2009 (4AAF19DD)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
HECIx64.sys                 Tue Oct 19 17:33:43 2010 (4CBE2AD7)
AppleCharger.sys            Mon Jan 10 02:57:29 2011 (4D2AD809)
Rt64win7.sys                Thu Jan 13 04:57:19 2011 (4D2EE89F)
SBFWIM.sys                  Tue Feb  8 04:37:58 2011 (4D512B16)
RTKVHD64.sys                Fri Feb 11 03:16:05 2011 (4D550C65)
EtronXHCI.sys               Fri Feb 25 10:51:52 2011 (4D67EC38)
EtronHub3.sys               Fri Feb 25 10:51:55 2011 (4D67EC3B)
speedfan.sys                Fri Mar 18 10:08:46 2011 (4D83838E)
sbtis.sys                   Tue Apr  5 12:12:37 2011 (4D9B5B95)
SbFw.sys                    Tue Apr  5 12:12:59 2011 (4D9B5BAB)
iaStor.sys                  Tue Apr 26 12:06:18 2011 (4DB7099A)
SBREdrv.sys                 Fri Apr 29 09:51:13 2011 (4DBADE71)
sbapifs.sys                 Wed May 11 10:20:27 2011 (4DCAB74B)
dtsoftbus01.sys             Fri Jan 13 06:45:46 2012 (4F10358A)
rzudd.sys                   Fri Aug 17 01:01:22 2012 (502DEC42)
igdkmd64.sys                Wed Dec 12 17:42:26 2012 (50C92472)

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

**************************Mon Feb 11 13:06:41.854 2013 (UTC - 7:00)**************************
Loading Dump File [E:\BSODDmpFiles\LazyElemental\Minidump\021113-11544-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:23.682
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by :gdrv.sys ( gdrv+18f9 )
BugCheck C4, {f6, e0, fffffa8012443b30, fffff880069108f9}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000e0, Handle value being referenced.
Arg3: fffffa8012443b30, Address of the current process.
Arg4: fffff880069108f9, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_gdrv+18f9
CPUID:        "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3073
  BIOS Version                  F3
  BIOS Release Date             05/13/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 11 13:02:10.839 2013 (UTC - 7:00)**************************
Loading Dump File [E:\BSODDmpFiles\LazyElemental\Minidump\021113-11278-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:23.056
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by :gdrv.sys ( gdrv+18f9 )
BugCheck C4, {f6, e0, fffffa8012406930, fffff88003fc98f9}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000e0, Handle value being referenced.
Arg3: fffffa8012406930, Address of the current process.
Arg4: fffff88003fc98f9, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_gdrv+18f9
CPUID:        "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3073
  BIOS Version                  F3
  BIOS Release Date             05/13/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

LazyElemental · Feb 12, 2013

Trying these solutions right now, I will let you know how successful they are.

Vir Gnarus · Feb 12, 2013

Btw, for future reference you should use Memtest86+ instead of the Windows Memory Diagnostic, since the latter tends to be rather poor in detecting faults. Also when doing memory testing you should always let it run several passes over your memory. Again this is just future reference. I personally do not think the symptoms you described nor the information given leads to a RAM issue.

LazyElemental · Feb 12, 2013

I'm sad to report that I'm still having problems. I removed all of the gigabyte utilities using windows add/remove program and uninstalled hamachi and daemon tools. I also updated my BIOS but my computer still locks up and blue screens. I could not figure out what to update too with the silicon image drivers, i think those might be associated with my mobo's firmware? I'm attaching another run of jcgriff2 and perfmon so you can see if anything has changed. Hope this helps!

Thanks for your help so far

writhziden · Feb 12, 2013

You might have mentioned that you have a Crucial M4 SSD...

Does this happen every hour on the hour? If so, it may be that the firmware is out of date, a known problem with the Crucial M4 / Micron MTFDDAK064MAM-1J1 .

M4 customers,

We are aware of an issue that is currently affecting a small number of users whereby their m4 causes their system to require a restart. This issue occurs after approximately 5,000 hours of actual “on time” use. Following the initial reboot, the system then requires subsequent restarts after each additional hour of use. However, the data on the SSD is unaffected and will not be lost due to this condition.

Through our investigation, we have determined the root cause of the problem and will be releasing a firmware update that rectifies the situation. We are currently running through our validation and compatibility process. Once this process is complete, the firmware will be made available to our customers. Although we understand the desire of some people to start using unreleased firmware now, we want to ensure that our solution works across multiple chipsets, systems, and operating systems before publishing the release code. We are currently targeting the week of January 16th, 2012 to publicly release the new firmware update.

We understand the impact that this is having on some users right now and apologize for this inconvenience. We appreciate your continued support, feedback, and patience as we finalize code and resolve this issue.

- BSOD Crucial M4.

SSD Troubleshooting:

The crashes you are receiving are common with SSDs when there are incompatible drivers, hardware, BIOS, or firmware issues. Proceed with SSD troubleshooting:

Make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace only the drive power connection if it is a desktop, (fully reconnect the drive to the system if it is a laptop) and then do steps 4-8 again.
10. Follow steps 1-3 again.
11. Reconnect the drive fully to the system.
12. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
13. Start your computer normally and run Windows.
The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

LazyElemental · Feb 13, 2013

I have updated my SSD drivers per your suggestion, I was not aware that they could be a problem! I had run across vague references to SSD issues but they suggested updating BIOS. I will report back tomorrow.
Thanks again!

LazyElemental · Feb 13, 2013

4 hours in a row, I think updating my SSD drivers fixed it! Thanks a ton guys, I really appreciate your help!

niemiro · Feb 13, 2013

LazyElemental said:
4 hours in a row, I think updating my SSD drivers fixed it! Thanks a ton guys, I really appreciate your help!

Awesome news! I have that same Crucial M4 SSD, it just needs that firmware update to stabalise it :)

Vir Gnarus · Feb 14, 2013

Yah. Just for future reference, firmware and BIOS updates should be the FIRST thing one should do when purchasing an SSD drive. They both work hand-in-hand and are very crucial to determining the stable operation of an SSD.

Search

Search

Screen freezes and then eventually BSOD

LazyElemental

Member

Attachments

LazyElemental

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

LazyElemental

Member

Vir Gnarus

BSOD Kernel Dump Expert

LazyElemental

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

LazyElemental

Member

LazyElemental

Member

niemiro

Senior Administrator, Windows Update Expert

Vir Gnarus

BSOD Kernel Dump Expert