- Joined
- Apr 5, 2012
- Location
- Malaysia, South East Asia.
Guys ,i just got a BSOD on startup ( first time getting from this error )
I used " WhoCrashed " to see the dump file.
Files :
C:\Windows\Minidump\Mini092812-01.dmp
C:\Windows\memory.dmp
Bug Check Name :
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 9/27/2012 11:58:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092812-01.dmp
This was probably caused by the following module: ecache.sys (ecache+0x73C9)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFFFFF8C56E3C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 which cannot be identified at this time.
On Thu 9/27/2012 11:58:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ecache.sys (ecache+0x73C9)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFFFFF8C56E3C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 which cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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 actually 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.
Anyone have any idea what to do to resolve this ?? So im posting this right after i got the BSOD and i restarted the PC, so i not sure will this be OFTEN / even happen again in future.
But i doubt BSOD will just go away and happen all sudden for no reason.
Also i didn't install any new HARDWARE / SOFTWARE recently at all. I just use my PC as usual play games etc. Didn't even have any WINDOWS UPDATE recently.
Never even open the PC and did any cleaning which might caused some hardware loosen.
That's why im shocked to all sudden getting a BSOD !
I used " WhoCrashed " to see the dump file.
Files :
C:\Windows\Minidump\Mini092812-01.dmp
C:\Windows\memory.dmp
Bug Check Name :
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 9/27/2012 11:58:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092812-01.dmp
This was probably caused by the following module: ecache.sys (ecache+0x73C9)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFFFFF8C56E3C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 which cannot be identified at this time.
On Thu 9/27/2012 11:58:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ecache.sys (ecache+0x73C9)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFFFFF8C56E3C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 which cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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 actually 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.
Anyone have any idea what to do to resolve this ?? So im posting this right after i got the BSOD and i restarted the PC, so i not sure will this be OFTEN / even happen again in future.
But i doubt BSOD will just go away and happen all sudden for no reason.
Also i didn't install any new HARDWARE / SOFTWARE recently at all. I just use my PC as usual play games etc. Didn't even have any WINDOWS UPDATE recently.
Never even open the PC and did any cleaning which might caused some hardware loosen.
That's why im shocked to all sudden getting a BSOD !