Help Please

sychosis said:

Hi I'm new to these forums, found them after quite a few bsod's over the last couple of months, I'm starting to pull my hair out with this one. I was looking to debug this myself but none of the symbol libraries seem to work .

I have had this issue a while now, even had new equipment at work.

Now got i5 650, asus p7-h55 m pro, 4gb ram, 160gb hdd, 450w psu.

I have attached the minidump file.

Please help, I'm going to run memtest over night see if the ram is a problem.

There isnt much information in this DMP file.
I can suggest another thing to do while waiting for the next crash
I would suggest you run a system file check

To do that type cmd in search>right click and run as admnin>sfc /scannow (note the space between sfc and "/")

Let us know the results

thanks


Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\033110-17487-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a94e50
Debug session time: Wed Mar 31 03:44:18.083 2010 (GMT-4)
System Uptime: 0 days 0:00:08.144
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
---------

3: 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 fffff80002df9bc1 to fffff800028c8ed0

STACK_TEXT:  
fffff880`009a9b38 fffff800`02df9bc1 : 00000000`00000000 00000000`00000000 fffff800`00812970 fffff800`00812970 : nt!KeBugCheck
fffff880`009a9b40 fffff800`02d4a419 : 00000000`00000000 fffffa80`03b4b040 00000000`00000080 fffffa80`03aedb30 : nt!Phase1InitializationDiscard+0x1331
fffff880`009a9d10 fffff800`02b6c166 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`028a7479 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`028a7486 : fffff800`02a41e80 fffffa80`03b4b040 fffff800`02a4fc40 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`02df9bc1 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
---------

Ok ran that test, it told me there were some corrupted files and have been repaired. Had a look at log file

sychosis said:

Ok ran that test, it told me there were some corrupted files and have been repaired. Had a look at log file

In the report did it say which files? If you upload the cbs.log file we can analyze it for you

Ken

If I knew how to do this i wouldn't be bothering you guys.

sychosis said:

If I knew how to do this i wouldn't be bothering you guys.

Not a problem. we are here to help and to show you how to do things.


EDIT: BTW the files fixed were OS files so this may have fixed the problem. Let us know

It's done this quite a bit though, had errors when xp was installed pci.sys missing. Just getting on my nerves and my bosses, he installed it this time round. I'm still going to run memtest, plus it's taking a while to get to ctrl-alt-del screen.

sychosis said:

It's done this quite a bit though, had errors when xp was installed pci.sys missing. Just getting on my nerves and my bosses, he installed it this time round. I'm still going to run memtest, plus it's taking a while to get to ctrl-alt-del screen.

Just let us know if we can help


Ken