Hi,

I have a friend who's getting the Blue Screen with the following text:

Stop: OXOOOOOO56 win 32k.sys
Address BF80172D base at BF800000 Datestamp 49e85772

He says it just started showing up randomly; not when he's doing anything in particular. 
I recently installed a new HD (about a month ago) when the old one died and reloaded 
the OS from self-created recovery discs. I also tested the memory at that time and 
it seemed to be fine.

Any ideas? I've done general searches on this error message and have gotten way too 
many different explanations. If you need more specific info, please let me know. 
Thanks.

Tip: Run a free scan for common Windows errors ad

re: Win32k.sys BSOD Wednesday, October 28, 2009 at 7:36 am Posted by MartinM (7551 messages posted) 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. [Reply or follow-up to this message] re: Win32k.sys BSOD Wednesday, October 28, 2009 at 8:12 am 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. > [Reply or follow-up to this message] re: Win32k.sys BSOD Wednesday, October 28, 2009 at 10:01 am Posted by MartinM (7551 messages posted) OK - a couple of things would help 1. Can the owner check the stop code please ? 2. In the Event Viewer, around the time of one of these BSOD, there wil lbe items with a red cross - double-clicking on them will reveal further details of the crashes . . . In passing, what was the make of the PC ? [Reply or follow-up to this message] re: Win32k.sys BSOD Wednesday, October 28, 2009 at 10:31 am Posted by Gary Tifeld (10 messages posted) Hi Martin, I will have to check that and get back to you. I'm not sure if I'll be able to get a better stop code from the owner as I think he emailed this to me, then threw away the paper he wrote it on, but I'll try. The PC in question is an HP Pavilion a749c. Thank you so much. --- Gary On Wednesday, October 28, 2009 at 10:01 am, MartinM wrote: > >OK - a couple of things would help > >1. Can the owner check the stop code please ? > >2. In the Event Viewer, around the time of one of these BSOD, there wil lbe items >with a red cross - double-clicking on them will reveal further details of the crashes >. . . > >In passing, what was the make of the PC ? > [Reply or follow-up to this message] re: Win32k.sys BSOD Thursday, October 29, 2009 at 10:21 am Posted by Gary Tifeld (10 messages posted) Hi again, Martin. I haven't had a chance to check the event viewer on the PC yet, but I just realized something. The owner wrote down the info and emailed it to me. I copied/pasted his info into these messages. Now that I look at it again, I think he meant Zeros where he entered the letter "O". So I'm thinking the stop code was probably 0x00000056. Does that make more sense? --- Gary On Wednesday, October 28, 2009 at 10:01 am, MartinM wrote: > >OK - a couple of things would help > >1. Can the owner check the stop code please ? > >2. In the Event Viewer, around the time of one of these BSOD, there wil lbe items >with a red cross - double-clicking on them will reveal further details of the crashes >. . . > >In passing, what was the make of the PC ? > [Reply or follow-up to this message] re: Win32k.sys BSOD Thursday, October 29, 2009 at 12:21 pm Posted by MartinM (7551 messages posted) Thanks Gary, That is an extremely rare error, and almost always associated with iffy hardware - and if not with hardware drivers (but drivers do not cause random, occasional events - they usually either work or they don't). I think its safe to say your friend has a hardware problem so I'd advise posting at a decent hardware forum - Tom's Hardware is one I know of, there are others of course. Hope this helps. On Thursday, October 29, 2009 at 10:21 am, Gary Tifeld wrote: >Hi again, Martin. > >I haven't had a chance to check the event viewer on the PC yet, but I just realized >something. The owner wrote down the info and emailed it to me. I copied/pasted his >info into these messages. Now that I look at it again, I think he meant Zeros where >he entered the letter "O". So I'm thinking the stop code was probably 0x00000056. >Does that make more sense? > >--- Gary > > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum