New
#1
BSOD mostly when printing photos- ntoskrnl.exe and iusb3xhc.sys
I have a brand new ASUS CM6870-US-3AA-
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17133318144 total
VM: 2147352576, free: 1930207232
I keep crashing and getting BSOD mostly when I am printing pictures- It can be when I am in Windows Live Photo Gallery or Photoshop Elements 10.
Here is the info from WhoCrashed for todays crash:
On Sat 6/23/2012 7:34:38 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\062312-26707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
On Sat 6/23/2012 7:34:38 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x638BB)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel(R) USB 3.0 eXtensible Host Controller Driver
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.
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: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: iusb3xhc.sys Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
On Sat 6/23/2012 7:12:19 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\062312-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
Here is the WhoCrashed Conclusion:
Conclusion
</B>
13 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
I did a full disk scan (chkdsk) and memory diagnostic and both were fine
-also did 2 full Norton scans and again no problems.
Help--and Thanks
Last edited by bsaf; 24 Jun 2012 at 09:16. Reason: added zip file