Jump to content











Photo
- - - - -

win xp recovery disk (rc.iso) blu screen stop 7E


  • Please log in to reply
17 replies to this topic

#1 lemarec

lemarec

    Newbie

  • Members
  • 13 posts
  •  
    France

Posted 30 October 2010 - 11:12 AM

Hello

I tri win xp recovery disk, there is a wiondows blue screen with stop .... 0000x7e (pci.sys)

is anybody can help me

Thanks

#2 davidecosta

davidecosta

    Silver Member

  • Developer
  • 670 posts
  • Location:Sardinia
  •  
    Italy

Posted 30 October 2010 - 01:11 PM

for the hundredth time: ISO or USB? Virtual Machine o real Machine?

#3 lemarec

lemarec

    Newbie

  • Members
  • 13 posts
  •  
    France

Posted 30 October 2010 - 01:26 PM

Thanks for reply

on usb, real machine

#4 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1,671 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 30 October 2010 - 01:51 PM

Where did this rc.iso come from? Who made it? Was there a guide or instructions associated with it?

#5 davidecosta

davidecosta

    Silver Member

  • Developer
  • 670 posts
  • Location:Sardinia
  •  
    Italy

Posted 30 October 2010 - 02:00 PM

Where did this rc.iso come from? Who made it? Was there a guide or instructions associated with it?



The rc.iso is this http://www.thecomput...om/files/rc.iso

#6 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1,671 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 30 October 2010 - 03:26 PM

Thanks davidecosta.

I don't get that Blue Screen of Death when booting with:
qemu -cdrom rc.iso -boot d
So perhaps it's a corrupted download? Or perhaps it's being booted off the USB with the GRUB4DOS map command? When Windows switches over to the kernel and drivers, it won't have a driver for the GRUB4DOS-mapped disc.

#7 lemarec

lemarec

    Newbie

  • Members
  • 13 posts
  •  
    France

Posted 30 October 2010 - 04:24 PM

I only use automatic configuration of Sardu, i download rc.iso fron Sardu link

#8 davidecosta

davidecosta

    Silver Member

  • Developer
  • 670 posts
  • Location:Sardinia
  •  
    Italy

Posted 30 October 2010 - 07:03 PM

In sardu i use this string: (read here)

label Avvio di XP Recovery Console

menu label Avvio di XP Recovery Console

	  COM32 /chain.c32

	  APPEND cmldr=/cmdcons/setupldr.bin hd0,1

but the result is the some with

KERNEL /boot/grub.exe

	APPEND --config-file="timeout 0;fallback 1;find --set-root /cmdcons/setupldr.bin;chainloader /cmdcons/setupldr.bin;write 0x7C03 0x63646D63;write 0x7C07 0x00736E6F

In my pc boot fine, after asking me to insert the cd of windows xp home...i've professional....but i don't see BSOD
My opinion is that it is a hardware problem

#9 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1,671 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 30 October 2010 - 08:21 PM

What is the point of all this if Windows doesn't have a driver for accessing rc.iso? You "pull the tablecloth out from underneath", but the table comes with it and the dishes all break. Am I missing something?

#10 ilko

ilko

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    Bulgaria

Posted 31 October 2010 - 02:28 AM

What's the hardware where the error comes up?

This reminds me of Asus EeePC and several other similar netbook models where XP setup/Recovery Console prior to SP2 results in 0x0000007E at pci.sys during text mode.

BTW- I guess the link to rc.iso shouldn't be posted.

#11 davidecosta

davidecosta

    Silver Member

  • Developer
  • 670 posts
  • Location:Sardinia
  •  
    Italy

Posted 31 October 2010 - 09:01 AM

BTW- I guess the link to rc.iso shouldn't be posted.


Why?
It's not warez. As is the recovery (Vista and Seven) from NeoSmart.
I don't understand instead how to distribute a Pe>2 eScan

#12 lemarec

lemarec

    Newbie

  • Members
  • 13 posts
  •  
    France

Posted 31 October 2010 - 11:13 AM

Hello

I try two other pc (notbook)

2nd pc : bsod stop 7e but no other message (not pci.sys)
3rd pc : boot ok, he want windows xp cd

#13 cdob

cdob

    Silver Member

  • Expert
  • 902 posts

Posted 31 October 2010 - 12:15 PM

Why?
It's not warez.

Non distribuatable files are distributed without manufacturer permission. Hence warez.

Version seem to be rather old. Fails at some current hardware.
Why not download newer files from original manufacturer and create a recovery console part locally?
http://www.boot-land...?showtopic=2254
http://www.boot-land...?showtopic=5316
http://www.boot-land...showtopic=10073

Redistributing Software
http://www.microsoft...ns/Default.aspx
https://www.microsof...ssions/faq.mspx

As is the recovery (Vista and Seven) from NeoSmart.

Distribution is not clear. May be with or without manufacturer permission.

I don't understand instead how to distribute a Pe>2 eScan

http://msdn.microsof...s/ff723773.aspx
A third party manufactuer may get permission to distribute Windows PE.
You have to ask the original manufacturer first.

#14 davidecosta

davidecosta

    Silver Member

  • Developer
  • 670 posts
  • Location:Sardinia
  •  
    Italy

Posted 31 October 2010 - 01:02 PM

Non distribuatable files are distributed without manufacturer permission. Hence warez.

