Windows XP PRO blue screen STOP ERROR

[fLYtRap]

I am getting this error lately (this computer is not conected to the internet, so I am exluding virus, trojan or other possibiliteies like that.

This error comes up on various occassions.

Does anyone have a clue what that colud be?:

PLEASE READ ENTIRE ERROR MESSAGE BEFORE POSTING ANY COMMENTS!

"A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. ---> I DO
If a driver is identified in the stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. ---> win32k.sys ?

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup options, and than select safe mode. ---> NO NEED

Technical information:

*** STOP: 0x000000SE (0xC000000S, 0x8F8F752C, 0xBAA656A4, 0x00000000)

*** win32k.sys - Adress 8F8F752C base at 8F800000, DateStamp 3f73195d

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance."

[redwudz]

You can't tell much from Windows cryptic error codes, but my first guess would be a RAM error. You might try running memtest86: http://www.memtest86.com/ It may tell you if you have a bad module. You may have to try one module at a time to figure out which one is the problem.

Or if you are overclocking, turn it down a little. If you have a spare memory module or more than one, trade them out and try one at a time.

I've ran into problematic memory modules before and they can cause all kinds of strange errors. If you are getting a lot of BSODs, it may get rapidly worse as these crashes can damage the OS files when it shuts down the system. The memory dump is trying to save the data for the next boot. You may get the other message when rebooting. 'Your computer has recovered from a serious error.....'

[fLYtRap]

Actually those errors are very acurate if you know how to read them. It must have something to do with this listed driver, but I have no clue what that could be.

[bobkart]

... and than select safe mode.

Just curious, did the message really contain this grammatical error?

[InXess]

This is usually due to OS inability to write to certain memory area be it RAM (modules), pagefile or generally HDD. It is close to "device unavailable" internal message. If you run memory test and checks out OK proceed to fixing the file system on OS HDD as well as pagefile HDD if different then OS. You may have to chkdsk it, if no improvement image the drive, zero-write the drive and reimage. Other possible reason is failing HDD controller (that means HDD replacement). In both cases Manuf. HDD FULL (advanced) disk test utility may help. Also check your PC and CPU running temperatures and see if you can go any lower by improving cooling. Memory although may go bad is less likely then HDD failure. If your OS can't reach it's components due to disk corruption it will ultimately damage the OS.
Check event log for entries and clues. Run Sandra stress test (memory, HDD) to see how they hold. Write down all BSOD codes, search MS KB for an error you get. Some may be decoded (not fully though, just hints what caused the STOP) based on 1st and 2nd set of codes after STOP msg.

[fLYtRap]

... and than select safe mode.

Just curious, did the message really contain this grammatical error?

I'm not sure what do you mean. I wrote it as it was on the screen.

[bobkart]

http://news.zdnet.co.uk/itmanagement/0,1000000308,39273376,00.htm

(I'll apologize in advance for being of no help to this thread.)

[fLYtRap]

http://news.zdnet.co.uk/itmanagement/0,1000000308,39273376,00.htm

(I'll apologize in advance for being of no help to this thread.)

Well you could point where exacly is the grammatical error

I don't feel like looking for it...

[bobkart]

There are only five words in what I quoted.

Never mind then. Or should I say than?

[guns1inger]

STOP codes can be helpful, but you have to be able to translate them. These should help narrow things down

http://www.aumha.org/win5/kbestop.php
http://labmice.techtarget.com/windowsxp/TroubleshootingXP/error.htm
http://www.updatexp.com/stop-messages.html

The only specific reference I could find to that error code and file was a german page that suggested that it could be faulty ram.

[GKar]

i'm with redwudz, ram, try reseating the ram module first though. since the error message didn't seem to refer to a video driver, ram would be first choice.

You can also try upping the voltage (+2.5) on the ram in bios if you have that option, it will help stabilize it.

[lacywest]

I've been getting it quite a few times my self.

Two weeks ago ... I blamed it on my USB 2.0 hub and disconnected it and the problem stopped.

But ... the Blue Screen of Death is back ... twice now ... once during the night while at work last night and once really quick after going back into my computer room ... minutes later.

Only thing I could try that was a quick fix ... if that was the problem ... was turn off the ATI Overclocking Tool for my ATI 9800XT video card. For the rest of the day ... so far ... no problems

[Ditka1985]

The stop message you are getting ends with 5E not "SE", as all such messages are coded in hexadecimal.

5E errors are of the variety: "Object Initialization Failed".

Win32k.sys, unfortunately, can show as the module at fault even though there are other causes. However, the most common causes of any Win32k.sys-reported BSOD is RAM, followed by drivers (specifically, video). Other defective hardware can cause this -- including processor and video card.

My recommendation would be to re-seat your RAM (or swap/remove the modules to isolate the problem). Also, I would make sure that your BIOS settings for RAM are correct (in other words, if you are overclocking your RAM, back it down to test).

If you are using a video card that is not integrated with the motherboard, remove and reseat the card. If the driver cannot initialize the card properly (for whatever reason), it will throw a 5E. I would also verify that you've got the latest stable video driver for your card.

Lastly, make sure that you're not overheating the system. Check all the fans for proper operation, and make sure none of your heat sinks have worked their way loose, etc.

[Bjs]

After a quick squizz and research :

WIN32K.SYS is primarily concerned with graphics and user interface tasks .

To locate issue :

1: If your an overclocking egghead , return bios to normal values before carrying out next steps .
2: Rare ... but run memtest (the slots should be cleaned)

3: If all above is fine , but still issue ...

Video adapter (over clocked / heated) or it's drivers are at fault (incompatible)... especially if it appears to be intermittent .

-------------------------

Several programs have been documented by ms to cause similar issue's ... roxio being one .

------------------------

Being a system builder , I never , ever , install those motherboard , vga , tweaking utilities ... they cause plenty of havoc and instability in the uninitiated (no prior over clocking experience) .

[Xylob the Destroyer]

if you call Microsoft customer support, they can tell you exactly what the meaning of the error mesages mean.

*** STOP: 0x000000SE (0xC000000S, 0x8F8F752C, 0xBAA656A4, 0x00000000)

*** win32k.sys - Adress 8F8F752C base at 8F800000, DateStamp 3f73195d

then you will have a definite place to start instead randomly hoping that whatever you're trying is going to fix the problem.

[JohnnyMalaria]

According to Microsoft: (should apply to XP as well as 2000 since XP is part of the 2000 family)

Error Message:
STOP: 0x0000005E (parameter, parameter, parameter, parameter) OBJECT_INITIALIZATION_FAILED

Explanation:
This is a Windows 2000 Executive character-mode STOP message. Phase 0 initialization of the object manager failed. This can only happen during the relatively short period of time that the Windows 2000 Executive is being initialized, during phase 4 of Windows 2000 startup. This might be a hardware problem.

User Action:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

[fLYtRap]

It looks like most people here recommend memory test, so this is what am going to do first.

[grossjamesh]

Where to find more information.

Windows 2000 Pro resource Kit Ch33, pg 1534-1537.

Windows 2000 DDK. Has the documentation on the parameters.

Some of this information is available through public web access, however for really detailed
information you will need to go into MSDN(subscription only).

[fLYtRap]

Where to find more information.

Windows 2000 Pro resource Kit Ch33, pg 1534-1537.

Windows 2000 DDK. Has the documentation on the parameters.

Some of this information is available through public web access, however for really detailed
information you will need to go into MSDN(subscription only).

Windows 2000

I have XP PRO

[Ai Haibara]

XP is actually an upgrade to WinNT/2000.

[Skith]

I had similar behavior, don't recall the exact STOP error message (I threw out my notes), but it was indeed caused by a bad stick of ram. Memtest86 confirmed it within a short period of time. I tested the sticks together and individually. Replacing them fixed everything.

Let us know how it turns out.

[JohnnyMalaria]

XP is actually an upgrade to WinNT/2000.

Internally, Microsoft refer to their NT OSes (i.e., NT kernel) as:

NT 4.0 = 4.0
2000 = 5.0
XP = 5.1
Vista = 6.0

So, actually, 2000 is a major upgrade from NT 4.0 (which didn't have the PnP support that 2000 does). XP is minor upgrade and still within the 2000 family (i.e., 5.x). Vista is a major upgrade from 2000/XP.

[fLYtRap]

How long does this damn memory test takes
Its been running for 20 hours now and it is on 74% pass.

[InXess]

How long does this damn memory test takes
Its been running for 20 hours now and it is on 74% pass.

You specify how long. 20 hrs should be enough. If no errors (vast majority of cases) proceed to other steps (refer to posts).

[nutstoyou]

http://hcidesign.com/memtest/support.html

You should be testing only available ram. 100% coverage should only take around 20mins.

[Nelson37]

Just to save everyone some time -


How many parts in this PC are left over from the one in which you fried the processor?

[fLYtRap]

Just to save everyone some time -


How many parts in this PC are left over from the one in which you fried the processor?

Is this a joke or what
I have no clue how to respond to this question...
Would you be willing to elaborate on this ?

[fLYtRap]

Anyways I finished memory test since I notice after 20 hours that the test passed 29 times

I will just wait for another error and see if those will be the same.

[Nelson37]

you don't remember

"I think I busted cpu and the mobo at the same time and it wasn't a static discharge. I forgot to put cooling fan over the cpu and I power it up and the smoke came out of the socket.
After that screen was black, fans spinning, lights on and hdd was getting power as well. There was no beeps at all in any time.
I though I busted video card as well, so I bought a new card to check it out, but that wasn't a problem and my old card is working great.
When I removed 1394 from the slot computer is shutting down with no problem. I came up with a temp solution and am putting it on stand by and than I power it down with the button. I set the BIOS to default. "

Shall I repeat the question?

[TooLFooL]

you don't remember

"I think I busted cpu and the mobo at the same time and it wasn't a static discharge. I forgot to put cooling fan over the cpu and I power it up and the smoke came out of the socket.
After that screen was black, fans spinning, lights on and hdd was getting power as well. There was no beeps at all in any time.
I though I busted video card as well, so I bought a new card to check it out, but that wasn't a problem and my old card is working great.
When I removed 1394 from the slot computer is shutting down with no problem. I came up with a temp solution and am putting it on stand by and than I power it down with the button. I set the BIOS to default. "

Shall I repeat the question?

now taht's funny!