BSD Blues

System hasn't BSD on me while running. It BSD's when I boot. Then the only way I can get back in is from recovering an image I have stored. This works in 2 out 3 attempts. But on the next reboot I may have to recover my image again (using MS backup). I have a dmp file that I am going to upload. I don't even know how to open it let alone analyze it. Maybe some one can point me to the problem. Right now I suspect my graphics adapter.


Attachment 53763

Well, if you suspect your graphics driver, try updating the drivers.

I can't see real cause. Maybe one of the experts can give a better solution.

Try opening an elevated command prompt and running sfc /scannow. That will scan for bad system files, repairing as necessary.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\021210-46675-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03292e50
Debug session time: Fri Feb 12 18:05:27.213 2010 (GMT-5)
System Uptime: 0 days 0:00:24.322
Loading Kernel Symbols
..........................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6B, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+1331 )

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

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

PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: 0000000000000000, Indicates the NT status code that caused the failure.
Arg2: 0000000000000000, (reserved)
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x6B

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800035f7bc1 to fffff800030c6ed0

STACK_TEXT:  
fffff880`009a9b38 fffff800`035f7bc1 : 00000000`00000000 00000000`00000000 fffff800`00812740 fffff800`00812740 : nt!KeBugCheck
fffff880`009a9b40 fffff800`03548419 : 00000000`00000000 fffffa80`06d31040 00000000`00000080 fffffa80`06caab30 : nt!Phase1InitializationDiscard+0x1331
fffff880`009a9d10 fffff800`0336a166 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`030a5479 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`030a5486 : fffff800`0323fe80 fffffa80`06d31040 fffff800`0324dc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!Phase1InitializationDiscard+1331
fffff800`035f7bc1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!Phase1InitializationDiscard+1331

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+1331

BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+1331

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

I don't suspect the driver I suspect the card itself.

I have run sfc /scannow, I have run the repair disk in the repair mode and memory test mode. I have tried installing previous restore points. I replaced the grapics driver I downloaded from nvidia with one windows MS update offered. So far I haven't made any difference in the problem. I may have to pruchase a graphics adapter.

Once I did a clean install as usual it came so I coul use Win and It even rebooted and eventually I couldn't reboot. Same thing when I installed images from my backups.

Do you have onboard or discreet graphics? If discreet, disconnect it and use onboard graphics, if possible.

No graphics on MB. I am running an Nvidia GeForce GTX 260. It's been trouble free for about six mths. I added a few lines to the original post.

BS on boot.
The only way I can get win loaded is boot from the repair disk and restore an image. When the restore is done it auto boots it self and comes up. Win is fine then and does everything I ask. performance speed, graphics etc. seems normal.
At this stage if you exit Win (restart) then the boot will BS. If you push power off and power back up boot BS's. Then You have to restore the image again.
Have put different drivers in the graphics card all which have worked before. No Change.
The device manager shows no problems.
All disks seem to function. Memory checks out. I am using the machine now. If I shut it down I am screwed.
I have done clean installs they are fine until I exit win and try a reboot (via power button or reset). The difference is sonewhere in the fact the new Installation has never been shut down or it has been run for some period of time. This I think is hardware related.

Since re-imaging fixes it (temporarily), then there's gotta be an issue with the storage sub-system that's causing this.

From this link on my website: BSOD Index

Cause Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.
This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.

Try running a hard drive diagnostic (inside Windows so you don't have to reimage). You can download a free disk diagnostic from the website of the hard drive manufacturer. If unable to find one, try the free version of HDTune ( HD Tune website - it's the one after the HDTune Pro)

Usasma

Dl'd and installed HD Tune Pro (trial) Everthing looked ok (OS Disk) until I got on the folder usage tab and it locks up on the OS disk. All other disks don't do that.

I am going to shut down and disconnect some disks and reimage to a new boot disk to see if that works.

Disconnect the OS disk when doing so (both the data and the power cables).

I prefer the diagnostic from the manufacturer of the hard drive (they should know exactly how to test their own stuff) - but the HD Tune is a decent substitute for initial troubleshooting.

Good luck!

Usasma, Why didn't I just go ahead and change the disk?
I checked the disk with Win's chkdisk twice and it found no errors, not one.
I dl'd HD Tune Pro (trial) and it wasn't show much until I got to the folder tab and it hung the app trying to read the folders. Since My other disks didn't do that I shut down and went to another disk for my OS. Win Repair disk could not load an image to the new disk for what ever reason. So I used Acronis 2010, it couldn't load an image on the disk. So I done a clean install and then loaded an image. Appears to be OK, I can shut down and reboot. Thanks, for holding my hand. Got a big mess to clean up now.