[ipxe-devel] Windows XP just reboots all time in the logo screen
Daniel García
abuelandersson at gmail.com
Fri Oct 7 12:01:11 UTC 2011
Hi,
I've re-installed Windows XP and sanbootconf 1.0. It still giving me the
same problem: windows reboots itself when the logo screen appears.
Looking at the WinDbg report, i think the problem migth be that sanbootconf
driver doesn´t load in the boot secuence.
Anybody can tell me why it happends? Thanks for yout time.
Daniel Garcia.
El 5 de octubre de 2011 16:20, Daniel García <abuelandersson at gmail.com>escribió:
Thanks for the info, Shao
>
> I've followed your advice and checked if sanbootconf driver was loaded, and
> it looks like it wasn't. I don't know why this happend, I installed the last
> version of sanbootconf with no error.
>
> I attach the new WinDbg capture with the result of the "lm" command.
>
> Daniel Garcia.
>
> El 5 de octubre de 2011 15:26, Daniel García <abuelandersson at gmail.com>escribió:
>
> Hi again,
>>
>> I've upgraded to iPXE and to the new version of sanbootconf too, but I'm
>> getting the same error: the client machines conects to the iscsi target and
>> starts booting windows xp, until it reboots itself, giving a 0x00007b error
>> in the WinDbg.
>>
>> I attach the WinDbg output file. I'd appreciate any kind of help. I've
>> been looking hard for any solution, but I found nothing...
>>
>> Daniel.
>>
>> El 4 de octubre de 2011 13:51, Daniel García <abuelandersson at gmail.com>escribió:
>>
>> Hi,
>>>
>>> I've followed the how-to and I get the error report from WinDbg attached
>>> to this mail. I'd appreciate any information you can give me.
>>>
>>> It seems like sanbootconf driver doesn't load.
>>>
>>>
>>> Daniel.
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20111007/3e07ce46/attachment.htm>
-------------- 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 (Fri Oct 7 13:35:33.609 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for 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
Break instruction exception - code 80000003 (first chance)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
nt!DbgBreakPoint:
8052b5d0 cc int 3
kd> g
*** 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> lm
start end module name
804d7000 806e5000 nt (export symbols) ntkrpamp.exe
806e5000 80705d00 hal (export symbols) halmacpi.dll
f7185000 f71bb000 iscsiprt (deferred)
f71bb000 f71fa000 msiscsi (deferred)
f71fa000 f7213b80 Mup (deferred)
f7214000 f7237180 Fastfat (deferred)
f7238000 f7257b00 fltMgr (deferred)
f7258000 f726f900 atapi (deferred)
f7270000 f7280e00 psched (deferred)
f7281000 f72d9380 tcpip (deferred)
f72da000 f72ec600 ipsec (deferred)
f72ed000 f7303880 KSecDD (deferred)
f7304000 f7330980 NDIS (deferred)
f7331000 f7356a80 dmio (deferred)
f7357000 f7375c00 ftdisk (deferred)
f7376000 f7386d80 pci (deferred)
f7387000 f73b5280 ACPI (deferred)
f73b6000 f73cd880 SCSIPORT (deferred)
f73ce000 f74ce000 sptd (deferred)
f75cf000 f75d8380 isapnp (deferred)
f75df000 f75e9580 MountMgr (deferred)
f75ef000 f75fc000 VolSnap (deferred)
f75ff000 f7607900 msgpc (deferred)
f760f000 f7617e00 disk (deferred)
f761f000 f762b180 CLASSPNP (deferred)
f784f000 f7855180 PCIIDEX (deferred)
f7857000 f785bd00 PartMgr (deferred)
f785f000 f7863a80 TDI (deferred)
f79df000 f79e2000 BOOTVID (deferred)
f7acf000 f7ad0b80 kdcom (deferred)
f7ad1000 f7ad2100 WMILIB (deferred)
f7ad3000 f7ad4700 dmload (deferred)
f7b97000 f7b97d80 pciide (deferred)
More information about the ipxe-devel
mailing list