-
Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
Why not Click Here To Sign Up and start enjoying great FREE Tech Support.
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
BSOD UNEXPECTED_KERNEL_MODE_TRAP
- Thread starter Ben Davis
- Start date
-
- Tags
- bsod windows 10
- Status
Follow posting instructions form the following link.
https://pchelpforum.net/t/posting-instructions-please-read-before-posting-in-this-section.11266/
https://pchelpforum.net/t/posting-instructions-please-read-before-posting-in-this-section.11266/
Are crash dmps enabled on your computer.
What you describe in your reply #3 suggests more of a hardware issue, overheating and/or a flaky PSU coming to mind.
Please provide information about your computer, is it a custom build or brand name such as Dell or HP, if a brand name, provide the model name or series number (not serial) if a custom build post the brand and model name or number for the MB, the RAM (including the amount) add on video card if one is used and the PSU (power supply unit) providing these details will enable us to better assist you.
What you describe in your reply #3 suggests more of a hardware issue, overheating and/or a flaky PSU coming to mind.
Please provide information about your computer, is it a custom build or brand name such as Dell or HP, if a brand name, provide the model name or series number (not serial) if a custom build post the brand and model name or number for the MB, the RAM (including the amount) add on video card if one is used and the PSU (power supply unit) providing these details will enable us to better assist you.
Are you overclocking at all?
Corsair are a good brand of PSU but I have seen a few bad reviews of your particular model, one here posts the following;
Cons: This thing failed after 2 weeks
It would randomly turn off my whole system without warning, just a mess, and I was so confused Until I read a post about my symptoms and pointed toward a faulty power supply then I use my 10 year warranty from corsair and then they gave me a better power supply instead because they didn’t have an rmx on hand, great customer service though, hopefully it will function
Corsair are a good brand of PSU but I have seen a few bad reviews of your particular model, one here posts the following;
Cons: This thing failed after 2 weeks
It would randomly turn off my whole system without warning, just a mess, and I was so confused Until I read a post about my symptoms and pointed toward a faulty power supply then I use my 10 year warranty from corsair and then they gave me a better power supply instead because they didn’t have an rmx on hand, great customer service though, hopefully it will function
Thanks phill heres a copy of a crash dump i just got, although recently it has begun to do what you have described above, my computer has been randomly starting to freeze where the screen will instantly pause the audio will cut out and ill have to manually restart it, hope you can make some sense of this, and sorry its taken so long for me to get this
Edit: No i'm not overclocking as far as i know (although asus gpu tweak is set to gaming mode so it may be automatically overclocking?)
Edit 2: I bought the psu from pccasegear, i've found how to claim a warranty etc but if this does turn out to be the issue what would i describe as the fault?
Edit: No i'm not overclocking as far as i know (although asus gpu tweak is set to gaming mode so it may be automatically overclocking?)
Edit 2: I bought the psu from pccasegear, i've found how to claim a warranty etc but if this does turn out to be the issue what would i describe as the fault?
Last edited:
Nothing specific showing up in your crash dmp as all that is listed is PROCESS_NAME: System and IMAGE_NAME: ntkrnlmp.exe which could just about anything, you can check the latter here
Lets see if DriverVerifier can flush out any rogue driver/s, see info below but please note that not all options are available in Windows 10.
To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2
1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support
2. Run Driver Verifier -
- Windows 7 & Vista - START | type verifier
- Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier
Make these selections -
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -
▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks
4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot[/HIDE]
- If the Driver Verifier (DV) finds a violation, it will result in a BSOD
- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1
- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot
- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use
If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.
Lets see if DriverVerifier can flush out any rogue driver/s, see info below but please note that not all options are available in Windows 10.
To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2
1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support
2. Run Driver Verifier -
- Windows 7 & Vista - START | type verifier
- Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier
Make these selections -
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -
▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks
4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot[/HIDE]
- If the Driver Verifier (DV) finds a violation, it will result in a BSOD
- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1
- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot
- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use
If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.
Thanks again for the help, currently running windows 10 but 'Concurrency Stress Test' was not an option i was able to select, also i'm unsure as to how I make my BSOD dumps VERIFIER_ENABLED_MINIDUMPs.
Under system failure my enabled settings are as follows.
Write an event to the system log
Auto restart
Auto memory dump
Dump file: "%SystemRoot%\MEMORY.DMP"
Disable automatic deletion of memory dumps when disk space is low
Under system failure my enabled settings are as follows.
Write an event to the system log
Auto restart
Auto memory dump
Dump file: "%SystemRoot%\MEMORY.DMP"
Disable automatic deletion of memory dumps when disk space is low
Same location Ben, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
For clarity, it was mentioned in my reply #8 that not all options are available in Windows 10
For clarity, it was mentioned in my reply #8 that not all options are available in Windows 10
The verifier didnt cause me a BSOD and nothing was generated in the Minidump folder i was just listing out my system failure settings to see if they were okay or not, where do i go from here?
Edit: Since the verifier has found no problems should i turn it off?
Edit: Since the verifier has found no problems should i turn it off?
Settings info acknowledged and yes they are as they should be
Please be sure to run DV for a minimum of 72 hrs from when it was first initiated, longer is better and it really does not affect system performance.
Please be sure to run DV for a minimum of 72 hrs from when it was first initiated, longer is better and it really does not affect system performance.
The first crash was caused by a problem between Avast and Discord, the second only flags up a system driver along with the driver NETIO.SYS which is related to the Network I/O Subsystem, this could also be caused by a problem between Avast and your network connection.
Try updating your network drivers, make sure that Windows is fully up to date and uninstall Avast, see my canned info below;
Windows 8, 8.1 and 10 come with an improved Windows Defender, it offers the same real-time anti-virus/anti-malware protection as Microsoft Security Essentials. Windows Defender also shares the same malware signature definitions as Microsoft Security Essentials, and Forefront Endpoint Protection. Technically, Microsoft Security Essentials has not been renamed Windows Defender, or combined with it in Windows 8, 8.1 and 10.
Having more than one AV installed on your computer is bad, it will slow down the computer, cause internet connection problems and leave you with no AV protection at all if they cancel each other out as they fight for resources.
If any AV product that you have is a paid for version you should always make sure that you have a copy of the product key kept somewhere safe just in case you ever wish to reinstall it.
Avast clean removal info here
If you stick with only Windows Defender, once any other AV has been correctly uninstalled, check to see if Windows Defender has auto enabled and allow it to update and carry out a full scan of your computer.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8013266ce90, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MI_READ_PTE_LOCK_FREE+0
fffff801`3266ce90 488b01 mov rax,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: AV
PROCESS_NAME: Discord.exe
TRAP_FRAME: ffff8e06daa8a260 -- (.trap 0xffff8e06daa8a260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013266ce90 rsp=ffff8e06daa8a3f8 rbp=7fffffffffffffff
r8=ffffb4da6d369000 r9=ffffb48000009140 r10=ffff920ead0f0980
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MI_READ_PTE_LOCK_FREE:
fffff801`3266ce90 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801327d3c69 to fffff801327c30a0
STACK_TEXT:
ffff8e06`daa8a118 fffff801`327d3c69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8e06`daa8a120 fffff801`327d08e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8e06`daa8a260 fffff801`3266ce90 : fffff801`3275c951 00000000`00000001 00000000`00000000 ffff2f1f`84605a96 : nt!KiPageFault+0x425
ffff8e06`daa8a3f8 fffff801`3275c951 : 00000000`00000001 00000000`00000000 ffff2f1f`84605a96 00000000`00000000 : nt!MI_READ_PTE_LOCK_FREE
ffff8e06`daa8a400 fffff801`3267a901 : 00000000`00000000 fffff801`3266e4b1 ffff920e`ad0f0980 ffffb480`00009140 : nt!MiCaptureProtectionFromLockedProto+0x29
ffff8e06`daa8a430 fffff801`326778b4 : 00000000`01228000 00000000`00002c00 00000000`00000001 ffff920e`adfa7a80 : nt!MiGetPageProtection+0x551
ffff8e06`daa8a4a0 fffff801`326e63a6 : 00000000`03a9c000 00000000`01200000 ffff920e`ad0f0980 0a000000`1c8da121 : nt!MiQueryAddressState+0x414
ffff8e06`daa8a690 fffff801`32b1a1b6 : ffff8e06`00000006 00000000`00000003 ffff8e06`00000000 00000000`00000003 : nt!MiQueryAddressSpan+0x126
ffff8e06`daa8a730 fffff801`32b19a51 : ffff8e06`daa8aa00 ffffb480`003b97c8 ffffb4da`40001dc8 ffffb4da`6d200008 : nt!MmQueryVirtualMemory+0x756
ffff8e06`daa8a8d0 fffff80a`2dedd398 : ffff920e`a7558700 ffff8e06`daa8aa80 00000000`00000000 00000000`03caa000 : nt!NtQueryVirtualMemory+0x25
ffff8e06`daa8a920 ffff920e`a7558700 : ffff8e06`daa8aa80 00000000`00000000 00000000`03caa000 00000000`00000030 : aswSnx+0x2d398
ffff8e06`daa8a928 ffff8e06`daa8aa80 : 00000000`00000000 00000000`03caa000 00000000`00000030 00000000`0909e458 : 0xffff920e`a7558700
ffff8e06`daa8a930 00000000`00000000 : 00000000`03caa000 00000000`00000030 00000000`0909e458 00000000`00000000 : 0xffff8e06`daa8aa80
STACK_COMMAND: kb
FOLLOWUP_IP:
aswSnx+2d398
fffff80a`2dedd398 448be0 mov r12d,eax
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: aswSnx+2d398
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSnx
IMAGE_NAME: aswSnx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5bdc3b02
FAILURE_BUCKET_ID: X64_AV_VRF_aswSnx+2d398
BUCKET_ID: X64_AV_VRF_aswSnx+2d398
Followup: MachineOwner
Try updating your network drivers, make sure that Windows is fully up to date and uninstall Avast, see my canned info below;
Windows 8, 8.1 and 10 come with an improved Windows Defender, it offers the same real-time anti-virus/anti-malware protection as Microsoft Security Essentials. Windows Defender also shares the same malware signature definitions as Microsoft Security Essentials, and Forefront Endpoint Protection. Technically, Microsoft Security Essentials has not been renamed Windows Defender, or combined with it in Windows 8, 8.1 and 10.
Having more than one AV installed on your computer is bad, it will slow down the computer, cause internet connection problems and leave you with no AV protection at all if they cancel each other out as they fight for resources.
If any AV product that you have is a paid for version you should always make sure that you have a copy of the product key kept somewhere safe just in case you ever wish to reinstall it.
Avast clean removal info here
If you stick with only Windows Defender, once any other AV has been correctly uninstalled, check to see if Windows Defender has auto enabled and allow it to update and carry out a full scan of your computer.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8013266ce90, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MI_READ_PTE_LOCK_FREE+0
fffff801`3266ce90 488b01 mov rax,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: AV
PROCESS_NAME: Discord.exe
TRAP_FRAME: ffff8e06daa8a260 -- (.trap 0xffff8e06daa8a260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013266ce90 rsp=ffff8e06daa8a3f8 rbp=7fffffffffffffff
r8=ffffb4da6d369000 r9=ffffb48000009140 r10=ffff920ead0f0980
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MI_READ_PTE_LOCK_FREE:
fffff801`3266ce90 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801327d3c69 to fffff801327c30a0
STACK_TEXT:
ffff8e06`daa8a118 fffff801`327d3c69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8e06`daa8a120 fffff801`327d08e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8e06`daa8a260 fffff801`3266ce90 : fffff801`3275c951 00000000`00000001 00000000`00000000 ffff2f1f`84605a96 : nt!KiPageFault+0x425
ffff8e06`daa8a3f8 fffff801`3275c951 : 00000000`00000001 00000000`00000000 ffff2f1f`84605a96 00000000`00000000 : nt!MI_READ_PTE_LOCK_FREE
ffff8e06`daa8a400 fffff801`3267a901 : 00000000`00000000 fffff801`3266e4b1 ffff920e`ad0f0980 ffffb480`00009140 : nt!MiCaptureProtectionFromLockedProto+0x29
ffff8e06`daa8a430 fffff801`326778b4 : 00000000`01228000 00000000`00002c00 00000000`00000001 ffff920e`adfa7a80 : nt!MiGetPageProtection+0x551
ffff8e06`daa8a4a0 fffff801`326e63a6 : 00000000`03a9c000 00000000`01200000 ffff920e`ad0f0980 0a000000`1c8da121 : nt!MiQueryAddressState+0x414
ffff8e06`daa8a690 fffff801`32b1a1b6 : ffff8e06`00000006 00000000`00000003 ffff8e06`00000000 00000000`00000003 : nt!MiQueryAddressSpan+0x126
ffff8e06`daa8a730 fffff801`32b19a51 : ffff8e06`daa8aa00 ffffb480`003b97c8 ffffb4da`40001dc8 ffffb4da`6d200008 : nt!MmQueryVirtualMemory+0x756
ffff8e06`daa8a8d0 fffff80a`2dedd398 : ffff920e`a7558700 ffff8e06`daa8aa80 00000000`00000000 00000000`03caa000 : nt!NtQueryVirtualMemory+0x25
ffff8e06`daa8a920 ffff920e`a7558700 : ffff8e06`daa8aa80 00000000`00000000 00000000`03caa000 00000000`00000030 : aswSnx+0x2d398
ffff8e06`daa8a928 ffff8e06`daa8aa80 : 00000000`00000000 00000000`03caa000 00000000`00000030 00000000`0909e458 : 0xffff920e`a7558700
ffff8e06`daa8a930 00000000`00000000 : 00000000`03caa000 00000000`00000030 00000000`0909e458 00000000`00000000 : 0xffff8e06`daa8aa80
STACK_COMMAND: kb
FOLLOWUP_IP:
aswSnx+2d398
fffff80a`2dedd398 448be0 mov r12d,eax
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: aswSnx+2d398
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSnx
IMAGE_NAME: aswSnx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5bdc3b02
FAILURE_BUCKET_ID: X64_AV_VRF_aswSnx+2d398
BUCKET_ID: X64_AV_VRF_aswSnx+2d398
Followup: MachineOwner
Thanks so much for your help, I've just removed avast, updated windows and checked for driver updates but I was just wondering, is it normal to have this many network drivers? (see attached file)
Edit: Been running games / programs that my computer seemed to crash most often in, so far so good! Ty a lot.
Edit: Been running games / programs that my computer seemed to crash most often in, so far so good! Ty a lot.
Attachments
Last edited:
Yes those network drivers are normal, they each have a different function.
See how things go for a couple of days and for now can I just ask that you create a new system restore point while things are stable.
You are welcome btw
See how things go for a couple of days and for now can I just ask that you create a new system restore point while things are stable.
You are welcome btw
- Status