locked
Please help with BSOD RRS feed

  • Question

  • This has happened several times over the past few days. Please help, hopefully this info will help you help me!!!

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    12/25/2012 12:21 AM

    Status
    Not Reported

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

    Files that help describe the problem (some files may no longer be available)
    Mini122512-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 828CBF50
    BCP3: A50FB60C
    BCP4: 00000000
    OS Version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1

    Tuesday, December 25, 2012 6:07 AM

All replies

  • Sorry for not stating already, this is on windows vista
    Tuesday, December 25, 2012 6:16 AM
  • First lets test what hardware we can.
     
    Standard Hardware Troubleshooting
     
    S.M.A.R.T
     
    Click Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator.
     
    Disk drives in Windows monitor themselves for impending failure. The feature is called S.M.A.R.T. It will detect impending failure 30% of the time. In an elevated command prompt type
    wmic /namespace:\\root\wmi PATH MSStorageDriver_FailurePredictStatus get active,predictfailure,reason /format:List 
    If it's on Active will be true, if not on turn it on in the computer's BIOS.
     
    Predict Failure should be False if everything's ok.
     
    In Vista and later if SMART predicts failure Windows prompts the user to run Backup.
     
    Run Chkdsk
    In Computer right click your drives and choose Properties, then Tools tab,
    then click Check Now. Tick BOTH checkboxes then Start. Reboot. This will
    take overnight.

    Sfc
    Check for file  corruption by clicking Start - All Programs - Accessories - Right click
    Command Prompt and choose Run As Administrator. Type

    sfc /scannow

    Memory Diagnostic
    If you haven't run a memory diagnostic then please do so. Click Start - Control Panel - choose Classic View in left hand pane - choose Administrative Tools -  then Memory Diagnostics Tool.

    For Chkdsk Results
    Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at both the Application and System logs (under Windows Logs) for entries.
     
    Look for EventID is 7 and Source is Disk
    Look for EventID is 11 and Source is Disk
    Look for EventID is 51 and Source is Disk
    Look for EventID is 52 and Source is Disk
    Look for EventID is 55 and Source is NTFS
    Look for EventID is 130 and Source is NTFS
    Look for EventID is 1001 and Source is Autochk
    Look for EventID is 1001 and Source is Winlogon
    Look for EventID is 1001 and Source is WinInit
    Look for EventID is 1001 and Source is Chkdsk
    Look for EventID is 26212 and Source is Chkdsk
     
    Double click the entry for details on that entry.
     
    P.S. 7 and 55 are the auto repair codes where windows repairs disk errors silently on the fly. 52 is the SMART warning.
     
    For SFC Results
    Check for file  corruption by clicking Start - All Programs - Accessories - Right click
    Command Prompt and choose Run As Administrator. Type
    findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more
    This will see which files are corrupted. We may be able to copy them from another computer.
     
    For Memory Diagnostic
    Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at both the Application and System logs (under Windows Logs) for entries.
     
    Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-Results
     
    Double click the entry for details on that entry.

    --
    .
    --
    "Stephen Smelski" wrote in message news:518630dc-1f69-4b34-ad5b-dace96c54ce4...

    This has happened several times over the past few days. Please help, hopefully this info will help you help me!!!

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    12/25/2012 12:21 AM

    Status
    Not Reported

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

    Files that help describe the problem (some files may no longer be available)
    Mini122512-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 828CBF50
    BCP3: A50FB60C
    BCP4: 00000000
    OS Version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1


    David Candy
    Thursday, December 27, 2012 10:43 PM
  • 1000008e errorsarethe same as 0000008e errors.
     

    Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

    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 the error handler did not catch.

    Parameters

    The following parameters appear on the blue screen.

    Parameter Description

    1

    The exception code that was not handled

    2

    The address where the exception occurred

    3

    The trap frame

    4

    Reserved

     

    Cause

    The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.

    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.

    For a complete list of exception codes, see the Ntstatus.h file that is located in the inc directory of the Microsoft Windows Driver Kit (WDK).

    Resolution

    If you are not equipped to debug this problem, you should 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 you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.

    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 a kernel debugger is connected and 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 that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

    • 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 bug check 0x1E. 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. For more information about these procedures, see the owner's manual for your computer.

    The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A 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.


    --
    .
    --
    "Stephen Smelski" wrote in message news:518630dc-1f69-4b34-ad5b-dace96c54ce4...

    This has happened several times over the past few days. Please help, hopefully this info will help you help me!!!

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    12/25/2012 12:21 AM

    Status
    Not Reported

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

    Files that help describe the problem (some files may no longer be available)
    Mini122512-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 828CBF50
    BCP3: A50FB60C
    BCP4: 00000000
    OS Version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1


    David Candy
    Thursday, December 27, 2012 10:45 PM
  • If you want to analyse your own dump files. (C:\windows\Minidump).

    Download and install Debugging Tools for Windows
    http://msdn.microsoft.com/en-us/windows/hardware/hh852363
    Install theWindows SDK but just choose the debugging tools.

    Create a folder called Symbols in C:\

    Start Windbg. File menu - Symbol File Path and enter
    srv*C:\symbols*http://msdl.microsoft.com/download/symbols

    Close and reopen WinDbg. File menu - Open Crash Dump

    This will analyse the crash dump. You need to close and reopen WinDbg for
    each dump file analysed. Because you are downloading symbols from the
    internet WinDbg will appear to be doing nothing. But it's downloading. Be
    patient.
     
    You are looking for a driver or system library that the crash occurred in at the end of the listing. Find the file, right click then Properties - Details tab. You'll need to update the driver identified.

    Type in theWinDbg command prompt

    !analyze -v
    -v stands for Verbose and if the crash was originated by a program, as opposed to hardware or a driver, it will appear in the middle of the listing.

    Or upload the minidump files to your Public folder on Skydrive and copy the link from the address bar and I'll analyse them.
     
    Skydrive is Microsoft's Windows Live file upload site at https://skydrive.live.com/.  Read about it at http://explore.live.com/skydrive.

    If you have downloaded any of the Live applications or have a web based Live
    mail account you already have access to your Skydrive.

    Put your event list in the Public folder and copy the link from the address bar.


    --
    .
    --
    "Stephen Smelski" wrote in message news:518630dc-1f69-4b34-ad5b-dace96c54ce4...

    This has happened several times over the past few days. Please help, hopefully this info will help you help me!!!

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    12/25/2012 12:21 AM

    Status
    Not Reported

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

    Files that help describe the problem (some files may no longer be available)
    Mini122512-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 828CBF50
    BCP3: A50FB60C
    BCP4: 00000000
    OS Version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1


    David Candy
    Thursday, December 27, 2012 10:54 PM
  • To See if a Fix is Available

    In Control Panel (and select Classic view in the left hand pane) choose Problem Reports and Solutions (type problem in Start's search box), go to Problem History, right click your error and choose Check For Solution. You may also right click and choose Details for more info. Post those details here.

    To See if a Recent System Change Caused It

    In Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then choose Reliability and Performance Monitor and choose Monitoring Tools then Reliability Monitor (type Reliability in search on Start) . This list is a chart of software installs, uninstalls, Windows updates, and crashes by date (scroll left to see earlier dates). See if your crashes started happening after you installed or uninstalled something.


    --
    .
    --
    "Stephen Smelski" wrote in message news:518630dc-1f69-4b34-ad5b-dace96c54ce4...

    This has happened several times over the past few days. Please help, hopefully this info will help you help me!!!

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    12/25/2012 12:21 AM

    Status
    Not Reported

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

    Files that help describe the problem (some files may no longer be available)
    Mini122512-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 828CBF50
    BCP3: A50FB60C
    BCP4: 00000000
    OS Version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1


    David Candy
    Thursday, December 27, 2012 11:44 PM