Windows 7: "ntoskrnl.exe" BSOD

Toggle sidebar Toggle sidebar
TiredGiraffe

TiredGiraffe

Commendable
Feb 28, 2016
45
0
1,540
Please help me fix this I have no idea what this is but here is the cause:

On Mon 29/02/2016 21:36:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022916-17456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xA (0xFFFFF8A005659728, 0x2, 0x1, 0xFFFFF80003338A50)
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.
 
Solution
C
Hey,
DRIVER_IRQL_NOT_LESS_OR_EQUAL is caused when kernel mode driver attempts to read invalid memory at high IRQL.
To resolve the issue, follow the below methods:

Method 1. Disable the faulty driver: You may see driver in blue screen by name like xyz.sys. All you need to do is remove it from device manager.

Method 2. Run driver verifier: If driver name is not displayed in BSOD then you can run driver verifier. To do so, go through with the below steps:
Start> type verifier in search> select create standard setting> Click on automatically select all drivers installed> Next
Now restart, all faulty drivers will be listed in BSOD. Uninstall them from device driver

Method 3. Restore system to an earlier point: The problem can occur due...
Sort by date Sort by votes
C

carolinebennett

Reputable
Oct 15, 2015
31
0
4,560
Hey,
DRIVER_IRQL_NOT_LESS_OR_EQUAL is caused when kernel mode driver attempts to read invalid memory at high IRQL.
To resolve the issue, follow the below methods:

Method 1. Disable the faulty driver: You may see driver in blue screen by name like xyz.sys. All you need to do is remove it from device manager.

Method 2. Run driver verifier: If driver name is not displayed in BSOD then you can run driver verifier. To do so, go through with the below steps:
Start> type verifier in search> select create standard setting> Click on automatically select all drivers installed> Next
Now restart, all faulty drivers will be listed in BSOD. Uninstall them from device driver

Method 3. Restore system to an earlier point: The problem can occur due to recently added hardware or driver. In order to fix the issue, you need to perform system restore.

Method 4. Run Memory Test: If above methods did not resolve the bug check then it may be possible that there is a problem in RAM. Run memory test. To do this, go to control panel> diagnose your Computer's Memory Problems
If it displays error then it means you have to replace your RAM.

Method 5. Repair Windows System Files: You can run System File Checker in command prompt to repair corrupted or missing System Files. Open an elevated command line and type SFC /scannow.

Method 6. Repair Hard Disk errors: Run Check Disk utility in command prompt to repair disk related errors. Type CHKDSK /F.

Hope it will help you.
 
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