- May 24, 2017
- 21
- 0
- 510
Hi everybody,
I recently got my Motherboard burnt an ASrock H61 and I replaced it with an ECS H61H2-M10 (all other parts are ok) since then I get BSODs saying "IRQL_NOT_LESS_OR_EQUAL" and only once "MEMORY_MANAGEMENT" When I try to download,extract,install some heavy programs like 1GB+ (once I removed my Anti-Virus it worked a while then it's back again, now I'm left without anti-virus and still getting the problem)
Here is some info from WhoCrashed :
System Information (local)
--------------------------------------------------------------------------------
Computer name: USER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: H61H2-M10, ECS
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8536244224 bytes total
Crash Dump Analysis:
I searched on my motherboard site to see if there's any drivers unfortunately I haven't found anything (http://www.ecs.com.tw/ECSWebSite/Product/Product_DOWNLOAD.aspx?DetailID=1505&CategoryID=1&DetailName=Feature&MenuID=24&LanID=0)
I took a look to a driver site and this is what it gave me(https://www.touslesdrivers.com/index.php?v_page=31&v_id=UPzbu6UY3TogdDKK) :
Here are my drivers that are our outdated
http://imgur.com/a/tQGx4
And here is what I got when I downloaded an update for them from this site:
http://imgur.com/PxMW5rn
The 2 first folders on the top have an Installer each I don't know which one to choose and I don't know If I should do this update at all.
Please help me, this is my first time posting on Tom's Hardware so if I did any errors please excuse me, Thank you.
I recently got my Motherboard burnt an ASrock H61 and I replaced it with an ECS H61H2-M10 (all other parts are ok) since then I get BSODs saying "IRQL_NOT_LESS_OR_EQUAL" and only once "MEMORY_MANAGEMENT" When I try to download,extract,install some heavy programs like 1GB+ (once I removed my Anti-Virus it worked a while then it's back again, now I'm left without anti-virus and still getting the problem)
Here is some info from WhoCrashed :
System Information (local)
--------------------------------------------------------------------------------
Computer name: USER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: H61H2-M10, ECS
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8536244224 bytes total
Crash Dump Analysis:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 24/05/2017 18:57:21 your computer crashed
crash dump file: C:\Windows\Minidump\052417-13915-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EC1080)
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 24/05/2017 18:57:21 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EC1080)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Thu 18/05/2017 20:11:11 your computer crashed
crash dump file: C:\Windows\Minidump\051817-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0x1A (0x31, 0xFFFFFA80090234D0, 0xFFFFF88008D43000, 0xFFFFF8A0033DE51A)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 18/05/2017 15:33:07 your computer crashed
crash dump file: C:\Windows\Minidump\051817-19702-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0xFFFFFA801CB04778, 0x2, 0x1, 0xFFFFF80002F82EDC)
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 17/05/2017 22:20:57 your computer crashed
crash dump file: C:\Windows\Minidump\051817-15256-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0xFFFFFA8019EB7C7B, 0x2, 0x0, 0xFFFFF80002F22B2F)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 24/05/2017 18:57:21 your computer crashed
crash dump file: C:\Windows\Minidump\052417-13915-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EC1080)
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 24/05/2017 18:57:21 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EC1080)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Thu 18/05/2017 20:11:11 your computer crashed
crash dump file: C:\Windows\Minidump\051817-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0x1A (0x31, 0xFFFFFA80090234D0, 0xFFFFF88008D43000, 0xFFFFF8A0033DE51A)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 18/05/2017 15:33:07 your computer crashed
crash dump file: C:\Windows\Minidump\051817-19702-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0xFFFFFA801CB04778, 0x2, 0x1, 0xFFFFF80002F82EDC)
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 17/05/2017 22:20:57 your computer crashed
crash dump file: C:\Windows\Minidump\051817-15256-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F4C0)
Bugcheck code: 0xA (0xFFFFFA8019EB7C7B, 0x2, 0x0, 0xFFFFF80002F22B2F)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
I searched on my motherboard site to see if there's any drivers unfortunately I haven't found anything (http://www.ecs.com.tw/ECSWebSite/Product/Product_DOWNLOAD.aspx?DetailID=1505&CategoryID=1&DetailName=Feature&MenuID=24&LanID=0)
I took a look to a driver site and this is what it gave me(https://www.touslesdrivers.com/index.php?v_page=31&v_id=UPzbu6UY3TogdDKK) :
Here are my drivers that are our outdated
http://imgur.com/a/tQGx4
And here is what I got when I downloaded an update for them from this site:
http://imgur.com/PxMW5rn
The 2 first folders on the top have an Installer each I don't know which one to choose and I don't know If I should do this update at all.
Please help me, this is my first time posting on Tom's Hardware so if I did any errors please excuse me, Thank you.
Facebook
Twitter
Instagram