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

I also use WhoCrashed and got the same error about ntoskrnl.exe:

I also checked my C: drice with chkdsk and performed a memory diagnostic and both were fine.

This is not the first that i had. It's probably the 7th. it started today at 1:00PM (13:00 here in Europe) and all happened today (of course...). I noticed that almost all of them happened after i ended some processes i didnt needed running because i was going to defragment after that.
Most of these processes, I end before gaming for maximum performance... These are the ones i remember:

- Acmon.exe (Splendid utility from asus)
- AsScrPro.exe
- ATKOSD2.exe, DMedia.exe, HControl.exe, WDC.exe (Asus ATK Hotkey Package)
- ACEngSvr Module (i think i didnt always end this process)
- DTShellHelper.exe (Daemon Tools)
- FspUip.exe (asus mouse pad)
- FLxHCIm.exe (Fresco Logic)
- TeaTimer.exe (spybot)
- jusched.exe (java update)
- hid.exe and tray.exe (asus mouse)
- baterylife.exe (asus Power4Gear Hybrid)
- nvtray.exe (nvidia settings)

My WhoCrasher didnt found any specific driver because in the other +/-6 times, there was no dump created.
Do you think I should try the "verifier.exe" thing. How should i do it?

Help please!!! Thanks in advance.

joaodiogo321

Please start your own thread wherein you state your own problem.

bsaf,
Welcome to SevenForums!

You can uninstall WhoCrashed which is rather useless and can itself cause crashes.

What you can do is: Blue Screen of Death (BSOD) Posting Instructions

Karlsnooks- uninstalled WHoCrashed and uploaded the Windows_NT6 zip file--
thanks

Problematic Software:

• Recommend removing your ASUS utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability.

All crashes were related to your Intel(R) USB 3.0 eXtensible Host Controller Driver. Yours are not that old, so I suspect a USB device is the actual cause. What USB devices are you using?

You also appear to have some corrupted Norton drivers. Re-install Norton:

• Download and run the Norton Removal Tool
• Download a fresh copy of your Norton software
• Install the freshly downloaded Norton software

writhziden- thanks for the input- I uninstalled all the Asus utilities, and will reinstall Norton shortly- As for your question regarding the Usb devices- no USB 3.0 devices- just 2.0-- the usual- Microsoft keyboard and mouse, HP office jet 6500A printer and a backup hard drive

Same thing i posted in another thread : Intel USB 3.0 eXtensible host controller drivers are broken and cause bsods, hangups and some other errors when you plug external devices into the non USB 3.0 ports.

You have to uninstall the drivers in the standardsoftware folder NOT! in the device manager or it causes other bugs maybe.

When the broken intel drivers are uninstalled you can use all ports with 2.0 Speed only but without any errors. Just wait for working USB 3.0 drivers from Intel for your Panther Point Chipset even it could take a bit longer lol.

My pleasure.

Thanks, Alimbo- will it be better if I plug USB 2 devices into the 3.0 slots? And do you have any idea why it seems to happen when I am printing photos?
Thanks

As far as i have tested it only the USB 2.0 ports work for external devices such as printers if the USB 3.0 drivers are properly uninstalled. The USB 3.0 ports or eSata (if there is one) only work for data transfer at 2.0 Speed.

I cant answer your 2nd question without any proof since i dont know what exactly is wrong coded or if it is even a design failure in the end. But i think it has something to do with the fact that it handles USB 2.0 ports like they were USB 3.0 ports. Same goes for eSata. Since this would cause data interrupts due to the fact that USB 2.0 / eSata are technically different and need different controlling commands by the Chipset. But this is only my suggestion.