I keep getting blue screens whenever im playing a game (Dota2) and i've been getting it for quite often now. I have the whocrashed app and this is what it says:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 9/27/2014 12:08:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092814-23790-01.dmp
This was probably caused by the following module: hdaudbus.sys (0xFFFFF8800482696A)
Bugcheck code: 0xD1 (0x24, 0x9, 0x0, 0xFFFFF8800482696A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 12:08:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x196A)
Bugcheck code: 0xD1 (0x24, 0x9, 0x0, 0xFFFFF8800482696A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 11:50:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-27019-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA80083CD1A0, 0x4F444648, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 6:24:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-23540-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x2DDE0)
Bugcheck code: 0xD1 (0x8000, 0xA, 0x1, 0xFFFFF8800485DDE0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode 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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 9/27/2014 12:00:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0xA, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 9/25/2014 6:02:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-25552-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x24, 0xFFFFF8A00240A270, 0xFFFFF8A00B8AAC90, 0x0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 9/25/2014 5:46:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-26114-01.dmp
This was probably caused by the following module: hidusb.sys (0xFFFFF88008036EE3)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF88008036EE3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 9/24/2014 11:39:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-23524-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F273C83)
Bugcheck code: 0x3D (0xFFFFF88002F1AC80, 0x0, 0x0, 0xFFFFF8800F273C83)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 344.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 344.11
Bug check description: This bug check appears very infrequently.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation).
Google query: NVIDIA Corporation INTERRUPT_EXCEPTION_NOT_HANDLED
On Wed 9/24/2014 11:23:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-24211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x6400000038, 0x2, 0x1, 0xFFFFF800030E4F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On Wed 9/24/2014 11:07:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-23992-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x128859)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF88004951859, 0xFFFFF8800CD9F460, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation SYSTEM_SERVICE_EXCEPTION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:
netwns64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation)
shareduserdata.sys
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 have no idea how to fix these things because i have no idea in dealing with these errors. Can someone walk me through it? Would appreciate it very much. Thank you!
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 9/27/2014 12:08:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092814-23790-01.dmp
This was probably caused by the following module: hdaudbus.sys (0xFFFFF8800482696A)
Bugcheck code: 0xD1 (0x24, 0x9, 0x0, 0xFFFFF8800482696A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 12:08:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x196A)
Bugcheck code: 0xD1 (0x24, 0x9, 0x0, 0xFFFFF8800482696A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 11:50:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-27019-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA80083CD1A0, 0x4F444648, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 9/27/2014 6:24:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-23540-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x2DDE0)
Bugcheck code: 0xD1 (0x8000, 0xA, 0x1, 0xFFFFF8800485DDE0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode 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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 9/27/2014 12:00:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0xA, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 9/25/2014 6:02:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-25552-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x24, 0xFFFFF8A00240A270, 0xFFFFF8A00B8AAC90, 0x0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 9/25/2014 5:46:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-26114-01.dmp
This was probably caused by the following module: hidusb.sys (0xFFFFF88008036EE3)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF88008036EE3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 9/24/2014 11:39:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-23524-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F273C83)
Bugcheck code: 0x3D (0xFFFFF88002F1AC80, 0x0, 0x0, 0xFFFFF8800F273C83)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 344.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 344.11
Bug check description: This bug check appears very infrequently.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation).
Google query: NVIDIA Corporation INTERRUPT_EXCEPTION_NOT_HANDLED
On Wed 9/24/2014 11:23:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-24211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x6400000038, 0x2, 0x1, 0xFFFFF800030E4F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On Wed 9/24/2014 11:07:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092414-23992-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x128859)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF88004951859, 0xFFFFF8800CD9F460, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation SYSTEM_SERVICE_EXCEPTION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:
netwns64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation)
shareduserdata.sys
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 have no idea how to fix these things because i have no idea in dealing with these errors. Can someone walk me through it? Would appreciate it very much. Thank you!