Hi,
**Results verified by WinDBG, DumpCHK, and BlueScreenView.**The BugChecks were 0A (5), 1A, and 7E.
0A CAUSE was BlueToothUsb_w764.sys - update the BIOS (you have), low level chipset
drivers, and other on-board drivers - especially anything relating to USB and BlueTooth.
Memory and malware could also be involved in the issue so check those thoroughly using
the methods in the troubleshooter and/or below.
BugCheck A, {10, 2, 0, fffff800028276a9}
Probably caused by : BlueToothUsb_w764.sys ( BlueToothUsb_w764+3b839 )
FAILURE_BUCKET_ID: X64_0xA_BlueToothUsb_w764+3b839
BUCKET_ID: X64_0xA_BlueToothUsb_w764+3b839
1A CAUSE was a Windows component which means something else drove it into Fault.
A BlueTooth Process was running though no indication of the root cause. See the trouble-
shooter for methods to try to solve the issue.
7E CAUSE btcusb.sys - look updates to the BlueTooth and USB drivers.
You need to add adequate antivirus/antispyware protection - see the recommendations
in the reply below.
======================================================================
Check this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueScreens - top 3 methods (+1 other).
http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990
BCCode: 0A 0x0000000A
Check these KB's
Error message on a blue screen on a computer that is running Windows 7 or Windows Server
2008 R2: "STOP: 0x0000000A"
http://support.microsoft.com/kb/979444
Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and
that has iSCSI storage: "0x0000000A"
http://support.microsoft.com/kb/979711
Those and 5 other KB Articles are available
http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000000A&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10
Drivers could be at fault however disk issues or antivirus/antispyware/security products are
just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.
The video driver or something affecting it would be very suspect.
Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking
at the System maker and device makers's sites.
Below I will post a generic bluescreen troubleshooter and in the next message how to update
drivers and BIOS as well as do memory checks.
BCCode: 0A 0x0000000A
Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS
- Restart your computer.
- Press F8 at the character-based menu that displays the operating system choices.
- Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
- Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
- Try disabling memory caching of the BIOS.
- Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
- Make sure the latest Service Pack is installed.
- If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming
proper termination.
- For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.
Comments
Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.
BCCode: 0A 0x0000000A <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-\*1025.html
==================================================================
BCCode: 1a 0x0000001aRemove ALL power and reseat all cards, memory, and cables (both ends when possible) -
actually remove and replace - do not just snug. Make sure the vents are clear and that the
fans are working. Even though the temp is OK do not assume heat can't affect the video,
sound or other system functions it those get to hot. Try adding a small fan blowing into
the vents as a test. (Those are mostly for a PC not a laptop.)
Have you added any hardware lately? Have you updated any driver just before these started?
(Check Control Panel - Windows Updates to see if any drivers were updated there about the
time this started) Main likely culprits are Video driver, other major drivers, memory, and
antivirus/antispyware/security products could be at fault as well as drive issues.
Use the troubleshooter below and refer to the next message for drivers and memory when
you get to those sections and then return back to the troubleshooter as needed.
BCCode: 1a 0x0000001a <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/MEMORY-MANAGEMENT-0x0000001A-\*1041.html?order=votes
==================================================================
BCCode: 7E 0x0000007E which is also 0x1000007E
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
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:
- 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 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
==================================================================
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
Also do this so you can see the likely bluescreens.
Windows Vista automatically restarts if your PC encounters an error that causes it to crash.
http://www.winvistatips.com/disable-automatic-restart-t84.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 Information
BlueScreenView 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
How to Install a Device Driver in Vista Device Manager (also Windows 7)
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
