Windows 7: BSOD at random intervals

bpierce · 21 Feb 2012

Hi....I custom built my system using a copy of Windows 7 Ultimate purchased from Purdue University. It is an upgrade copy.

I have recently been having unexpected shutdowns, which I initially thought were from downloading large files, but I just had one where I wasn't downloading any large file. I just had my two email programs up (Outlook 2007 & Thunderbird)

Below you will find some info about my system. Please let me know if you need more info. Thank you for your time and consideration.

Manufacturer/Model Number Custom Build
OS Windows 7 Ultimate SP1 64-bit
CPU Intel Core i7 860 @ 2.8GHz
Motherboard Asus P7P55D Pro
Memory Patriot 1600EL Series 16GB running XMP-1600
Graphics Card(s) NVidia GeForce 9600 GT 1GB Memory
Sound Card Integrated into MB
Monitor(s) Displays Asus 19" VH198T
Screen Resolution 1440 x 900
Hard Drives ST31000528AS (two)
ST31500341AS (two)
total of 4 physical, but 6 logical
PSU OCZ Stealth X Stream 700Watt
Case Antec Three Hundred
Cooling 4 120mm fans + 140mm top fan

writhziden · 23 Feb 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\bpierce\Windows_NT6_BSOD_jcgriff2\022112-24928-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03252000 PsLoadedModuleList = 0xfffff800`03497670
Debug session time: Tue Feb 21 19:39:25.602 2012 (UTC - 7:00)
System Uptime: 0 days 10:39:10.492
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a5, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  
ñÌ

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800121a1d5 to fffff800032cec40

STACK_TEXT:  
fffff880`099ce6b8 fffff880`0121a1d5 : 00000000`00000024 00000000`000c08a5 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`099ce6c0 fffff880`01219e28 : 00000001`00000000 00000000`00000000 00000000`00000000 00000004`90000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`099ce7c0 fffff880`010d1bcf : fffffa80`0ce69fb0 fffffa80`0ce69af0 fffffa80`0d4e3a70 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x8ba9
fffff880`099ce870 fffff880`010d06df : fffffa80`0efb66d0 fffffa80`0d58db01 fffffa80`0efb6600 fffffa80`0ce69af0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`099ce900 fffff800`032f6bc5 : fffffa80`0ce69b10 fffffa80`0f7328b0 fffffa80`0ec98330 fffff880`009b2180 : fltmgr!FltpDispatch+0xcf
fffff880`099ce960 fffff800`032f6699 : 00000000`00000001 00000000`00000001 fffffa80`0ec98270 fffffa80`0ec98270 : nt!IoPageRead+0x255
fffff880`099ce9f0 fffff800`032dd02a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`00001008 : nt!MiIssueHardFault+0x255
fffff880`099ceac0 fffff800`032ccd6e : 00000000`00000001 00000000`00202000 00000000`77782501 00000000`00000000 : nt!MmAccessFault+0x146a
fffff880`099cec20 00000000`776a2f4e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0012e078 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776a2f4e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`0121a1d5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

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

Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

bpierce · 26 Feb 2012

Hi....

I am in the process of scanning my hard drives for errors. Currently, all have pasted, except the H drive, which is a partition of the C drive. It has come back with the error "The disk does not have enough space to replace bad cluster" I am going to rescan again, and very possible clone this disc to a new one, as this sounds like it might be a rather serious error or do you think that since the H drive and C drive are both one physical drive, should I just rebuild from scratch? I have not done the memory scan yet, but plan to this week. Will post the result of the scan once completed again. Any input would be most helpful. Thanks!

writhziden · 26 Feb 2012

Definitely sounds like a possibly bad drive. Backup your data as you said. Then use the HD Diagnostic site as a reference to help find your hard disk manufacturer and the manufacturer's diagnostic tools.

bpierce · 27 Feb 2012

Again, thanks for your help....

Please pay particular attention to the files corresponding to the C and H drives, as these are one physical drive divided into two logical drives. Any insight will be helpful. Also, this is a ST31500341AS Sata HDD

Thank you.

writhziden · 27 Feb 2012

How have you been shutting down the computer?

You have very strange hard disk behavior that is often attributed to hard shut downs causing the drive to stop unexpectedly.

How is the system currently running? Let us know if you need any further troubleshooting.

bpierce · 20 Mar 2012

Thank you to all who have helped me on this issue. It turns out that it was bad memory. I pulled all sticks of memory and went back to my original 8GB and have since been as solid as a rock. No more errors of any kind.

Again, thank you!

writhziden · 20 Mar 2012

You're welcome. Glad you found the solution.

Windows 7: BSOD at random intervals

BSOD at random intervals problems?