Constant BSOD's on win32k.sys - HELP!

[Guest]

This just started out-of-the-blue as far as I can tell... All of a sudden, my
laptop started experiencing constant BSOD's on file win32k.sys, sometimes
while doing activities in programs, other times while typing in the password
for a username, others while the machine just sits there idle!

The machine is being rendered unusable, and I can't get any work done!
Please, can someone help?!

 

[Will Denny]

Hi

Could you please post the Stop Code from one of the BSODs?

--


Will Denny
MS-MVP Windows Shell/User
Please reply to the News Groups

 

[Guest]

Hi Will,

I was unable to give you a stop code, as the machine almost instantly
reboots after the BSOD appears, which btw, after the reboot, stalls on the
Windows XP screen. The machine cannot be rebooted unless its a cold-boot.

However I did find this message in my System Event log:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 11/01/2005
Time: 1:01:25 AM
User: N/A
Computer: DELLCPIR
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf8287c5, parameter3
f5548c90, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 32 38 37 63 35 bf8287c5
0040: 2c 20 66 35 35 34 38 63 , f5548c
0048: 39 30 2c 20 30 30 30 30 90, 0000
0050: 30 30 30 30 0000

Hopefully that might be helpful, and I will continue to attempt to write
down the stop code on the next BSOD, which shouldn't take too long.

Edison

 

[Will Denny]

Hi

Please see if the following helps:

http://www.eventid.net/display.asp?eventid=1003&source=System+Error

--


Will Denny
MS-MVP Windows Shell/User
Please reply to the News Groups

 

[Guest]

Hi Will,

I was able to write down this stop code while trying to boot the machine
into Safe Mode with Networking:

STOP: 0x000000A5 (0x00000011, 0x00000006, 0x00000000, 0x00000000)

The screen mentioned something about the system BIOS not being fully ACPI
compliant, however I know it is, and this is the first time Windows has shown
this error. The machine itself is a Dell Latitude CPi-R400GT notebook.

I've also run the Dell Latitude Diagnostics program on the hardware (all in
extended mode) and it found no errors with any of the hardware, including the
system RAM (Micron), or the HD (brand new Toshiba 30GB).

Edison

 

[Plato]

This just started out-of-the-blue as far as I can tell... All of a sudden, my
laptop started experiencing constant BSOD's on file win32k.sys, sometimes
while doing activities in programs, other times while typing in the password
for a username, others while the machine just sits there idle!

Sometimes caused by a new app you've recently installed and set to run
24/7. Sometimes caused by ram that has just gone bad.

 

[Guest]

Hi Plato,

I actually managed to get it to BSOD on me without the message disapearing,
and it brought up a STOP code 0x0000001a, which according to MS indicates
defective RAM. I removed the chip in DIMM bank A and the machine started
working perfectly again, albeit somewhat slower.

Thankfully the chip is a Kingston chip with lifetime warantee, so I can get
the problem fixed with no cost to me. Thanks again for all the help here from
you and Will.

Edison

 

[Plato]

I actually managed to get it to BSOD on me without the message disapearing,
and it brought up a STOP code 0x0000001a, which according to MS indicates
defective RAM. I removed the chip in DIMM bank A and the machine started
working perfectly again, albeit somewhat slower.

Some ram has this nasty habit of working perfectly for a year, then it
takes a hike. Odd.

 

[Malke]

(snip)

Hello Edison, I can see why you are no longer available online in MSN

To "foody" - WTF?

To Edison - Write down the Stop Error and research it here:

http://www.aumha.org/win5/kbestop.htm

I'd also test your RAM. I like Memtest86+ from www.memtest.org.
Obviously, you have to get the program from a working machine. You will
either download the precompiled Windows binary to make a bootable floppy
or the .iso to make a bootable cd. If you want to use the latter, you'll
need to have third-party burning software on the machine where you
download the file - XP's built-in burning capability won't do the job.
In either case, boot with the media you made. The test will run
immediately. Let the test run for an extended period of time - unless
errors are seen immediately. If you get any errors, replace the RAM.

Malke