Share via

BSOD - BCCode: 1000007e

Anonymous
2014-06-07T23:18:07+00:00

I have been getting constant blue screens from what I think is a faulty driver or something just going wrong. I had a malfunctioning video card so I sent my computer in and now I got it back, but I still get BSOD sometimes.

Things I have done already:

-Memtest

-Checkdisk

-Virus Scan

-Driver update (I actually need to install new drivers but for some reason AMD isn't working)

-Windows updates (I have 1 important update not installed, but I am not sure if it the root cause of the BSOD)

Things I have NOT done:

-Uploaded or checked Dump files (I can't get it to work)

-Viewed system logs

Overall this whole computer process has been very messy and frustrating, and and all help would be appreciated. Thanks.

Additional Information:

(This is the event error code that resulted in a BSOD)

Log Name:      Application

Source:        Microsoft-Windows-WMI

Date:          6/7/2014 5:01:05 PM

Event ID:      10

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      user-PC

Description:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />

    <EventID Qualifiers="49152">10</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-06-07T22:01:05.000000000Z" />

    <EventRecordID>2540</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>user-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>//./root/CIMV2</Data>

    <Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99</Data>

    <Data>0x80041003</Data>

  </EventData>

</Event>

(This is the windows response)

Problem signature:

  Problem Event Name: BlueScreen

  OS Version: 6.1.7601.2.1.0.768.3

  Locale ID: 1033

Additional information about the problem:

  BCCode: 1000007e

  BCP1: FFFFFFFFC0000005

  BCP2: FFFFF800028D9B80

  BCP3: FFFFF88003376DC8

  BCP4: FFFFF88003376620

  OS Version: 6_1_7601

  Service Pack: 1_0

  Product: 768_1

Files that help describe the problem:

  C:\Windows\Minidump\060714-42229-01.dmp

  C:\Users\user\AppData\Local\Temp\WER-83101-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

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

Anonymous
2014-06-08T09:15:14+00:00

Smitty64

In addition to the excellent advice already offered. please refer to the link below fo additional troubleshooting steps.

Log Name:      Application

Source:        Microsoft-Windows-WMI

Date:          6/7/2014 5:01:05 PM

Event ID:      10

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      user-PC

Description:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

*Resolution* See link.

Event ID 10 is logged in the Application log after you install  Service Pack 1 for Windows 7 or Windows Server 2008 R2.

http://support.microsoft.com/kb/2545227/en-us

Was this answer helpful?

0 comments No comments

Answer accepted by question author

Anonymous
2014-06-07T23:28:01+00:00

Hi,

Definitely contact whoever serviced your computer because they definitely did not check

it out carefully enough and this may be hardware. Regardless they should have resolved

the issues before returning the unit.

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


Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

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

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

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

We can analyze the minidumps if you make them available from the OneDrive or other file

sharing sites (such as MediaFire). If you have problems uploading the minidumps copy

them to the Desktop or the Documents folder and upload them from there.

Adding files to your OneDrive

http://windows.microsoft.com/en-us/windows-8/getting-started-onedrive-tutorial

One-Drive - Share files and folders and change permissions

http://windows.microsoft.com/en-us/onedrive/share-file-folder

Zip or upload the contents of C:\Windows\minidump

Use OneDrive to upload collected files

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


References to Vista also apply to Windows 7.BCCode: 7E      0x0000007E  which is also 0x1000007EThis 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 SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDThe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

Important Info If You Have Received a STOP CodeIf you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

These actions might prevent an error like this from happening again:

  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Parameters

The following parameters appear on the blue screen.

CauseThe 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:

  • 0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
  • 0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
  • 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 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 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 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 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 

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

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 stop Windows 7 automatically installing drivers

http://support.microsoft.com/kb/2500967/en-us


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 <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-06-07T23:28:40+00:00

    Hi,

    References to Vista also apply to Windows 7.

    This is my generic how to for proper driver updates : (Check for BIOS and driver

    updates.)

    This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW

    to Hide Microsoft drivers - update those without Dump in their names. (Also update

    the BIOS and chipset drivers.)

    DriverView - Free - utility displays the list of all device drivers currently loaded on

    your system. For each driver in the list, additional useful information is displayed:

    load address of the driver, description, version, product name, company that

    created the driver, and more.

    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the

    most current. Control Panel - Device Manager - Display Adapter - write down the

    make and complete model of your video adapter - double click - Driver's tab -

    write down the version info. Now click UPdate Driver (this may not do anything

    as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this

    will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

    if 3rd party with their own software and drivers and any other major device drivers

    you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback)

    and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get

    their latest versions. (Look for BIOS, Chipset and software updates at System

     Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

    REBOOT after each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are

    installing actually shows up. This is because some drivers rollback before the

    latest is installed (sound drivers particularly do this) so install a driver - reboot

    • check to be sure it is installed and repeat as needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR

    SCANNER - check manually by model.

    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

    If you update drivers manually then it is a good idea to disable Driver Installations

    in Windows Updates, this leaves Windows Updates ON however it will not install

    drivers which will usually be older and cause issues. If Updates suggests a new

    driver then HIDE it (Right Click on it) and then go look for new ones manually if

    you wish.

    How to stop Windows 7 automatically installing drivers

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

    Stop Windows 7 from Automatically Installing Device Drivers

    http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

    How To Disable Automatic Driver Installation In Windows 7 / Vista

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

    Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for

    Professional, Ultimate, and Enterprise)

    http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

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

    Memory tests do not catch all errors such as mismatched memory (possible

    even for sticks that appear to be identical) and when faster memory is placed

    in system behind slower  memory. So it is best to also swap sticks in and out

    to check for those even if all memory tests fail to show a problem.

    To test RAM check here - let it run 4+ hours or so.  <-- best methodwww.memtest.org

    For the Vista/Windows 7 Memory Diagnostic Tool

    Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list

    • Right Click - RUN AS ADMIN follow the instructions

    How to Run the Memory Diagnostics Tool in Windows 7

    http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-07T23:27:49+00:00

    Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments