Share via

Blue Screen, Bugcheck code: 0x1000007E, Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Anonymous
2011-01-13T14:22:29+00:00

ORIGINAL TITLE:  I get BSOD.HELP HELP HELP!

 I get BSOD

On Thu 1/13/2011 1:08:22 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\011411-12558-01.dmp

This was probably caused by the following module: cdrom.sys (cdrom+0x13DD6)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF88C13DD6, 0xFFFFFFFF8AB97948, 0xFFFFFFFF8AB97520)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\cdrom.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: SCSI CD-ROM Driver

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 1/13/2011 1:08:22 PM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF88C13DD6, 0xFFFFFFFF8AB97948, 0xFFFFFFFF8AB97520)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .

Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

I formatted pc,i installed all windows updates,i installed all the latest drivers for my pc,i jst dnt know what the problem is now.

Is it my nod32 antivirus real time file system protection?

Some one help me plz

My computer specs are Nvidia 9500gt graphics card,2gbdd3 ram,amd athlon ii x4 2.6ghz,500gb disk.Bios are fully updated,i dno whats up anymore.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
  1. Anonymous
    2011-01-15T07:39:42+00:00

    Hi,

    Results verified with WinDBG, DumpCHK, and BlueSceenView.

    1. That is a horrible file sharing site, can make you wait 30 minutes to download. Please find another

    one or use the SkyDrive (see link auggy mentioned).

    1. The Bug_Checks were c0000221 and 7E.

    The CAUSE of 7E was cdrom.sys which is a very unusual cause and is a Window component meaning

    something else drove it into fault.

    The other c0000221 is also unusual for a fresh installation of Windows.

    Remove ALL power and reseat the cards, memory, and cables (on both ends when possible) - actually

    remove and replace - do not just snug. Clean out the dust bunnies and make sure the vents are clear.

    This is often hardware related. Check the memory thoroughly.

    Crash List - Created by using BlueScreenView

    Dump File Crash Time Dump File Size Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version
    011411-12558-01.dmp 1/14/2011 2:09:00 AM 131,072 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x88c13dd6 0x8ab97948 0x8ab97520 cdrom.sys cdrom.sys+13dd6 SCSI CD-ROM Driver Microsoft® Windows® Operating System Microsoft Corporation 6.0.6002.18005 (lh_sp2rtm.090410-1830) 32-bit C:\Windows\Minidump\011411-12558-01.dmp 4 15 7600
    011411-14679-01.dmp 1/14/2011 8:17:22 PM 135,440 0xc0000221 0x8991c508 0x00000000 0x00000000 0x00000000 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.0.6002.18267 (vistasp2_gdr.100608-0458) 32-bit C:\Windows\Minidump\011411-14679-01.dmp 4 15 7600

    Check these KB articles :

    "Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server

    2008 R2

    http://support.microsoft.com/kb/979538

    "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU is under

    heavy load conditions in Windows 7 or Windows Server 2008 R2

    http://support.microsoft.com/kb/983615


    See this thread for information on using BlueScreenView, MyEventViewer, and other methods to

    troubleshoot BlueScreens - top 3 replies (+1 other).

    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990


    References to Vista also apply to Windows 7.

    This error is usually a driver issue and display adapter (video) driver is the most suspect though it

    could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues

    can also cause the error. When you get to the driver section of the troubleshooter use my generic

    methods in the next message and then return to the troubleshooter if needed.

    Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows

    Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-

    spyware/security programs.

    When you get to the driver and memory sections of the troubleshooter refer to the next message to

    update drivers and test memory and then refer back to the troubleshooter if needed.

    BCCode: 7E      0x0000007E  which is also 0x1000007E

    Cause

    The SYSTEM_THREAD_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:

    • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

    For a complete list of exception codes, see the Ntstatus.h file that is located in theinc directory of

    the Microsoft Windows Driver Kit (WDK).

    Resolving the Problem

    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 system

    was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly,

    make sure that a kernel debugger is connected and the system 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 issues:

    • Hardware incompatibility*.* Make sure that any new hardware that is 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 a driver is listed by name within the bug check message, disable or remove that driver. 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 must 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 computer

    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 0x7E.

    You can also disable memory caching of the BIOS might 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.

    BCCode: 7E    0x00000007E  which is also 0x1000007E <-- read this link

    http://www.faultwire.com/solutions-fatal\_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-\*1141.html?order=votes


    0xc0000221

    Unknown Hard Error Ntdll.dll Error Resolution

    http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm

    Sony - NTDLL.DLL errors

    http://www.custcenter.com/cgi-bin/sonypictures.cfg/php/enduser/std\_adp.php?p\_faqid=4276&p\_created=1217370595&p\_topview=1

    Check there and you can use Safe Mode - repeatedly tap F8 as you boot - Last Known Good Configuration

    and maybe even System Restore back to a point before this happened. If no luck follow the guidelines in

    the link above.

    0xc0000221  <-- read this linkhttp://www.faultwire.com/solutions-fatal_error/STATUS-IMAGE-CHECKSUM-MISMATCH-0xC0000221-*1316.html?order=votes

    ===============================================================

    Look in the Event Viewer to see if anything is reported about those.

    http://www.computerperformance.co.uk/vista/vista\_event\_viewer.htm

    MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.

    http://www.nirsoft.net/utils/my\_event\_viewer.html

    Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info

    that would help. Such as the BCC and the other 4 entries on the lower left. And any other error

    information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

    As examples :

    BCCode: 116

    BCP1: 87BC9510

    BCP2: 8C013D80

    BCP3: 00000000

    BCP4: 00000002

    or in this format :

    Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)

    tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

    This is an excellent tool for posting Blue Screen Error InformationBlueScreenView scans all your minidump files created during 'blue screen of death'crashes, and displays the information about all crashes in one table - Freehttp://www.nirsoft.net/utils/blue\_screen\_view.html

    Many BlueScreens are caused by old or corrupted drivers, especially video drivers however

    there are other causes.

    You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or

    Recovery Options if your system has that installed by the maker.

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    You can try a System Restore back to a point before the problem started if there is one.

    How to Do a System Restore in Windows 7

    http://www.sevenforums.com/tutorials/700-system-restore.html


    Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

    Enter this at the prompt - sfc /scannow

    How to Repair Windows 7 System Files with System File Checker

    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program

    generates in Windows Vista cbs.log (and Windows 7)

    http://support.microsoft.com/kb/928228

    The log might give you the answer if there was a corrupted driver. (Does not tell all the possible

    driver issues).

    Also run CheckDisk so we can rule out corruption as much as possible.

    How to Run Check Disk at Startup in Windows 7

    http://www.sevenforums.com/tutorials/433-disk-check.html


    Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party

    keyboard and mouse, as well as other major device drivers.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.

    http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

    Installing and updating drivers in Windows 7 (updating drivers manually using the methods above

    is preferred to ensure the latest drivers from System maker and Device makers are found)

    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

    How To Disable Automatic Driver Installation In Windows Vista - Drivers

    http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

    http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx


    How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart

    unexpectedly

    http://support.microsoft.com/kb/958233

    Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)

    http://www.chicagotech.net/vista/vistabluescreen.htm

    Understanding and Decoding BSOD (blue screen of death) Messages

    http://www.taranfx.com/blog/?p=692

    Windows - Troubleshooting Blue Screen Errors

    http://kb.wisc.edu/page.php?id=7033


    In some cases this might be required.

    StartUp Repair from Recovery Options or Windows 7 disk

    How to Run a Startup Repair in Windows 7

    http://www.sevenforums.com/tutorials/681-startup-repair.html

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    How to Create a Windows 7 System Repair Disc

    http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

    How to Do a Repair Install to Fix Windows 7

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    Hope this helps.


    Rob Brown - Microsoft MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

    0 comments No comments

