BSOD 0x0000007E while booting img on AMD
#1
Posted 18 February 2011 - 01:12 PM
before this BSOD , the img worked on almost 10 intel based notebooks and desktops , so i was pretty sure that somehow it is related to AMD specific issue .
i googled , and found out that intelppm service is the cause ,
since wimb, had it configured to 3 (load on demand ) , i tried with this settings too , but failed .
so i asked it here first ,
http://reboot.pro/9830/page__st__120
post # 121
then karyonix posted on post # 125 to disable it (set the intelppm service to 4)
. i asked on wuyou forums ,
and the solution FROM the link within worked .
as well as from karyonix , settings it to 4 , also worked .
Method 1 :
open driver.cab (driver cache\i386) folder , from it , extract " processr.sys " , rename it to " intelppm.sys "
REPLACE with the existing intelppm.sys file in your system32 folder.
DO NOT CHANGE THE SERVICE STATUS , KEEP IT TO 3 ) 0x000003.
Method 2 :
change the intelppm service to 4 (disable)
both above methods worked for me , on AMD and INTEL systems .
reference chinese thread .
http://bbs.wuyou.com...80&extra=page=1
#2
Posted 18 February 2011 - 01:21 PM
reference chinese blog (translated) :reference chinese thread .
http://translate.goo...en&hl=&ie=UTF-8
including a third method:
The first method:
1. Click "Start", click "Run", type regedit, and then click "OK."
2. Locate and click the following registry key: HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Services \ Intelppm
3. To change the start value of 4
4. Start value of 1 indicates support for the CPU INTEL
5. Start value of 4, AMD CPU support
INTEL above method may result in the CPU drive there! No, do not use the following method is recommended.
The second method:
First C: \ WINDOWS \ Driver Cache \ i386 \ drivers.cab
The processr.sys unzipped to replace the renamed intelppm.sys
C: \ WINDOWS \ system32 \ drivers \ intelppm.sys file
a third method:
1. Click "Start", click "Run", type regedit, and then click "OK."
2. Locate and click the following registry key: HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Services \ Intelppm
Change the value of the ImagePath
system32 \ DRIVERS \ processr.sys
It must be a VERY strange system or install as the setting to "3" (load on demand) seems like having always worked for everyone.
WOnko
#3
Posted 18 February 2011 - 01:51 PM
and as mentioned in my original post in wimb;s thread ,
service set to 3 , DID work on one AMD's desktop .
anyhow , since method 1 , is working on both intel and AMD's i have , so i am gonna keep it this way .
#4
Posted 18 February 2011 - 02:10 PM
But this way, with "4" disabled, unless I am mistaken you don't have intelppm running even on Intel machines.anyhow , since method 1 , is working on both intel and AMD's i have , so i am gonna keep it this way .
I find it "queer", just as this one:
http://blogs.msdn.co.../24/484461.aspx
I am old school and getting old , but as I see it a driver is either needed or it is not.
Could your issue be related to KB953356?:
http://www.blogsdna....r-amd-users.htm
http://msinfluential...ing-xp-sp3.aspx
http://support.micro...kb/953356/en-us
Wonko
#5
Posted 18 February 2011 - 02:42 PM
Maybe not so strange, as Wimb has also seen the same problem: http://reboot.pro/13...post__p__122653It must be a VERY strange system or install as the setting to "3" (load on demand) seems like having always worked for everyone.
#6
Posted 18 February 2011 - 02:56 PM
Doodoo, that's ANOTHER issue .Maybe not so strange, as Wimb has also seen the same problem: http://reboot.pro/13...post__p__122653
In the referenced post wimb reported that:
An image with intelppm.sys with start set as "3" (on demand or manual) AND working allright on an AMD machine, once booted on an Intel one had the start set to "1" (system) and then couldn't boot anymore on AMD)
That is PERFECTLY NORMAL (an image with intelppm.sys start 1 NOT booting on AMD), the "queer" thing is an image with intelppm.sys start 3 failing to boot.
If a driver is NOT set to 0 (boot) or 1 (system) or 2 (Autoload) BUT to 3 (on demand or manual) *something* must "trigger" it's start.
Obviously if it is set to 4 (Disabled) *nothing* can "trigger" it's start.
Wonko
#7
Posted 18 February 2011 - 03:09 PM
You're absolutely right, I should have read more carrefully....Doodoo, that's ANOTHER issue .
I'm doing too many things at once, trying to multi-task, which, as an honourable man, I obviously can't do very wellsince wimb, had it configured to 3 (load on demand ) , i tried with this settings too , but failed .
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users