BSOD when trying to start in Normal Mode

Hi
Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Win7
- an OEM or full retail version? OEM

- What is the age of system (hardware)? About a Year
- What is the age of OS installation (have you re-installed the OS?) A Year
Model- Alienware M14x

A few days ago, i encountered a sudden collapse in my computer system as in I would get BSOD in the form of a very short message that says Fatal Error. I would get BSOD even trying to get into Safe Mode. So I factory reset the computer and kept a backup copy of my C Drive.

It was working fine for a 2 days when this morning, the system refused to boot into normal mode. Safe mode + Networking was all right. The system will continuously churn
out error messages pertaining to the likes of Wermgr or something to that sort, or explorer.exe failing to load or cannot be written to Memory...(I'm sorry i cant be more precise here, If you need me to elaborate more, i can purposely crash my system)

I used BlueScreenViewer and it shows a Critical_Object_Termination as the cause and the driver is Ntoskrnl.exe + 66500.

I apologise for not including a Perfmon/Report. MY system doesn't seem to be able to churn out a report.

Thank you Sirs and Mdms.

F4 bugcheck. Attached dump points to csrss.exe as the culprit, which is more than likely incorrect.

Two things I'd like for you to do:

Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Dump for reference:

Code:

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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032412-24928-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.21094.amd64fre.win7_ldr.111118-2051
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03040ed0
Debug session time: Sat Mar 24 00:21:00.062 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:29.124
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8009053b30, fffffa8009053e10, fffff8000317b020}

Probably caused by : csrss.exe

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

0: 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: fffffa8009053b30, Terminating object
Arg3: fffffa8009053e10, Process image file name
Arg4: fffff8000317b020, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8009053b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`045afac8 fffff800`031ff1f2 : 00000000`000000f4 00000000`00000003 fffffa80`09053b30 fffffa80`09053e10 : nt!KeBugCheckEx
fffff880`045afad0 fffff800`031a9fa3 : ffffffff`ffffffff fffffa80`09097720 fffffa80`09053b30 fffffa80`09053b30 : nt!PspCatchCriticalBreak+0x92
fffff880`045afb10 fffff800`0312c96c : ffffffff`ffffffff 00000000`00000001 fffffa80`09053b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x16ed6
fffff880`045afb60 fffff800`02e71753 : fffffa80`09053b30 fffff880`c0000006 00000000`012bfe50 fffffa80`09097720 : nt!NtTerminateProcess+0x20c
fffff880`045afbe0 00000000`775ff7ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`012bed18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775ff7ba


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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

An Update:

I have ran MemTest and passed 9 times without error. I will now embark on Driver Verifier. Thanks for the help. Will Update once i get something concrete

Sorry but does the Drive Verifier trigger the BSOD while im using safe mode + Networking?

I cant get the Computer to go past the black screen after the welcome screen. Instead of a BSOD, i get a whole bunch of error messages that Wermgr has stopped working...Taskscheduler has stop working...

Thanks a million!

Stellarnight said:

Sorry but does the Drive Verifier trigger the BSOD while im using safe mode + Networking?

No, because the drivers you are telling to be stressed with Driver Verifier are third party drivers, not Microsoft signed drivers. Only the essential non third party drivers are loaded in Safe Mode.

So is there anything else i can do since i cant really enter normal mode?

Are you still having difficulty entering normal mode? Do you have the same troubles if Verifier is disabled (I assume so since the title basically indicates this to be so)?

• 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.

Hello Thanks ePeen and writhziden for responding!

A friend of mine came over and diagnose the problem to be a damaged HDD.
He replaced the HDD and the laptop is now running like a charm:)
Thanks!

No problem. Glad your friend was able to help you find a solution. :) Thanks for posting back.