Freeze, no BSOD while idle, error log attached

[mk11]

All;
Really need some help. Just built this machine a week ago and have a crash out of nowhere about once a day. Most of the time this happens when computer is idle over night. Sleep mode is not active. I have installed the latest GTX 780 driver and not sure what is causing this. Weird things is this is not creating a minidump.
No overclocking.
i4390k
EVGA x79 dark
Ballistix 32GB
Samsung SSD 500
EVGA GeForce GTX780
I have the crash log attached.
Any help would be greatly appreciated.

 

[Arc]

Hi mk11.

All the recent BSODs are caused by Marvell 91xx SATA Controller Driver.

Probably caused by : mvs91xx.sys ( mvs91xx+3b890 )

For further assistance, please upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[mk11]

Thx for your super quick reply. File attached.

 

[Arc]

Uninstall Marvell 91xx SATA 6G Controller from Control Panel> Programs and features.

Then follow Drivers - Clean Left over Files after Uninstalling

Restart the computer, and use it normally.

Let us know how it is going.

 

[mk11]

Great - thx a bunch for your help. Uninstall and driver sweep completed. Will update how it's going.
Happy I found this forum

 

[mk11]

Unfortunately this did not cure the freezes -just had another one. This time just working in browser (chrome), computer just froze again. New SF log attached.

 

[Arc]

No BSOD lately.

Which network connection do you use?

• Intel(R) 82579LM Gigabit Network Connection
• Intel(R) 82574L Gigabit Network Connection

Both are installed, and controlled by the same driver. May it be a conflict there?

The wireless connection, ASUS PCE-N53 300Mbps 11n Dual band Wireless LAN PCI-E Card is old enough.

    Image name: netr28x.sys
    Timestamp:        Fri Oct 28 07:06:43 2011 (4EAA072B)

You need to update the driver; I dont know the download location.

Scan the system for possible virus infection with the following programs. Which Antivirus do you use?

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and display fusion.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[mk11]

I currently use neither one of the network connections, so I uninstalled one - updated the wireless driver, scanned system for viruses - was clean. Using webroot for antivirus. Followed your instructions and cleaned up startup. I did leave one additional file in startup - my autokey script for remapping my keyboard. restarted. Let's see....
Thx again.

 

[mk11]

24hrs no crash so far. Thx again for your help ARC.

 

[Arc]

Give it some more time?

 

[mk11]

OK... Thursday afternoon and only one crash on Monday which I traced back to the automatic reinstall of the network card I manually removed, so appears the LM connection might have been the cause of that issue. Next question now... this network adapter shows up again and again. How can I make sure it does not get installed again? I deleted it in device manager.

Marc

 

[Arc]

Try disabling it?

 

[mk11]

My crashes are back, windows again crashes every night and just crashed again during normal workload a few minutes ago. Attaching crash log.

 

[Arc]

View attachment 290785

The zip you uploaded does not contain any new crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also, make it sure that the Samsung SSD is running with the up to data firmware.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[mk11]

Followed your instructions, no mini-dump - just crashed again. BTW it is not a BSOD, machine just freezes.

 

[Arc]

Followed your instructions, no mini-dump - just crashed again. BTW it is not a BSOD, machine just freezes.

OK, then let us test it elementwise. Drivers first.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[mk11]

Update: Tried to run driver verifier but then get BSOD on startup. Good thing is... we now have a dump file - see attached. One thing I noticed during driver verifier setup... there was still a Marvell driver in there even though I installed it and cleaned it with the sweeper. Running sweeper again does not find any left over divers. What should I do next?

 

[Arc]

Good job on Marvell

Th crash dump indicating to Webroot SecureAnywhere Anti-virus driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {80000003, fffff80002e77a38, fffff8800a92e920, 0}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=WRkrn.sys"]WRkrn.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=WRkrn.sys"]WRkrn.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=WRkrn.sys"]WRkrn.sys [/URL]( WRkrn+3ef3 )

Followup: MachineOwner
---------

In that situation, you need to uninstall WebRoot. You may use CleanWDF.exeavailable here.

Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[mk11]

Done all of the above, found quite a bit of malware and removed. Had several more freezes since then. Just tried to run driver verifier again and windows created a BSOD on boot - attaching dump file.

 

[Arc]

The crash dump that you have uploaded is of 24/10 and is not DV enabled.

If there was malware, better you opt for a clean install; as the deepest searches also sometimes fail to remove the entire infection.