Occasional BSOD - need help resolving

N9OK · 02 Jun 2013

My homebuilt computer has suffered from periodic BSOD since it was built 3+ years ago. The first few months of its life it was a Linux computer, which suffered from occasional rebooting. Windows 7 ultimate has been installed for the last 3 years, during which time BSOD have been common. There have been 3 periods of time recently where they have been more frequent.

1) My CPU fan died and I didn't catch it, resulting in very frequent BSOD. After I replaced the fan and started running Core Temp 1.0 RC4 and continuously logging fan temps, BSOD occurrence dropped dramatically. This was Jan or Feb 2013.

2) I implemented a periodic disk defragment using MyDefrag. BSOD were a frequent occurrence during the nightly defrags. BSOD occurrence dropped dramatically after deactivating these defrags. This was Feb or March this year.

3) I had a BSOD yesterday. It happened right after I woke the computer, as I was typing a URL into Chrome, first thing in the AM.

Thinking back, many of the BSOD occur as the computer is waking up. The exception is when I was running MyDefrag; I would frequently find the computer crashed during the night.

Any assistance in troubleshooting this would be appreciated. I have other Windows computers which have never BSOD, so I think it's reasonable to expect to be able to operate crash free.

Arc · 02 Jun 2013

Hello N9OK. Update your display driver. Install the latest WHQL only. Go to Drivers - Download NVIDIA Drivers, Download 320.18 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Some other issue is there, as it appears. It would be better if you upload your MSINFO32.nfo file.

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

N9OK · 02 Jun 2013

Arc, thanks for your reply. I updated the graphics driver, as you suggested, to 320.18 WHQL. MSINFO32 has been uploaded. Awaiting further instructions...

Thanks again,

Joe N9OK

Arc · 03 Jun 2013

Here I am waiting for your results, or any further BSOD :)

Will analyze the subsequent dumps comparing with this file.

N9OK · 03 Jun 2013

That's funny!

OK, so assuming that another BSOD happens, I will upload the output from the SF_Diagnostic_Tool as well as the output from MSINFO32 again. Correct? Anything else I should plan on doing?

Thank you very much.

Joe N9OK

Arc · 04 Jun 2013

Apparently not :)

If updating the display driver is able to run the computer good, let it run. For any further issue, we are here :)

N9OK · 09 Jun 2013

Another BSOD occured. My son logged into his account on my PC to play "Tribes Ascend". He made several video setting changes in the game. When he was done, he logged out of Windows. The BSOD occurred as he was logging out. The files are attached. Thanks again for your assistance in getting to the bottom of this.

Arc · 09 Jun 2013

Hello N9OK.

Uninstall Virtual CloneDrive. It may cause such issues, as experienced previously.

You have only one HDD, so RAID is not necessary for you. Disable AMD RAID Console. Also Disable RAID in BIOS.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Turn off Link State Power Management.
PCIe Link State Power Management - Turn On or Off in Windows

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.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus (you may keep Fences too).
Apply > OK
Accept then restart.

Let us know the results.
____________________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 17fe47, 2, 1f145}

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

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000017fe47, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000001f145, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003165a0c to fffff800030d6c00

STACK_TEXT:  
fffff880`0c16cf58 fffff800`03165a0c : 00000000`0000004e 00000000`00000099 00000000`0017fe47 00000000`00000002 : nt!KeBugCheckEx
fffff880`0c16cf60 fffff800`03082ed0 : 00000000`00000000 fffff680`00003360 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0c16cfa0 fffff800`030a67a3 : fffffa80`0ab669f0 fffff700`00003863 0000007f`fffffff8 fffff8a0`2a802be0 : nt! ?? ::FNODOBFM::`string'+0x32418
fffff880`0c16d030 fffff800`030a7872 : fffffa80`0ab669f0 fffffa80`00000000 fffff880`00001685 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0c16d8e0 fffff800`033accba : fffff8a0`1cb56a90 fffff880`0c16dc20 00000000`00000000 fffffa80`0ab68060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0c16d930 fffff800`03392dbd : 00000000`00000000 00000000`00000001 00000000`7ef6e000 fffffa80`0a8e5970 : nt!PspExitThread+0x56a
fffff880`0c16da30 fffff800`030c971a : 00000000`00000100 fffffa80`0ab68120 00000000`00000001 fffff800`030cc81d : nt!PsExitSpecialApc+0x1d
fffff880`0c16da60 fffff800`030c9a60 : 00000000`00000246 fffff880`0c16dae0 fffff800`03392d30 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0c16dae0 fffff800`030d5f37 : fffffa80`0ab68060 00000000`000002c4 00000000`00000000 fffffa80`09c87250 : nt!KiInitiateUserApc+0x70
fffff880`0c16dc20 00000000`72a92e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0577ec58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72a92e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`03165a0c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

N9OK · 10 Jun 2013

Ok, so I ran the RAM test, the Graphics Card stress test per the instructions, and no problems showed up at all. I turned off Link State Power Management. I do indeed have 2 hard drives, and the BIOS sees both of them, and reports both as healthy, but the hardware RAID on the Motherboard must hide that fact from Windows.

I strongly believe that the cause of the BSOD on my PC is hardware based, since I also had problems when Linux was installed on this computer. The BSOD always seem to occur when the PC is transitioning from Sleep mode to awake mode. Are there any automated tests that test the various components of power saving / sleep mode? If those modes could be exercised then maybe the problem would happen more frequently.

Thank you again for working with me on this.

Joe N9OK

Arc · 10 Jun 2013

Apparently there is no such test.

How is it running now? Is it still BSODing when putting to sleep or wake up? If so, supply the latest zip too.