Random BSOD.

[Meeyah222]

I've been having random BSOD for a couple of weeks now. Just playing or browsing the internet then my laptop will have BSOD (or sometimes just black out) then reboots (with suggestion to safe mode).
The first few times I did the System Restore on Safe Mode but the problem still happened a few days after.

I also ran WhoCrashed, here's the info:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 9/5/2015 1:10:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090515-69014-01.dmp
uptime: 02:17:23
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x109 (0xA3A039D89E7FB6F9, 0xB3B7465EF0FDF2CF, 0xFFFFF8800337D540, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/5/2015 1:10:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 02:17:23
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A039D89E7FB6F9, 0xB3B7465EF0FDF2CF, 0xFFFFF8800337D540, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.



Then after my latest BSOD


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 9/9/2015 11:51:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091015-27362-01.dmp
uptime: 01:18:34
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x487E0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF880056C57E0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: Intel Corporation UNEXPECTED_KERNEL_MODE_TRAP



On Wed 9/9/2015 11:51:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:18:34
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x487E0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF880056C57E0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: Intel Corporation UNEXPECTED_KERNEL_MODE_TRAP



On Sat 9/5/2015 1:10:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090515-69014-01.dmp
uptime: 02:17:23
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A039D89E7FB6F9, 0xB3B7465EF0FDF2CF, 0xFFFFF8800337D540, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 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.


I hope this help besides the DM log zip file below.


Please help me. I'm really afraid my laptop will die on me.
They say BSOD are very critical and may permanently disable laptop/pc.
Your help will be greatly appreciated.

 

[Hacb]

well, have you updated that driver it talks about? maybe that will help.

 

[Meeyah222]

Thanks for the quick reply.
I already did with the USB 3.0 Device Driver

I'm just really worried with the problem with that ntkrnlmp.exe
So far, everything I found on google are not helpful.
I don't know what to do with it.

 

[Meeyah222]

I had another BSOD last Thursaday, Sept 17.
A week since my last BSOD.
This time error only listed about 0x109 CRITICAL_STRUCTURE_CORRUPTION

I ran malwarebytes (and fixed all found errors)
CCleaner and Registry (and fixed all found errors)

I uninstalled Bluestacks, because I've had 3 BSOD while playing Clash of Clan, so I thought that may be the problem.
And uninstalled also some apps I'm not using anymore.

This morning I again had BSOD while I was asleep.
I forgot to shutdown my laptop but that shouldn't have been a problem because I set it to sleep after an hour.

Please help, again.

Below are my dump files on Sept 17 and today (Sept 19) from DM Log Collector.
Thanks in advance.

 

[Laith]

Just from the looks of it, it could be a bad Windows installation or a bad HDD.

Run SeaTools(DO NOT RUN FOR SSDS) http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Run MGADiag and post your results http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

Also the thing you heard in your first post is completely wrong. BSODs protect you from system damage, there is no way that a BSOD can automatically disable the system.