7 additional answers

Sort by: Most helpful
  1. Anonymous
    2011-01-14T08:40:19+00:00

    hey guys since i just formatted pc ive crashed like 2 times within the last 2 days.these are the only dump files i got for now and here is the download link.

    And whats clean boot state?dies he mean safe mode?

    http://www.easy-share.com/1913553789/Minidump.rar

    0 comments No comments
  2. Anonymous
    2011-01-14T04:54:43+00:00

    Also, can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

    0 comments No comments
  3. Anonymous
    2011-01-13T15:25:36+00:00

    Hi,

    Quick Action Plan

    1. Restart the computer and keep tapping the F8 key
    2. You would see an Advanced Boot Options screen
    3. Choose the option of "Safe Mode"
    4. Once you are able to login, Click Start > Right Click on Computer > Properties
    5. In the System Properties window, click on Device Manager on the top right
    6. When the Device Manager opens up, expand "Optical Drive" and then Right Click on the CD-ROM and then Disable
    7. Restart the computer and check if your problem is resolved

    If not, then you might have to get the drivers of your CD-ROM updated or force them to use generic drivers provided by Microsoft.

    The problem can be resolved and the error message viewed above is because of Windows Updates.

    This would involve intensive troubleshooting which I can certainly mention but would be very difficult to follow. I would recommend you to call up Microsoft Technical Support and get a Service Request generated free of cost, since the problem is because of Windows Updates. Microsoft provides free support to issues caused because of Windows Update.

    The number for Microsoft Technical Support is 1800-936-5700 (United States and Canada). If you are located outside this location, try searching a number for your region onwww.bing.com


    Saurabh Yadav | *** Email address is removed for privacy ***

    0 comments No comments
  4. Anonymous
    2011-01-13T15:21:11+00:00

    Hello,

    Little suggestion, did you try to boot in clean state mode to see if this resolves the problem? If yes, then it might be a conflicting driver or software causing this.

    Since when are you getting this? Did you make any changes to your system before getting this?

    Might also be a hardware problem not a software problem.

    Hope these suggestions will help you,

    Regards,

    Andrew


    Always 'Vote as helpful' for those who helped and 'mark as answer' if the info helped you in a sort of way. Thanks

    0 comments No comments