locked
The instruction at 0x776e7a1f referenced memory at 0x00000028. The memory could not be written. RRS feed

  • Question

  • Hello Every one

    Today i was stuck in the lab session of Operating System Deployment, I have made booting imange , operating image successfully. Even I was made and advertise task secuence of upgradation of Window Xp to Windows 7.

    As I was anlysised of XP client Pc has copied booting files and capture of the others file. We have got error message since xp client machine tobe restart which is mentioned below as well as snapshot below.

    Error:- The instruction at 0x776e7a1f referenced memory at 0x00000028. The memory could not be written.

    Click on Ok to terminate the program.

    Please suggest us what should i do for this for resovling the issue.

    In case if you feel to ask any quires or any other details, please revert back.

    Monday, July 23, 2012 6:55 AM

Answers

  • well then you found the wrong smsts.log file,, look again at the post i linked you to and check all locations for that file, the error must be logged and it will help us determine what went wrong.


    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Tuesday, July 24, 2012 8:39 PM
  • Hi Niall

    Thanks for your reply.

    I did not got any error in the smsts.log files. I have been checked on fresh machine as i was installed XP operating system and installed sms client then run the task sequence as found the issue has same.

    You won't see any error in the logs because the program has crashed.

    You should still post the logs so that we can see what the program was doing when it crashed.

    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Tuesday, July 24, 2012 10:50 PM
  • Considering the type of error, maybe run a hard drive diagnostics and a memory diagnostics? This doesnt seem like a typical SCCM error.
    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Wednesday, July 25, 2012 11:11 AM

All replies

  • what does your smsts.log file say about this ? is it only happening on one computer ? if so perhaps it has issues with memory/hard disc

    here's how to see that log, and funnily enough it's a similar error to yours



    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    Monday, July 23, 2012 5:04 PM
  • Hi Niall

    Thanks for your reply.

    I did not got any error in the smsts.log files. I have been checked on fresh machine as i was installed XP operating system and installed sms client then run the task sequence as found the issue has same.

    Monday, July 23, 2012 8:20 PM
  • well then you found the wrong smsts.log file,, look again at the post i linked you to and check all locations for that file, the error must be logged and it will help us determine what went wrong.


    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Tuesday, July 24, 2012 8:39 PM
  • Hi Niall

    Thanks for your reply.

    I did not got any error in the smsts.log files. I have been checked on fresh machine as i was installed XP operating system and installed sms client then run the task sequence as found the issue has same.

    You won't see any error in the logs because the program has crashed.

    You should still post the logs so that we can see what the program was doing when it crashed.

    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Tuesday, July 24, 2012 10:50 PM
  • Considering the type of error, maybe run a hard drive diagnostics and a memory diagnostics? This doesnt seem like a typical SCCM error.
    • Marked as answer by Sabrina Shen Thursday, August 9, 2012 5:58 AM
    Wednesday, July 25, 2012 11:11 AM