Windows 7 Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL when plugging in any USB Bluetooth Dongle

[Jhon Shaw]

HI I hope someone can help. Im so frustrated right now. Im trying to use a Trendnet TBW-150UB dongle and every time i plug it in it BSODs. I have tried another dongle (JabraA320s) and get the same result.

Ive gone in to view hidden entries in Device manager and cleared those out. I've reinstalled all the USB stuff as well. Updated all my drivers, Manually displaced all the usb driver files so fresh ones would install. Downloaded the latest drivers from Trendnet that are for Vista (Im running 7 64bit). Ive disabled the Wifi card and sound card but none of this has worked. Below are the most recent error logs from WhoCrashed. Thank you for any help.

[FONT=Segoe UI, Arial]On Mon 7/22/2013 8:21:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-80593-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cmudax3.sys[/FONT] (0xFFFFF88007231FB7)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88007231FB7)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\cmudax3.sys
product: [FONT=Segoe UI, Arial]C-Media Audio Driver (WDM)[/FONT]
company: [FONT=Segoe UI, Arial]C-Media Inc[/FONT]
description: C-Media Audio WDM Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: cmudax3.sys (C-Media Audio WDM Driver, C-Media Inc).
Google query: [FONT=Segoe UI, Arial]C-Media Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/22/2013 6:49:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-69437-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80048F2038, 0xB6000000, 0x181)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/22/2013 5:57:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-73656-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003296A0F, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/22/2013 5:08:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-70015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/22/2013 4:38:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-65812-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0x0, 0xD, 0x1, 0xFFFFF800032710D0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]

 

[Jhon Shaw]

This is the latest BSOD after physically removing the soundcard from the equation. Onboard sound, lan and video are all disabled in the bios. All that is left are 2 sticks of ram, PCIe nvidia video card, wifi PCI card and a sata HDD

[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/22/2013 11:49:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-73062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0x3, 0x2, 0x1, 0xFFFFF8000329175D)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]

 

[usasma]

Please provide this information so we can provide a complete analysis: Link Removed

Be sure that you have the latest drivers installed for the TrendNet dongle
Try the dongle on another system in order to make sure that it's not physically broken.

 

[Jhon Shaw]

Please provide this information so we can provide a complete analysis: Link Removed

Be sure that you have the latest drivers installed for the TrendNet dongle
Try the dongle on another system in order to make sure that it's not physically broken.

The forum will not let me upload the zip to my manager. It's under the 5mb limit. I tried multiple times so here is a link to it via dropbox - https://www.dropbox.com/s/6whu001w0bwmvx0/W7F_24-07-2013.zip

I have the latest drivers for the dongle however it wont let me run setup to install them because as soon as I plug it in which the setup requires, it bluescreens. I have gone in and updated the hidden driver in Device Manager with the drivers in the setup folder. Hope I can be helped.

 

[usasma]

Try the dongle in another system - if it causes a BSOD there, then it's the dongle that's at fault.

There are enough signs here that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):

To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - Link Removed )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.

C: drive only has about 2% free space. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

These devices are disabled. Is this deliberate? If so, why?

VirtualBox Host-Only Ethernet Adapter ROOT\NET\0001 This device is disabled.

802.11n Wireless LAN Card PCI\VEN_1814&DEV_3062&SUBSYS_30621814&REV_00\4&2F735D55&0&5020 This device is disabled.

Please enable them and then update their drivers - or remove them from your system. If you choose to update the drivers, please feel free to disable them again (if so desired).

Please remove the AsRock XFastLAN utility from your system as it is known to cause BSOD's. If the XFastUSB utility is installed, please remove that also.

Out of 13 memory dumps there were 5 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).

You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed I suspect the dongle, so test that first (in another machine)

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Please remove the software for the wireless USB XBox controller. It's driver (xusb21.sys) has been known to cause BSOD's in some Windows systems. Once the entire system is stabilized feel free to install it again and test it.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

btwusb.sys Wed Jan 24 20:31:36 2007 (45B80878)
WIDCOMM USB Bluetooth Driver
btwusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
Wacom(tablet) Mouse Filter
Link Removed

btkrnl.sys Fri Mar 30 00:44:53 2007 (460C95C5)
Bluetooth Network Protocol Stack
Link Removed

evsbc.sys Mon May 19 09:01:30 2008 (48317A2A)
ELTIMA Virtual Serial Bus
evsbc.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

FNETURPX.SYS Fri Oct 3 22:27:02 2008 (48E6D476)
FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
Link Removed

