Windows 7: BSOD that crashes indexes

jpaulino · 17 Mar 2012

Hi,

I have Windows 7 64bits and I have BSOD all the time. I have changed my harddisk a few weeks ago and after install it all, it started again.

Not only I get blue screens but also I got harddisk problems. The chkdsk /f detects erros in the indexes (it deletes some stuff when running) and I have problems starting the harddisk/boot.

In attach I have my the performance monitor html and the Windows_NT6_BSOD_jcgriff2.

I'm really tired about this

Thanks for all the help on this!

jpaulino

zigzag3143 · 17 Mar 2012

No DMPs included in upload try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

jpaulino · 17 Mar 2012

Thanks,

I have followed your steps but it doesn't creates the Minidump folder. Does it creates when the crash occours?

zigzag3143 · 17 Mar 2012

Quote: Originally Posted by jpaulino

Thanks,

I have followed your steps but it doesn't creates the Minidump folder. Does it creates when the crash occours?

Yes it does

jpaulino · 18 Mar 2012

Another BSOD

I got this message:

Quote:

Collecting data for crash dump ...
Initializing disk for crash dump ...

I leave it this way for more then an hour and after that I turned off the computer. But it doesn't created any *.dmp file or the minidump folder.

OMG

zigzag3143 · 18 Mar 2012

Quote: Originally Posted by jpaulino

Another BSOD

I got this message:

Quote:

Collecting data for crash dump ...
Initializing disk for crash dump ...

I leave it this way for more then an hour and after that I turned off the computer. But it doesn't created any *.dmp file or the minidump folder.

OMG

Evidently it is crashing before the service to write the DMP is launched. Please run a system file check.

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

jpaulino · 04 Apr 2012

I'm sorry for the delay, but now I have a new harddisk, a fresh instalation of windows 7, and a BSOD again

Here's the information that I got when the system restarts:

Quote:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2070

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8005A7A060
BCP3: FFFFFA8005A7A340
BCP4: FFFFF80002DCE5F0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040412-15140-01.dmp
C:\Users\JorgePaulino\AppData\Local\Temp\WER-29468-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

And in attached the dump file.

Thanks for any help on this!

writhziden · 05 Apr 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\jpaulino\040412-15140-01\040412-15140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c93650
Debug session time: Wed Apr  4 09:35:33.333 2012 (UTC - 6:00)
System Uptime: 0 days 0:29:23.005
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005a7a060, fffffa8005a7a340, fffff80002dce5f0}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005a7a060, Terminating object
Arg3: fffffa8005a7a340, Process image file name
Arg4: fffff80002dce5f0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8005a7a060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07ce3468 fffff800`02e557b2 : 00000000`000000f4 00000000`00000003 fffffa80`05a7a060 fffffa80`05a7a340 : nt!KeBugCheckEx
fffff880`07ce3470 fffff800`02e02c9b : ffffffff`ffffffff fffffa80`03d61060 fffffa80`05a7a060 fffffa80`05a7a060 : nt!PspCatchCriticalBreak+0x92
fffff880`07ce34b0 fffff800`02d82094 : ffffffff`ffffffff 00000000`00000001 fffffa80`05a7a060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`07ce3500 fffff800`02acafd3 : fffffa80`05a7a060 fffff800`c0000005 fffffa80`03d61060 00000000`03240960 : nt!NtTerminateProcess+0xf4
fffff880`07ce3580 fffff800`02ac7570 : fffff800`02b16aff fffff880`07ce3ef8 fffff880`07ce3c50 fffff880`07ce3fa0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07ce3718 fffff800`02b16aff : fffff880`07ce3ef8 fffff880`07ce3c50 fffff880`07ce3fa0 00000000`032421a0 : nt!KiServiceLinkage
fffff880`07ce3720 fffff800`02acb3c2 : fffff880`07ce3ef8 00000000`0002cfc3 fffff880`07ce3fa0 00000000`03241c78 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`07ce3dc0 fffff800`02ac9f3a : 00000000`00000001 00000000`03240f18 00000000`03242101 00000000`0002cfc3 : nt!KiExceptionDispatch+0xc2
fffff880`07ce3fa0 00000000`77b88e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`03240f20 fffff800`02ac3310 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b88e3d
fffff880`07ce4380 fffff880`07ce4978 : fffff900`c2702a60 fffff880`07cd3000 00000000`00000000 00000000`00000001 : nt!KiCallUserMode
fffff880`07ce4388 fffff900`c2702a60 : fffff880`07cd3000 00000000`00000000 00000000`00000001 fffff880`07ce4db0 : 0xfffff880`07ce4978
fffff880`07ce4390 fffff880`07cd3000 : 00000000`00000000 00000000`00000001 fffff880`07ce4db0 00000000`00000000 : 0xfffff900`c2702a60
fffff880`07ce4398 00000000`00000000 : 00000000`00000001 fffff880`07ce4db0 00000000`00000000 00000000`00000000 : 0xfffff880`07cd3000


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

Did you run sfc /scannow as requested by zigzag3143?

If you are overclocking any hardware, please stop.
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.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Use the short and long tests of SeaTools to determine whether the hard disk is failing.

Windows 7: BSOD that crashes indexes

BSOD that crashes indexes problems?