BOSD IRQL not less or equal

Toggle sidebar Toggle sidebar
F

FromFinland

Prominent
Feb 28, 2017
10
0
510
i got this bosd when i played Counter strike global offensive and my computer runs it normally but when i played like 1 hour i got BOSD. its called irql not less or equal. Can someone help me to fix this problem? Thanks for your time! (im new on this site too so dont expect me to use this like pro) im using w10 atm
 
Solution
Colif
Only downside to going back to 7 is you will need to buy a win 7 licence unless you upgraded to 8.1 and then to 10. If you went from 7 to 10, then your old licence was converted to a win 10 licence 1 month after you swapped. So you would need to buy a licence for 7 in that case.

I don't know what graphics card you have so i don't know what impact of going to 7 will be. If you play DX12 games now then you wouldn't be able to on 7 as I think it only has DX 11
Sort by date Sort by votes
On Tue 28.2.2017 17.23.12 your computer crashed
crash dump file: C:\Windows\Minidump\022817-26890-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0xB62C)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFF809E07DB62C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Tue 28.2.2017 17.23.12 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0xB62C)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFF809E07DB62C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Fri 24.2.2017 14.29.33 your computer crashed
crash dump file: C:\Windows\Minidump\022417-30109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB153)
Bugcheck code: 0x124 (0x0, 0xFFFF970E1392E8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 24.2.2017 3.04.56 your computer crashed
crash dump file: C:\Windows\Minidump\022417-26312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x0, 0xFFFFF800A649DA92, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 23.2.2017 23.31.02 your computer crashed
crash dump file: C:\Windows\Minidump\022317-26812-01.dmp
This was probably caused by the following module: hidusb.sys (hidusb+0x11EE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800B33011EE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.
 
Upvote 0 Downvote
top error is directX and they are normally caused by graphics card drivers so try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

Whea errors are hardware errors, normally associated with CPU but can be other hardware like USB or PCI cards

hidusb.sys = USB drivers. I would check on motherboard web site (or if its a brand name PC, the website for model) and make sure you have latest USB drivers.

fixing USB drivers may fix the whea error
 
Upvote 0 Downvote
Colif last time (yesterday) when i got this Bluescreen it said something about USB things? Have any ideas ? all usb things wich are plugged in is my Headset (razer kraken usb) my mouse (gigabyte M6900 and my keyboard (CMSTORM)
 
Upvote 0 Downvote
Colif last time (yesterday) when i got this Bluescreen it said something about USB things? Have any ideas ? all usb things wich are plugged in is my Headset (razer kraken usb) my mouse (gigabyte M6900 and my keyboard (CMSTORM)
 
Upvote 0 Downvote
On Fri 3.3.2017 23.08.00 your computer crashed
crash dump file: C:\Windows\Minidump\030417-28375-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF80B77CB428A)
Bugcheck code: 0xD1 (0x6D4, 0x2, 0x0, 0xFFFFF80B77CB428A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: USB 1.1- and USB 2.0-port controller
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.

 
Upvote 0 Downvote
download USB drivers for your motherboard and reinstall them. Even if you have the latest.

If I knew what motherboard, I would have linked it here, but unless PC is a brand name PC, it should be easy to find. If its a brand name PC, go look at make/model site

I already said this above: hidusb.sys = USB drivers. I would check on motherboard web site (or if its a brand name PC, the website for model) and make sure you have latest USB drivers.

If you already did that, Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote
i also got this today!
On Tue 7.3.2017 17.35.46 your computer crashed
crash dump file: C:\Windows\Minidump\030717-28500-01.dmp
This was probably caused by the following module: usbaudio.sys (usbaudio+0x17B90)
Bugcheck code: 0xBE (0xFFFFF80E124E7B90, 0xD300000257E5121, 0xFFFF85002D1954C0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\usbaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Audio Class Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.
 
Upvote 0 Downvote
USB again..

I guess its my fault for not asking before but how old is your PC? That motherboard hasn't got any chipset drivers since Vista, I am amazed it only has one problem. There aren't any drivers I can offer you that will help as Vista age drivers won't work on win 10.

the only 2 ways to fix this error are 1) go back to win 7 as vista drivers do work on it, or save up and buy a new PC as I am sure you will notice a difference in everything (I only upgraded from a 10 year of PC myself last year so I know what I am saying here)
 
Upvote 0 Downvote
would it help if i just reset my computer to run in windows 7? and if it does is it chanching my game experiense? like can i play all games what i play atm or what? and if it helps how i can reset it back to windows 7
 
Upvote 0 Downvote
Only downside to going back to 7 is you will need to buy a win 7 licence unless you upgraded to 8.1 and then to 10. If you went from 7 to 10, then your old licence was converted to a win 10 licence 1 month after you swapped. So you would need to buy a licence for 7 in that case.

I don't know what graphics card you have so i don't know what impact of going to 7 will be. If you play DX12 games now then you wouldn't be able to on 7 as I think it only has DX 11
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom