My computer restarts at boot up when the mouse shows on screen.It loads and work fine only after pressing F8 at boot up with Last Known Good Configuration.
I have attached the mini dump.
____________________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\andreea\Desktop\dump noni\Mini010109-2--school PC0.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\system;C:\WINDOWS\Symbols;C:\WINDOWS\Symbols\sp2
Executable search path is: C:\WINDOWS\
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Thu Jan 1 13:34:58.296 2009 (GMT+2)
System Uptime: 0 days 0:00:24.984
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 71, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!Phase1Initialization+1212 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SESSION5_INITIALIZATION_FAILED (71)
The bugcheck code (SESSION1 - SESSION5) indicates the point during
initialization when the failure was detected.
Arguments:
Arg1: 00000000, Indicates the NT status code that tripped Windows into thinking
that initialization failed.
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x71
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 806b1673 to 80537807
STACK_TEXT:
f79c683c 806b1673 00000071 85fc4540 00000000 nt!KeBugCheck+0x14
f79c6dac 80576b24 80087000 00000000 00000000 nt!Phase1Initialization+0x1212
f79c6ddc 804eed86 806b3797 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!Phase1Initialization+1212
806b1673 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!Phase1Initialization+1212
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
FAILURE_BUCKET_ID: 0x71_nt!Phase1Initialization+1212
BUCKET_ID: 0x71_nt!Phase1Initialization+1212
Followup: MachineOwner
---------
I have attached the mini dump.
____________________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\andreea\Desktop\dump noni\Mini010109-2--school PC0.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\system;C:\WINDOWS\Symbols;C:\WINDOWS\Symbols\sp2
Executable search path is: C:\WINDOWS\
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Thu Jan 1 13:34:58.296 2009 (GMT+2)
System Uptime: 0 days 0:00:24.984
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 71, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!Phase1Initialization+1212 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SESSION5_INITIALIZATION_FAILED (71)
The bugcheck code (SESSION1 - SESSION5) indicates the point during
initialization when the failure was detected.
Arguments:
Arg1: 00000000, Indicates the NT status code that tripped Windows into thinking
that initialization failed.
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x71
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 806b1673 to 80537807
STACK_TEXT:
f79c683c 806b1673 00000071 85fc4540 00000000 nt!KeBugCheck+0x14
f79c6dac 80576b24 80087000 00000000 00000000 nt!Phase1Initialization+0x1212
f79c6ddc 804eed86 806b3797 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!Phase1Initialization+1212
806b1673 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!Phase1Initialization+1212
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
FAILURE_BUCKET_ID: 0x71_nt!Phase1Initialization+1212
BUCKET_ID: 0x71_nt!Phase1Initialization+1212
Followup: MachineOwner
---------