Win7 BSOD "wininit.exe" help

[DougWD]

Here's the crash dump report:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Inaccessible path: 'G:\Temp\Symbols4Debugger'
Symbol search path is: G:\Temp\Symbols4Debugger;srv*
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`0305b000 PsLoadedModuleList = 0xfffff800`032a0670
Debug session time: Mon Dec 5 02:15:27.341 2011 (UTC - 8:00)
System Uptime: 0 days 6:35:50.184
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800ca6a060, fffffa800ca6a340, fffff800033db8b0}

Probably caused by : wininit.exe

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

2: 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: fffffa800ca6a060, Terminating object
Arg3: fffffa800ca6a340, Process image file name
Arg4: fffff800033db8b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800ca6a060

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.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

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`03b6b0e8 fffff800`034625e2 : 00000000`000000f4 00000000`00000003 fffffa80`0ca6a060 fffffa80`0ca6a340 : nt!KeBugCheckEx
fffff880`03b6b0f0 fffff800`0340f99b : ffffffff`ffffffff fffffa80`0ca5b2e0 fffffa80`0ca6a060 fffffa80`0ca6a060 : nt!PspCatchCriticalBreak+0x92
fffff880`03b6b130 fffff800`0338f448 : ffffffff`ffffffff 00000000`00000001 fffffa80`0ca6a060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`03b6b180 fffff800`030d6ed3 : fffffa80`0ca6a060 fffff800`c0000005 fffffa80`0ca5b2e0 00000000`00c40940 : nt!NtTerminateProcess+0xf4
fffff880`03b6b200 fffff800`030d3470 : fffff800`0312367f fffff880`03b6bb78 fffff880`03b6b8d0 fffff880`03b6bc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03b6b398 fffff800`0312367f : fffff880`03b6bb78 fffff880`03b6b8d0 fffff880`03b6bc20 00000000`ff28bce8 : nt!KiServiceLinkage
fffff880`03b6b3a0 fffff800`030d72c2 : fffff880`03b6bb78 00000000`00cc0000 fffff880`03b6bc20 00000000`ff28fa80 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`03b6ba40 fffff800`030d5e3a : 00000000`00000001 00000000`00c40ef8 00000000`00000001 00000000`00cc0000 : nt!KiExceptionDispatch+0xc2
fffff880`03b6bc20 00000000`77a68e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00c40f00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a68e3d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe

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

2: kd> !process fffffa800ca6a060 3
PROCESS fffffa800ca6a060
SessionId: 0 Cid: 0258 Peb: 7fffffd7000 ParentCid: 01c4
DirBase: 2de90d000 ObjectTable: fffff8a001053760 HandleCount: 90.
Image: wininit.exe
VadRoot fffffa800ca6c6b0 Vads 73 Clone 0 Private 761. Modified 11. Locked 2.
DeviceMap fffff8a000008b30
Token fffff8a0014c1060
ElapsedTime 06:35:37.203
UserTime 00:00:00.000
KernelTime 00:00:00.062
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (1700, 50, 345) (6800KB, 200KB, 1380KB)
PeakWorkingSetSize 1700
VirtualSize 49 Mb
PeakVirtualSize 54 Mb
PageFaultCount 1951
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 874

THREAD fffffa800ca6ab60 Cid 0258.025c Teb: 000007fffffde000 Win32Thread: fffff900c00e7c20 WAIT: (UserRequest) UserMode Non-Alertable
fffffa800ca85a20 NotificationEvent

THREAD fffffa800ca5b2e0 Cid 0258.0278 Teb: 000007fffffda000 Win32Thread: 0000000000000000 RUNNING on processor 2
THREAD fffffa800ca9e060 Cid 0258.028c Teb: 000007fffffd5000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Alertable
fffffa800ca9fd80 SynchronizationTimer
fffffa800ca9fef0 SynchronizationTimer
fffffa800ca4ab30 ProcessObject
fffffa800cae0a00 ProcessObject
fffffa800caeeb30 ProcessObject
fffffa800ca9def0 SynchronizationTimer

THREAD fffffa800e780980 Cid 0258.10e8 Teb: 000007fffffdc000 Win32Thread: 0000000000000000 WAIT: (WrQueue) UserMode Alertable
fffffa800ca57900 QueueObject

 

[circaal]

When exactly do you get this probem? The userinit.exe file is usually when you try to log into windows. I would run a HDD scan first off then try a windows repair and see if you get any luck that way.
-BYT

 

[DougWD]

Actually, that was the first one I believe. I was getting them often while working in Win7 x64 with the new nVidia driver, but I uninstalled that and reverted back one version. No more BSODs that point to the nVidia driver. This, however, was the first wininirtexe I have had. I happened when I was working in Win7 x64 and started a program. Everything froze.

I haven't had software BSODs since Win7 came out. My problems started after trying to uninstall Zonelarm Free edition. Never, ever load that program. That may be a coincidence though. I haven't had once since I posted.

What do you think?

 

[heatlesssun]

Do you have System Restore turned on? I know few people have that turned on around here but it's fantastic in situations like this to rollback a problematic install.

 

[DougWD]

Yes I have it on for my system disk, but I'd have to roll back far too much. If I keep having them I'll just re image a clean backup image and them reload my programs. I could reimage back to a place where I know I wasn't having trouble. However, I have made so many changes since then, I'd better better off just re-imaging the system and then reloading my programs for a clean install.

I'll just wait and see if it becomes more unstable. If so, I'll probably run a repair from the repair disk and see if that helps.

One thing I did notice. After I had the BSOD the BIOS wouldn't read my boot disk until I unplugged my pen drive from a USB 3.0 port. I'm wondering if that could have had anything to do with the BSOD in the first place.

 

[heatlesssun]

One thing I did notice. After I had the BSOD the BIOS wouldn't read my boot disk until I unplugged my pen drive from a USB 3.0 port. I'm wondering if that could have had anything to do with the BSOD in the first place.

USB devices and hubs can cause system instability from my experience. I've got around 25 USB devices and hubs plugged into my sig rig and it was kind of tricky getting everything to work and some devices seem to cause issues with system stability when plugged into one hub but not another or plugged directly into a port.

 

[circaal]

I would change your advanced system setting to create a minidump file and download bluescreenview. That way if you get another BSOD with BlueScreenView you can read the BSOD and it will tell you what driver caused the issue. Its a very helpful tool. I use it all the time when I am working with BSOD issues.
-BTY