| | |
Error message after Windows XP runs through setup process at first boot up
![]() |
•
•
Join Date: May 2005
Posts: 1
Reputation:
Solved Threads: 0
Hello all. I'm rather new to "Posting threads", but here it goes...
I built a system for my office. I installed Windows XP Pro, all the necessary software, applied the Group Policy, and installed SP2. When all was said and done, I ran SYSPREP so I could create an Image with Symantec Ghost 7.5. All went well until I booted the imaged system. It went through the normal setup/installing devices, etc. At the end of that, before it boots to the Windows logon screen, I get a "setup - Application Error" message: The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
I've searched the web for some support regarding this issue, but haven't found anything. Could the installation of SP2 be the cause?
Please help, anyone,
Keoki
I built a system for my office. I installed Windows XP Pro, all the necessary software, applied the Group Policy, and installed SP2. When all was said and done, I ran SYSPREP so I could create an Image with Symantec Ghost 7.5. All went well until I booted the imaged system. It went through the normal setup/installing devices, etc. At the end of that, before it boots to the Windows logon screen, I get a "setup - Application Error" message: The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
I've searched the web for some support regarding this issue, but haven't found anything. Could the installation of SP2 be the cause?
Please help, anyone,
Keoki
•
•
Join Date: Jun 2005
Posts: 1
Reputation:
Solved Threads: 0
Hi,
I have the exact same problem. After ghost finishes, the system reboots and then during the mini-setup I get the error:
Setup.exe - Application Error
The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
Was hoping that maybe you had found a fix for this problem. If you have, please reply. I'm racking my brain over this one and getting no where.
Also if you found anyway around it to get the same result please post.
I did find out how to fix the computer from going through the loop. Visit:
http://support.microsoft.com/default...b;en-us;287506
Cheers,
Maxi
I have the exact same problem. After ghost finishes, the system reboots and then during the mini-setup I get the error:
Setup.exe - Application Error
The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
Was hoping that maybe you had found a fix for this problem. If you have, please reply. I'm racking my brain over this one and getting no where.
Also if you found anyway around it to get the same result please post.
I did find out how to fix the computer from going through the loop. Visit:
http://support.microsoft.com/default...b;en-us;287506
Cheers,
Maxi
•
•
Join Date: Mar 2004
Posts: 3,826
Reputation:
Solved Threads: 144
Sometimes those errors can be caused by faulty hardware - a processor which is failing, RAM modules which are faulty or mismatched, etc, etc.
But most of the time they will be the result of software issues. In this case, it is most likely a program which is causing the problem, and if it results from a conflict with SP2 then the first place I'd start looking is any Symantec/Norton products in use!
But most of the time they will be the result of software issues. In this case, it is most likely a program which is causing the problem, and if it results from a conflict with SP2 then the first place I'd start looking is any Symantec/Norton products in use!
•
•
Join Date: Jul 2005
Posts: 1
Reputation:
Solved Threads: 0
It's not a hardware issue. I'm using one machine to create the image, another to test it, two different models altogether. I create an image about every two months, and this is the first time I've seen this at all. I don't believe it has anything to do with the mini setup either.
What I'm thinking is either policies, or one of 20 IA patches for XP that has come out recently.
I feel better knowing I'm not the only one getting an error unreferenced by MS, but as soon as I figure this out, I'll post it.
Mark
What I'm thinking is either policies, or one of 20 IA patches for XP that has come out recently.
I feel better knowing I'm not the only one getting an error unreferenced by MS, but as soon as I figure this out, I'll post it.
Mark
•
•
Join Date: Aug 2006
Posts: 1
Reputation:
Solved Threads: 0
•
•
•
•
Originally Posted by keoki.suerth
Hello all. I'm rather new to "Posting threads", but here it goes...
I built a system for my office. I installed Windows XP Pro, all the necessary software, applied the Group Policy, and installed SP2. When all was said and done, I ran SYSPREP so I could create an Image with Symantec Ghost 7.5. All went well until I booted the imaged system. It went through the normal setup/installing devices, etc. At the end of that, before it boots to the Windows logon screen, I get a "setup - Application Error" message: The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
I've searched the web for some support regarding this issue, but haven't found anything. Could the installation of SP2 be the cause?
Please help, anyone,
Keoki
Last edited by 'Stein; Aug 31st, 2006 at 9:25 pm.
•
•
Join Date: Aug 2006
Posts: 2
Reputation:
Solved Threads: 0
[quote=keoki.suerth;121118]Hello all. I'm rather new to "Posting threads", but here it goes...
I built a system for my office. I installed Windows XP Pro, all the necessary software, applied the Group Policy, and installed SP2. When all was said and done, I ran SYSPREP so I could create an Image with Symantec Ghost 7.5. All went well until I booted the imaged system. It went through the normal setup/installing devices, etc. At the end of that, before it boots to the Windows logon screen, I get a "setup - Application Error" message: The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
I've searched the web for some support regarding this issue, but haven't found anything. Could the installation of SP2 be the cause?
Keoki,
I've recently experienced the same issue (exact same memory location) and am currently troubleshooting it. Have you resolved this issue yet? What mechanism did you use to apply security settings? Did you use Security Configuration and Analysis? So far, I am under the impression that some security settings are causing the conflict. I don't believe it is SP2 - I've successfully syspreped a virgin-XP/Office 2003 installation w/SP2.
I built a system for my office. I installed Windows XP Pro, all the necessary software, applied the Group Policy, and installed SP2. When all was said and done, I ran SYSPREP so I could create an Image with Symantec Ghost 7.5. All went well until I booted the imaged system. It went through the normal setup/installing devices, etc. At the end of that, before it boots to the Windows logon screen, I get a "setup - Application Error" message: The instruction at "0x5f1a340b" referenced memory at "0x00000014". The memory could not be "read".
I've searched the web for some support regarding this issue, but haven't found anything. Could the installation of SP2 be the cause?
Keoki,
I've recently experienced the same issue (exact same memory location) and am currently troubleshooting it. Have you resolved this issue yet? What mechanism did you use to apply security settings? Did you use Security Configuration and Analysis? So far, I am under the impression that some security settings are causing the conflict. I don't believe it is SP2 - I've successfully syspreped a virgin-XP/Office 2003 installation w/SP2.
•
•
Join Date: Aug 2007
Posts: 1
Reputation:
Solved Threads: 0
Hi Everyone:
Recently I happened to achieve the same error, I read the thread and you were right, it was the telephony service. So I booted from CD, in command mode and wrote the follwing command:
enable TapiSrv STARTUP_AUTOMATIC_MODE (or something like that, just type enable /? and you'll get the right mode)
After that, I rebooted my machine (which was sysprep'ed) and voila!! ... everything works like a charm!!
Hope this can be useful.
Greetings
Heiner
Recently I happened to achieve the same error, I read the thread and you were right, it was the telephony service. So I booted from CD, in command mode and wrote the follwing command:
enable TapiSrv STARTUP_AUTOMATIC_MODE (or something like that, just type enable /? and you'll get the right mode)
After that, I rebooted my machine (which was sysprep'ed) and voila!! ... everything works like a charm!!
Hope this can be useful.
Greetings
Heiner
•
•
Join Date: May 2008
Posts: 3
Reputation:
Solved Threads: 0
I just want to second the fact that the starting of the tapisrv does fix the memory error, this is also linked in services to Telephony and the actual command is enable tapisrv SERVICE_AUTO_START!
Thank you for taking the time to share, this saved me two days of work for 30 workstations that I couldn't get past mini-setup with out your help!!!
R
Thank you for taking the time to share, this saved me two days of work for 30 workstations that I couldn't get past mini-setup with out your help!!!
R
•
•
•
•
Hi Everyone:
Recently I happened to achieve the same error, I read the thread and you were right, it was the telephony service. So I booted from CD, in command mode and wrote the follwing command:
enable TapiSrv STARTUP_AUTOMATIC_MODE (or something like that, just type enable /? and you'll get the right mode)
After that, I rebooted my machine (which was sysprep'ed) and voila!! ... everything works like a charm!!
Hope this can be useful.
Greetings
Heiner
•
•
Join Date: Sep 2008
Posts: 2
Reputation:
Solved Threads: 0
•
•
•
•
I just want to second the fact that the starting of the tapisrv does fix the memory error, this is also linked in services to Telephony and the actual command is enable tapisrv SERVICE_AUTO_START!
Thank you for taking the time to share, this saved me two days of work for 30 workstations that I couldn't get past mini-setup with out your help!!!
R
"Instruction at "0x7e44089d" referenced memory at "0x000003ff". The memory could not be "read"."
I see that there is a solution to the problem but it appears too advanced for me as I am a complete novice at software issues.. Would someone please be able to explain step by step what to do?
Thanks!!
![]() |
Similar Threads
- "Error message when installing w2k pro" (Windows NT / 2000 / XP)
- MERGED: Hardware/Driver Problems-Error Message (Windows 95 / 98 / Me)
- start up error message (Windows NT / 2000 / XP)
- spybot german error message (Viruses, Spyware and other Nasties)
- Error message when starting Microsoft Word (Windows 95 / 98 / Me)
- Reload page Error message when starting Windows XP (Viruses, Spyware and other Nasties)
- ME error message (unknown) (Windows 95 / 98 / Me)
- Error message when trying to load Windows XP from a CD! HELP! (Windows NT / 2000 / XP)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: My Website
- Next Thread: Forgot Windows NT 4.0 Admin Password HELP RECOVER
| Thread Tools | Search this Thread |
.net 64bit 2007 2010 a.exe activedirectory address android apache appstore automatically black blue bsod bulletin canonical chinese chkdsk codeplex combofix cursor deployment deployments desktop dns drive eartlink error errors explorer fax features fontmanagers format framework freeze hardware home internet interoperability laptop laptops lcd linux login mac markshuttleworth memory microsoft monitor motionle1600 netbooks novell nvidia open opensource operatingsystems options oracle osinstallationproblem osx palm partition printer product program proxy reformat remotedesktop repair replacingraiddrive retail retrieve screen security sharepoint simplifiedchinese sitetositevpn slowperformance sp3 spyware studios technology ubuntu update upgrade videodrivers videogames virus vista visual vpn win win32/heur windows windows7 windowsxp windowsxpnotstartingup. xp xpde






