BSOD at startup

[marcusedvalson]

I am really hoping someone can help me with this problem that started last night.
I have a Dell M1530 Dual Core 2.4 Ghz, 4gb Ram, Nvidia 8600M Graphics card.
On startup, I recieve a BSOD. I restarted in safe mode and got the following report, which I submitted and there was no solution from microsoft:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 81CF5886
BCP3: 8D19F8DC
BCP4: 00000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Ive attached the contents of the DMP file to this thread. I have done some reading around, and some people seem to think this is a driver problem, or a hardware/software change. The strange thing is, I haven't made any hardware, software or driver changes in the past weeks. The problem occurred out of the blue (no pun intended). Last night, I panicked and did a system restore to Tuesday (before the problem occurred). It seemed to work last night, but starting up this morning, I got the same problem. Does anyone have any ideas on what might be able to fix it? Any help is very very much appreciated.

Thanks!

 

[dmex]

Hey Marcusedvalson,

Here are the details for BCCode: 1000008e

Bug Check 0x8E:


The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This bug check indicates that a kernel-mode application generated an exception that Windows did not catch.

Cause
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check is a very common bug check, you must identify which exception was generated after the 0x8E code.
Common exception codes include the following:

• 0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates that an unaligned data reference was encountered.
• 0x80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
• 0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred.

Resolving the Problem
use some basic troubleshooting techniques:

• Make sure you have enough disk space.
• If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
• Try changing video adapters.
• Check with your hardware vendor for any BIOS updates.
• Disable BIOS memory options such as caching or shadowing.

If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the computer was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that the computer is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame supplies additional information.

If you do not know the specific cause of the exception, consider the following items:

* Hardware incompatibility. Make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
* Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If the bug check message lists a driver by name , disable or remove that driver. Also, disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the system by using the Recovery Console and then deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the BSOD. You can disable memory caching of the BIOS to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies.

Another possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation.
You can resolve BIOS problems by upgrading the system BIOS version.

Steven

 

[marcusedvalson]

Ok, I looked through the stuff you posted, and I then followed the recommendation to run a memory test. I ran the windows memory diagnostics tool, which rebooted my machine, and ran through the tests. I noticed that it said that there was a memory problem at like 10% through the test. The test finished and it then gave me an error that windows would not start, it listed the unexpected error encountered as: 0xC0000017. One of the options on the menu was boot windows vista. That didnt work, so I pressed escape. It ran back through the bios startup and windows started. Ok, great. I logged into windows, and it didnt give me the popup message from windows diagnostics tool. It didnt tell me anything. Does it save a log file anywhere that I can look at to help diagnose the problem? I assume it is a RAM problem, and I need to get it replaced, but I want to know the particulars, so I can communicate with Dell more effectively. Does anyone have any recommendations for me?

Thanks!

 

[marcusedvalson]

To anyone else that ends up searching for this problem and ends up on a forum page like I did, I updated my bios, and it seemed to fix all the problems I was having.

 

[dmex]

To anyone else that ends up searching for this problem and ends up on a forum page like I did, I updated my bios, and it seemed to fix all the problems I was having.

Good to hear that solved the problems

Steven