- Oct 1, 2016
- 21
- 0
- 1,520
im playing a game called adrenaline its been given me a bsod kmode exeption not handled when im playing i disabled xhunter.sys deleted it an even disabled driver signature rienforcement nothing worked please help this issue is really annoying and i have a whocrashed test result if it helps
Computer name: HAMMA
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: INTEL Corporation, MAHOBAY
CPU: GenuineIntel Intel(R) Pentium(R) CPU G2030 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2115211264 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 11/12/2016 8:35:30 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-28125-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1A010C49, 0x8, 0x1A010C49)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 8:35:30 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: xhunter1.sys (xhunter1+0x5488)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1A010C49, 0x8, 0x1A010C49)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: xhunter1.sys .
Google query: xhunter1.sys KMODE_EXCEPTION_NOT_HANDLED
On Sat 11/12/2016 8:30:44 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-28671-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x27010AAD, 0x8, 0x27010AAD)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 5:50:38 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-21328-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x10F47, 0x8, 0x10F47)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 2:18:29 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-25984-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0xFC (0xFFFFFFFF9B010DB3, 0x79392121, 0xFFFFFFFFA7095C4C, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 5 are included in this report. 2 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 353.62 , NVIDIA Corporation)
xhunter1.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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
Computer name: HAMMA
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: INTEL Corporation, MAHOBAY
CPU: GenuineIntel Intel(R) Pentium(R) CPU G2030 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2115211264 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 11/12/2016 8:35:30 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-28125-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1A010C49, 0x8, 0x1A010C49)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 8:35:30 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: xhunter1.sys (xhunter1+0x5488)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1A010C49, 0x8, 0x1A010C49)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: xhunter1.sys .
Google query: xhunter1.sys KMODE_EXCEPTION_NOT_HANDLED
On Sat 11/12/2016 8:30:44 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-28671-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x27010AAD, 0x8, 0x27010AAD)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 5:50:38 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-21328-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x10F47, 0x8, 0x10F47)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 11/12/2016 2:18:29 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-25984-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x20023)
Bugcheck code: 0xFC (0xFFFFFFFF9B010DB3, 0x79392121, 0xFFFFFFFFA7095C4C, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 5 are included in this report. 2 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 353.62 , NVIDIA Corporation)
xhunter1.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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
Facebook
Twitter
Instagram