Annoyances.org
Home » Windows XP Discussion Forum » Message 1256742747 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: Win32k.sys BSOD
Wednesday, October 28, 2009 at 8:12 am
Windows XP Annoyances Discussion Forum
Posted by Gary Tifeld (10 messages posted)


Hi Martin,

That code was given to me by the owner of the PC. I didn't actually see it myself.

When the PC was brand new, I created a set of recovery CDs using the pre-installed 
utility for that. When I just installed the new HDD, I booted off the first CD and 
did an automatic re-load. Does that make sense? I believe this was the correct procedure 
as I've done it before and have had no problems, but should I have followed another 
method? The system BIOS seemed to have no trouble recognizing the new drive.





On Wednesday, October 28, 2009 at 7:36 am, MartinM wrote:
>


>Gary,
>
>I believe I am right in saying you can't have a OXOOOOOO56 stop error - can
>you check the exact digits ?
>
>However the clue may lie in how the restore was done - what exactly do you mean by
>"reloaded the OS from self-created recovery discs" ? It is possible you may have
>to do a repair/install to fully identify the new HDD to the OS.
>




Written in response to:
re: Win32k.sys BSOD (MartinM: Wednesday, October 28, 2009 at 7:36 am)

There are presently no replies to this message.

All messages in this thread [show all]
-Win32k.sys BSOD (Gary Tifeld: Wed, Oct 28, 2009, 7:28 am)
-re: Win32k.sys BSOD (MartinM: Wed, Oct 28, 2009, 7:36 am)
*re: Win32k.sys BSOD (Gary Tifeld: Wed, Oct 28, 2009, 8:12 am)
-re: Win32k.sys BSOD (MartinM: Wed, Oct 28, 2009, 10:01 am)
*re: Win32k.sys BSOD (Gary Tifeld: Wed, Oct 28, 2009, 10:31 am)
-re: Win32k.sys BSOD (Gary Tifeld: Thu, Oct 29, 2009, 10:21 am)
*re: Win32k.sys BSOD (MartinM: Thu, Oct 29, 2009, 12:21 pm)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright © 1995-2009 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.