not less or equal problem

G

Guest

Guest
Hello,

Every time I try to turn my computer on it crashes 3 or 4 times before it actually boots into windows 8. This has been happening for about a month now.
I don't think I have an anti-virus installed in my PC.

Anyways, can anyone help me?

My system specs

Intel(R) Core(TM)2 Duo CPU T6600 @2.2GHz 2.20 Ghz
4.00 GB(3.87 Usable)
64-Bit Operating System, x65 based processor

On the other hand, I also ran Whocrashed on the problem and it said this:


On Fri 5/3/2013 4:02:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050313-45599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0x42DB, 0x2, 0x1, 0xFFFFF802AC83A37F)
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 Sun 4/14/2013 12:41:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041413-14773-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0x5180, 0x2, 0x1, 0xFFFFF8029CCF6C17)
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 Sun 4/14/2013 3:41:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041413-15069-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0xFFFFFA800FE5802C, 0xF, 0x0, 0xFFFFF803A35E1A35)
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 Sat 4/13/2013 4:11:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041313-15802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xFC (0xFFFFF880192A7899, 0x800000012E659963, 0xFFFFF880192A7640, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 4/13/2013 12:41:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041313-16224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFFA800FEC5290, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
This problem might be caused by a 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 Tue 4/9/2013 4:02:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040913-15194-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0xA (0xFFFFFA80CD3E4F25, 0xF, 0x0, 0xFFFFF80141D70855)
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 Sun 4/7/2013 2:36:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040713-19936-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2D965)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80051E9038, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 be caused by a thermal issue.
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 Sat 4/6/2013 12:01:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040613-15818-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x7F (0x8, 0xFFFFF880009C7C30, 0x0, 0xFFFFF800E2E6CC2F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

41 crash dumps have been found and analyzed. Only 15 are included in this report. 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.

The whole analysis had more information, this was only a part of it.

Any help?