[ipxe-devel] Windows XP just reboots all time in the logo screen
Daniel García
abuelandersson at gmail.com
Wed Oct 19 09:42:51 UTC 2011
Hi,
I did a new clean installation of windows xp, after formating my hard disk.
I installed the Microsoft ISCSI Initiator and after it the sanbootconf 1.0
driver. Everything went fine. But I'm still having the same situation:
Windows reboots because 0x7B error.
I checked the services and driver boot order using the LoadOrd.exe
aplication, and the result output is attached to this mail. It seems to be
well configured, sanbootconf has a start value of "Boot" and is in group
"Base", as you can see.
But when i run a WindDbg, it seems not to load the sanbootconf driver when
it should. I've also attached the WindDbg output.
I'm really stuck on here.
Thank you for all the help,
Daniel García.
2011/10/17 Shao Miller <Shao.Miller at yrdsb.edu.on.ca>
> On 10/17/2011 04:36, Daniel García wrote:
>
>> I've reinstalled the driver as i've been told. I've also activated the
>> "Verbose output" option. But it still reboots. I've attached to this mail
>> the error report.
>>
>> I've connected the physical disk to my client computer and it boots
>> correctly. But if you look in the WinDbg report, it seems to load the
>> sanbootconf driver, but it's almost the last driver to load. Maybe is that
>> the problem? How I can change the loading order of the modules? I've also
>> attached this report of a correct booting (no_error.txt)
>>
>
> A useful program which I think you might enjoy in order to view driver (and
> service) loaded order is Microsoft's Sysinternals' LoadOder (LoadOrd.exe).
> Please boot the iSCSI disk as a locally-attached disk, then run LoadOrder
> and have a look.
>
> All of the items with a value of "Boot" in the "Start value" column are
> those that are loaded by NTLDR; they're the ones that you see loaded when
> you choose to boot in Safe Mode or when you add the /SOS switch to your
> BOOT.INI file.
>
> If the SANBootConf driver is not a "Boot" driver, then either it's setup
> program has failed to set it as a boot-start driver, or you haven't run its
> setup program.
>
> Only those drivers that are boot-start drivers are available before STOP
> 0x7B time.
>
> - Shao Miller
>
> ______________________________**_________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/**mailman/listinfo/ipxe-devel<https://lists.ipxe.org/mailman/listinfo/ipxe-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20111019/232339ef/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: LoadOrder.txt
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20111019/232339ef/attachment.txt>
-------------- next part --------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\COM2
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Wed Oct 19 11:11:32.843 2011 (UTC + 2:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Verbose mode ON.
ntkrpamp.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
ModLoad: 804d7000 806e5000 ntkrpamp.exe
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
System Uptime: not available
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded exts extension DLL
Loaded kext extension DLL
Loaded kdexts extension DLL
Force unload of ntkrpamp.exe
ModLoad: 804d7000 806e5000 ntkrpamp.exe
ModLoad: 806e5000 80705d00 halmacpi.dll
Break instruction exception - code 80000003 (first chance)
Loading symbols for 804d7000 ntkrpamp.exe -> ntkrpamp.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
nt!DbgBreakPoint:
8052b5d0 cc int 3
kd> g
ModLoad: f7acf000 f7ad0b80 kdcom.dll
ModLoad: f79df000 f79e2000 BOOTVID.dll
ModLoad: f749f000 f74cd280 ACPI.sys
ModLoad: f7ad1000 f7ad2100 WMILIB.SYS
ModLoad: f748e000 f749ed80 pci.sys
ModLoad: f75cf000 f75d8380 isapnp.sys
ModLoad: f7b97000 f7b97d80 pciide.sys
ModLoad: f784f000 f7855180 PCIIDEX.SYS
ModLoad: f75df000 f75e9580 MountMgr.sys
ModLoad: f746f000 f748dc00 ftdisk.sys
ModLoad: f7ad3000 f7ad4700 dmload.sys
ModLoad: f7449000 f746ea80 dmio.sys
ModLoad: f7857000 f785bd00 PartMgr.sys
ModLoad: f75ef000 f75fc000 VolSnap.sys
ModLoad: f741c000 f7448980 NDIS.sys
ModLoad: f73ce000 f741b680 Rtenicxp.sys
ModLoad: f738f000 f73ce000 msiscsi.sys
ModLoad: f7359000 f738f000 iscsiprt.sys
ModLoad: f785f000 f7863a80 TDI.SYS
ModLoad: f7342000 f7358880 KSecDD.sys
ModLoad: f732f000 f7341600 ipsec.sys
ModLoad: f75ff000 f7607900 msgpc.sys
ModLoad: f72d6000 f732e380 tcpip.sys
ModLoad: f72c5000 f72d5e00 psched.sys
ModLoad: f72ad000 f72c4900 atapi.sys
ModLoad: f760f000 f7617e00 disk.sys
ModLoad: f761f000 f762b180 CLASSPNP.SYS
ModLoad: f728d000 f72acb00 fltMgr.sys
ModLoad: f727b000 f728cf00 sr.sys
ModLoad: f7257000 f727a180 Fastfat.sys
ModLoad: f723d000 f7256b80 Mup.sys
*** Fatal System Error: 0x0000007b
(0xF79EA524,0xC0000034,0x00000000,0x00000000)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f79ea524, c0000034, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntkrpamp.exe ( nt!KeRegisterBugCheckReasonCallback+77c )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8052b5dc cc int 3
0: kd> g
Shutdown occurred at (Wed Oct 19 11:13:11.312 2011 (UTC + 2:00))...unloading all symbol tables.
Unloading exts extension DLL
Unloading kext extension DLL
Unloading kdexts extension DLL
Unloading dbghelp extension DLL
Unloading ext extension DLL
Waiting to reconnect...
More information about the ipxe-devel
mailing list