netr28x.sys Wed Feb 25 22:02:09 2009 (49A60631)
Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Mon Jul 22 21:11:11.533 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-69015-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:21:15.142[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 19:49:19.984 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-73062-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:54.593[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+13d )[/B]
BugCheck [B]A, {3, 2, 1, fffff8000329175d}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000329175d, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiProcessExpiredTimerList+13d[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 19:42:08.630 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-74546-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 9:44:03.318[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 04:32:01.375 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-73562-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:01:40.000[/B]
Probably caused by :[B]hardware ( nt!KiDeferredReadyThread+5c )[/B]
BugCheck [B]A, {ffffd8e93d83ca21, 2, 0, fffff80003296f5c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffd8e93d83ca21, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003296f5c, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 04:29:44.054 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-73546-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:07:49.679[/B]
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by :[B]hardware ( amdk8+41f2 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 04:21:16.813 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-80593-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:19:41.422[/B]
*** WARNING: Unable to verify timestamp for cmudax3.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudax3.sys
Probably caused by :[B]cmudax3.sys ( cmudax3+29fb7 )[/B]
BugCheck [B]D1, {0, 2, 1, fffff88007231fb7}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88007231fb7, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_cmudax3+29fb7[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 02:49:17.107 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-69437-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:06:20.732[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, fffffa80048f2038, b6000000, 181}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80048f2038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000181, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 01:57:56.881 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-73656-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:09:30.491[/B]
*** WARNING: Unable to verify timestamp for cmudax3.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudax3.sys
Probably caused by :[B]cmudax3.sys ( cmudax3+686b4 )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff80003296a0f, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003296a0f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_cmudax3+686b4[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 01:08:11.344 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-70015-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:18.125[/B]
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by :[B]amdk8.sys ( amdk8+41f2 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x1E_amdk8+41f2[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 00:38:29.708 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-65812-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:01:21.505[/B]
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by :[B]amdk8.sys ( amdk8+41f2 )[/B]
BugCheck [B]A, {0, d, 1, fffff800032710d0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032710d0, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_amdk8+41f2[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 00:36:37.643 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072213-67500-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:12:23.440[/B]
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by :[B]amdk8.sys ( amdk8+41f2 )[/B]
BugCheck [B]A, {2669, d, 1, fffff800032d11d0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000002669, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032d11d0, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_amdk8+41f2[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 21 20:54:15.094 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072113-73359-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]1 days 17:26:28.358[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiDeferredReadyThread+565 )[/B]
BugCheck [B]A, {ffffdb5bb4e65620, 2, 1, fffff800032d1465}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffdb5bb4e65620, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032d1465, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiDeferredReadyThread+565[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 00:23:35.637 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071713-64843-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 5:22:06.434[/B]
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by :[B]netr28x.sys ( netr28x+1ff87 )[/B]
BugCheck [B]C4, {1001, fffffa80057bb608, fffffa8006789380, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000001001, Verifier predicted potential deadlock.
Arg2: fffffa80057bb608, Lock address.
Arg3: fffffa8006789380, Verifier internal data.
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_1001
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0xc4_1001_netr28x+1ff87[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Mon Jul 22 21:11:11.533 2013 (UTC - 4:00)**************************
[B]btwusb.sys             Wed Jan 24 20:31:36 2007 (45B80878)[/B]
[B]btkrnl.sys             Fri Mar 30 00:44:53 2007 (460C95C5)[/B]
[B]netr28x.sys            Wed Feb 25 22:02:09 2009 (49A60631)[/B]
WMDrive.sys            Thu Mar 11 03:13:30 2010 (4B98A62A)
amdxata.sys            Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys             Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys           Fri Apr  9 05:22:41 2010 (4BBEF1E1)
vsflt53.sys            Tue Apr 12 07:31:35 2011 (4DA43817)
nvBridge.kmd           Fri May 20 23:58:23 2011 (4DD7385F)
cfosspeed6.sys         Mon Jul  4 09:18:51 2011 (4E11BDBB)
PxHlpa64.sys           Mon Oct 17 10:29:34 2011 (4E9C3BCE)
AsrRamDisk.sys         Thu Jan 12 23:52:38 2012 (4F0FB896)
[B]dtsoftbus01.sys        Fri Jan 13 08:45:46 2012 (4F10358A)[/B]
VBoxUSBMon.sys         Thu Oct 18 11:08:03 2012 (50801B53)
VBoxNetFlt.sys         Thu Oct 18 11:08:03 2012 (50801B53)
VBoxDrv.sys            Thu Oct 18 11:09:06 2012 (50801B92)
nvlddmkm.sys           Fri Jan 18 08:22:15 2013 (50F94C87)
ElbyCDIO.sys           Mon Mar  4 04:21:51 2013 (513467AF)
VClone.sys             Sun Mar 10 20:49:12 2013 (513D2A08)
avgtpx64.sys           Tue May 28 10:57:10 2013 (51A4C5C6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 19:42:08.630 2013 (UTC - 4:00)**************************
cmudax3.sys            Mon Nov 30 22:31:07 2009 (4B148DFB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 02:49:17.107 2013 (UTC - 4:00)**************************
[B]FNETURPX.SYS           Fri Oct  3 22:27:02 2008 (48E6D476)[/B]
[B]xusb21.sys             Wed Apr  8 10:28:44 2009 (49DCB49C)[/B]
MijXfilt.sys           Fri Dec 31 02:54:06 2010 (4D1D8C1E)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 01:57:56.881 2013 (UTC - 4:00)**************************
[B]wacommousefilter.sys   Fri Feb 16 13:12:17 2007 (45D5F401)[/B]
[B]evsbc.sys              Mon May 19 09:01:30 2008 (48317A2A)[/B]
wacomvhid.sys          Mon Sep 21 19:29:14 2009 (4AB80C4A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 22 01:08:11.344 2013 (UTC - 4:00)**************************
cmudax3.sys            Fri May 22 03:02:32 2009 (4A164E08)
nvstor64.sys           Tue Jun 30 20:21:51 2009 (4A4AAC1F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 21 20:54:15.094 2013 (UTC - 4:00)**************************
wacmoumonitor.sys      Fri Oct 29 12:30:06 2010 (4CCAF68E)
[/font]

btwusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
evsbc.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed

 

[Jhon Shaw]

I will try the dongle in another machine when i have an opportunity, I only have access to this one atm. I have tried another dongle (Jabra) and it does the same thing. Interesting you mentioned the xbox controller. It's actually for my ps3 controller and uses motioninjoy which uses bt. I suspected these drivers to cause a problem but have had no luck completely removing this software/drivers. Their website and forum have been no help getting rid of it. There are a few things I disabled trying to fix this myself and as for windows, it came on the computer so I can't vouch for its origin. I will try everything you suggested. Thank you for your help.