Version seem to be rather old. Fails at some current hardware.
Why not download newer files from original manufacturer and create a recovery console part locally?
http://www.boot-land...?showtopic=2254
http://www.boot-land...?showtopic=5316
http://www.boot-land...showtopic=10073

Redistributing Software
http://www.microsoft...ns/Default.aspx
https://www.microsof...ssions/faq.mspx

Distribution is not clear. May be with or without manufacturer permission.

http://msdn.microsof...s/ff723773.aspx
A third party manufactuer may get permission to distribute Windows PE.
You have to ask the original manufacturer first.



BTW thank for link, I think I use this to XPRC.ISO

http://www.thecomputerparamedic.com/, http://neosmart.net have the permission for redistribute? http://www.escanav.com have the permission for redistribute?
I don't know.
I' don't have permission, never wanted, for redistribute.
if it is illegal to put links can take them off in two seconds.

#15 cdob

cdob

    Silver Member

  • Expert
  • 902 posts

Posted 31 October 2010 - 04:53 PM

http://www.thecomputerparamedic.com/, http://neosmart.net have the permission for redistribute? http://www.escanav.com have the permission for redistribute?
I don't know.

I don't know too.
I assume: a commercial company got the permission from original manufacturer

Ask them to clarify
http://neosmart.net/blog/contact-us/
http://www.escanav.c...n_contactus.asp

#16 cquirke

cquirke
  • Members
  • 8 posts
  • Interests:Maintenance OS (mOS), PCs, memetics, data recovery, formal malware management. On mOS, have some Bart skills, need to build WinPE 2.0 and Linux skills. My profile "date of birth" is a lie, of course.
  •  
    South Africa

Posted 08 December 2010 - 08:48 PM

Hello

I tri win xp recovery disk, there is a wiondows blue screen with stop .... 0000x7e (pci.sys)

is anybody can help me

Thanks


This usually happens if the XP native code base that underlies Bart PE, XP install disk etc. can't "see" the boot drive interface. The most common cause is where S-ATA is AHCI rather than legacy mode, or RAID.

Note that if you change modes from AHCI to Legacy or vice versa, the hard drive installation that was using the original setting will crash on boot. This applies to modern (Vista/7) Windows too, though their corresponding install DVDs and WinPE 2/3 won't care either way.

#17 GTech

GTech
  • Members
  • 3 posts
  •  
    United States

Posted 26 December 2010 - 01:56 AM

I fix A LOT of computers every week, been doing it for years, and when I use the Windows Recovery Disk, Windows XP Disc, or even a Barts PE Builder Boot CD (UBCD or Custom) it sometimes will kick out this same Blue screen, no matter which disc you use, for no apparent reason. (It could be a boot sector virus, and this is always the first step in diagnosing computer problems, running virus scanners.)

One thing I did notice is, it's more common on HP & Dell computers, call me crazy, but these two computer MFGs like to give me fits sometimes!

The resolution to the problem also starts with checking / testing hardware.

#1) Run Memtest86 4.01 (ONE Memory Module at a Time is the KEY!!)
#2) Re-Seat the Processor
#3) Start taking things off the Main Board (Mother Board), one piece at a time and see if this will not resolve the issue. (Obviously you won't be taking off the processor or RAM, but you can reduce RAM down to 1 known good RAM Memory Module) If there is a graphics card on the motherboard, and you have integrated OnBoard Video on the Mother Board, then take off the graphics card and see if this will allow it to pass setup.

Another common problem I run into is bad bios settings, so you may want to load factory defaults, or clear cmos even.

If you follow these steps you may find the cause of the problem. It could be something simple as a bad DVD/CD Optical Drive, it's hard to say what is the cause without testing the machine.

GTech

Edited by GTech, 26 December 2010 - 01:58 AM.


#18 bluebird

bluebird
  • Members
  • 1 posts
  •  
    Germany

Posted 27 November 2013 - 03:08 PM

[SOLVED]

 

i also getted BSOF, pci.sys, insert windows xp home cd in your cdrom drive

 

what i do for solving this problems:

 

 

i use sardu 2.0.6.5

i download the xp_rc with sardu or take the links from this page

 

after creating the usb pendrive is finish:

 

open your pendrive  --> goto /SARUDU/pe.cfg

 

replace the line:

 

APPEND cmldr=/cmdcons/setupldr.bin hd0,1

with

APPEND cmldr=/cmdcons/setupldr.bin hd0

 

save file. 

 

to provite to get the error message: insert windows xp home cd in your cd rom drive:

 

create a file on your usb pendrive @ /cmdcons/winnt.sif

 

open the createt file winnt.sif with editor

 

insert the following in this file:

-------------------------------------------start of file 

 

[data]
msdosinitiated="1"
floppyless="1"
CmdCons="1"
LocalSourceOnCD="1"
AutoPartition="0"
UseSignatures="yes"
InstallDir="\WINDOWS"
EulaComplete="1"
winntupgrade="no"
win9xupgrade="no"
Win32Ver="a280105"
uniqueid="C:\WINDOWS\ANM"
OriSrc="D:\"
OriTyp="5"
[regionalsettings]
Language=00000409
LanguageGroup=1
[unattended]
unused=unused
[userdata]
productid=""
productkey=""
[OobeProxy]
Enable=1
Flags=1
Autodiscovery_Flag=4

 

------------------------------------------------------end of file

thats all i do.

now it should works






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users