XPS M1530 BSOD 0x0000008E (0xC0000005, 0x94CC5881, 0x9B08CC04, 0x00000000)

Hi

Hi there
I've decided to upgrade my laptop to 4GB recently. I bought 2xKingston value ram's model: KVR667D2S5K2/4G. Unfortunately since the upgrade took place I am receiving BSOD during windows start.

*** STOP: 0x0000008E (0xC0000005, 0x94CC5881, 0x9B08CC04, 0x00000000)
*** win32k.sys - Adddress 94CC5881 base at 94C00000, DateStamp 45d3cc1d
Collecting data for crasch dump...

Here are my spec's:

XPS M1530 CORE 2 DUO T7250 2.00GHz,800MHz,2M 1
Display 15.4" UltraSharp¿ Widescreen WSXGA+ (1680x1050) TFT
Fingerprint Reader Biometric with BLACK accent
Memory Dual-Channel 2048MB (2x1024) 667MHz DDR2 SDRAM
Hard Drive 160GB SATA (7200rpm)
8xDVD+/-RW Slim Slot-Load Drive
Graphics Card 256MB NVIDIA GeForce Go 8600M GT
Dell Travel Remote control 1
European - Dell TrueMobile 355 internal Bluetooth Module
Intel® Pro Wireless 3945 802.11a/b/g Mini-PCI Card EUR

I'll be very appreciated for any suggestions.
Best regards

 

If you put the old RAM back in, does it still BSOD? If it's fine with old RAM the new RAM is faulty.

 

0x0000008E is usually faulty memory indicator, often accompanied by a PAGED AREA FAULT or similar in the BSOD text.

 

As far I haven't replaced those rams back to the original ones, because the replacement took place only two days ago. I will put the original ones back to check whether the problem still occurs or not (just to make sure). I wrote an email to Kingston technical support. 'Will see what they have to say about this. I will get back to you as soon as I'll receive a feedback from them. Thanks for suggestions.

 

zwitek
The MS site said this:

SYMPTOMS
When you install Microsoft Windows XP, you may receive a Stop Error message that is similar to one of the following while the Setup program is running:
STOP 0x0000008e
STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA
Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then you run the Setup program, you may receive an error message that is similar to the following:
Setup cannot copy the file Setupdd.sys.

Back to the top
CAUSE
This behavior may occur if one of the following conditions is true:
• One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
• The RAM configuration is incompatible with Windows XP.

Back to the top
RESOLUTION
To troubleshoot this behavior, follow these steps:
1. Remove some of the memory modules that are installed on the computer. Leave at least the RAM that is required for the computer to start and run Windows XP.

The recommended RAM to run Windows XP is 128 megabytes (MB). The minimum is 64 MB, and the maximum is 4 gigabytes.

For example, if two 256-MB memory modules are installed on your computer, remove one of the memory modules.
2. Restart your computer, and then run the Setup program:
a. Insert the Windows XP Setup CD-ROM in the CD-ROM drive, start the computer, and then click OK to select the first option screen to install a copy of Windows XP.
b. Click Accept, and then follow the instructions on the screen to complete the Windows XP installation.
3. If you again receive the error message that is mentioned in the "Symptoms" section, go to step 4.
4. Remove a different memory module, or install the RAM in a different memory slot.
5. Restart your computer, and then rerun Setup.

You may have to restart your computer several times to identify the specific memory modules that are not working correctly.

 

Thanks, I will check the chips as a seperate modules

 

Hi
I think I might have found the solution.
I've tryied to test every single chip as a separate module. The test was unsuccesful. I decided to swich to the old rams (the ones I received with my notebook as they had been working properly). Unfortunately it turned out that even the old ones were not working (still the same BSOD). I tryied to run the build-in dell test feature (Fn+power_button). After an hour of tests I haven't received any error which could confirm the memory failure. Next I've called my attention on two facts:
1. every BSOD accoured a tiny moment before the windows logon screen
2. after every reboot follwing the BSOD I've been receiving a windows diagnostic massage suggesting that the last problem was caused by windows itself
Next I've realized, that recently I had installed a software called WindowsBlinds. At first it was just a blind thought, but I've decided to go for it. I uninstalled it. Since than and as far I haven't seen any similar BSOD again. As this solution is rather unexpected I haven't decided to call it a final. I will keep observe my system and get back to you as soon something occure.
Thanks

 

great!!!!!!

that's what we like to hear.......