Random BSOD on Win7 64-bit

[lwrand]

Memtest is reporting that you either have a bad ram module, or, one of the slots on your mobo is bad... Test the ram modules one at a time until you find one that passes, then test that good one in each slot to make sure that you dont have a bad slot in your motherboard ... let us know how it comes out..

Hi Tews,
I have already tested a known good stick alone on all socket with no errors.
Errors come into play when I use them in pair either dual-channel operation or single channel. I had errors with 3 sticks too.

I'm completely out of thoughts...

 

[Tews]

Make sure that the ram you are using is compatible with your motherboard, or RMA the ram..

 

[lwrand]

In attach all dumps (old and new), as always, comments are really appreciated

Make sure that the ram you are using is compatible with your motherboard, or RMA the ram..

Supported: CORSAIR BoxP/N:TW3X4G1333C9DHX

Here is the official list for my Motherboard - Asus Crosshair IV Formula:
http://dlsvr04.asus.com/pub/ASUS/mb/socketAM3/Crosshair_IV_Formula/C4F_Memory_QVL20100726.pdf

I'm going to RMA all sticks, hopefully for the last time...!

 

[lwrand]

Could you please check the dumps ?
Just to be sure there's no evidence of driver causing the BSODs.

Kindly,

 

[Tews]

It still blames memory corruption .. RMA the ram...

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tom\Desktop\Windows_NT6_BSOD_jcgriff2\110710-34850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01a64000 PsLoadedModuleList = 0xfffff800`01ca1e50
Debug session time: Sun Nov  7 07:32:13.607 2010 (UTC - 5:00)
System Uptime: 0 days 1:04:11.106
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 144d11, 2, 144d0e}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

 

[CarlTR6]

There is one out of date driver on your system that is not showing in the driver list of the dump. However, it is showing as an unloaded module. This means it was involved in the crash, but necessarily the cause of the crash.

LVUSBS64.sys Jul 26 2008 - Logitech USB Monitor Filter, Downloads.

I have seen this driver reported as a camera driver also. I do not think there is an update for this driver; but you should certainly try. You can navigate to C:\Windows\System32\Drivers, locate the file and remane it from .sys to .bak. Reboot and the driver will not load. It will probably break your sound. But you can see if your system BSOD's with driver not loading. You can rename it again to .sys to restore it.

 

[lwrand]

Thx Carl, I have renamed the file as .bak and uninstalled the webcam.
In the meanwhile, I have RMA all sticks and I asked a friend to borrow me his rams and motherboard (they are exactly the same, vendor and model of mine).

I installed 3 sticks and I still got 2 reboot on WIN7's login (no BSOD) with DRAM Voltage set to 1.70 V (As raccomended by Asus), than I cleared the CMOS and run the default values on BIOS. And I'm writing here... let's see...

I'm planning to test my friend motherboard, but he told me about an issue with the RAM socket #2 (he is unable to boot with any stick on it, he got BSOD too). Maybe I have the same problem... What a nightmare!

In attach you can find all dumps plus the last two. Thanks again for your time.
Kindly,

 

[zigzag3143]

Thx Carl, I have renamed the file as .bak and uninstalled the webcam.
In the meanwhile, I have RMA all sticks and I asked a friend to borrow me his rams and motherboard (they are exactly the same, vendor and model of mine).

I installed 3 sticks and I still got 2 reboot on WIN7's login (no BSOD) with DRAM Voltage set to 1.70 V (As raccomended by Asus), than I cleared the CMOS and run the default values on BIOS. And I'm writing here... let's see...

I'm planning to test my friend motherboard, but he told me about an issue with the RAM socket #2 (he is unable to boot with any stick on it, he got BSOD too). Maybe I have the same problem... What a nightmare!

In attach you can find all dumps plus the last two. Thanks again for your time.
Kindly,

I am afraid it is still memory (pool_corruption)..would you be running windows Onecare?

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111110-45271-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01a15000 PsLoadedModuleList = 0xfffff800`01c52e50
Debug session time: Wed Nov 10 18:33:45.134 2010 (GMT-5)
System Uptime: 0 days 0:01:12.633
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa800517d480, fffffa800517d480, fffffa800513d480}

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )

Followup: Pool_corruption
---------

 

[lwrand]

I am afraid it is still memory (pool_corruption)..would you be running windows Onecare?

I'm running Windows Security Essentials right now, I don't know OneCare, you mean this one: Windows Live OneCare: home page ?

 

[lwrand]

I have *probably* found the solution. Let's start from the beginning...

First I have cleared the CMOS (on the Asus Crosshair Formula IV, it's quite easy, just press the button on the top-back of your motherboard) and I reinstalled Windows 7.
After that, just run Windows Update until your PC is fully updated with all the "Important" fixes. Then I started to update all the drivers from Asus and Sapphiretech.

On normal reboots the PC keep crashed with all the same BSODs (MEMORY_MANAGMENT, IRQL_NOT_LESS_OR_EQUAL and so on... I saw a KERNAL_EXCEPTION too, involving NTFS.sys) and exactly passed the Windows login screen for three time in a row... until at the fourth reboot, it runs smoothly

So I suspected that the problem could be the voltage on some components and ... I found that my CPU (AMD Phenom II X6 1090t) should be set with 1.45 V (mine was 1.25 as default option under BIOS). I rebooted and updated the option below

Changes on BIOS:
CPU Voltage: 1.45 V (currently I'm running at 1.40 as test)
NB Voltage: 1.20 V
IOMMU: Enabled

And now I'm running with no more crashes also on the first cold boot.
Hope it helps!

 

[CarlTR6]

Thank you very much for the update. That is good news and I hope it stays that way. Since you did a fresh install, don't reinstall any old software that is not Win 7 compatible. Update us a gain in about two or three days and let us know how your system is doing.

 

[lwrand]

In the past three days the system appeared to be really stable.
These are the main changes on BIOS:

CPU Voltage: 1.35 V
NB Voltage: 1.20 V
DRAM Voltage: 1.60 V
IMMOU: Enabled

Motherboard: http://www.asus.it/product.aspx?P_ID=kPGmtxee5RsQVsXG&templete=2
CPU: http://products.amd.com/en-us/Deskt...2=&f3=&f4=&f5=&f6=&f7=&f8=&f9=&f10=&f11=&f12=
DDR3 RAM: http://www.corsair.com/_datasheets/TW3X4G1333C9DHX.pdf

Feel free to update the thread with the [Solved] tag/title. It may helps somebody out there

 

[CarlTR6]

Great news and excellent work. Really happy to hear you are running smoothly. Thank you for updating us with your solution. That may well help another poster.

 

[lwrand]

Sadly, I still have these crashes (BSOD included) as described here:
Unstable System from cold boot and random crashes - The Corsair Support Forums

any thoughts ?

 

[lwrand]

I finally found the solution, after passing 3 months will cold boot BSOD, I just bought new ram sticks (GSKILL F3-16000CL9D-4GBTDD - 8 GB dual channel - coming with their own fan) and the cold boot BSODs are gone! Hope it helps out there,