and thank you .

IRQL NOT LESS OR EQUAL
Started by
lonewolf11
, Jan 12 2013 08:14 AM
#16
Posted 16 January 2013 - 12:42 PM

and thank you .
#17
Posted 16 January 2013 - 01:15 PM

You would have to open the system up and look. Is it a laptop or desktop?
#18
Posted 16 January 2013 - 02:01 PM

Laptop.
#19
Posted 16 January 2013 - 02:33 PM

Ok on the bottom of the laptop there should be a latch door that is marked with memory or ram. There will be a screw in the latch that you take out and when you open it you can see the memory module or modules.
I would suggest just running the memtest86 program and check it all at one time.
I would suggest just running the memtest86 program and check it all at one time.
#20
Posted 25 January 2013 - 06:34 PM

Another crash
On Sat 26/01/2013 12:21:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-46753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x76 (0x0, 0xFFFFFA800C0596E0, 0x6, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
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 driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
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 26/01/2013 12:21:27 AM GMT 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: 0x76 (0x0, 0xFFFFFA800C0596E0, 0x6, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Bug check description: This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
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 26/01/2013 12:21:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-46753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x76 (0x0, 0xFFFFFA800C0596E0, 0x6, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
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 driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
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 26/01/2013 12:21:27 AM GMT 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: 0x76 (0x0, 0xFFFFFA800C0596E0, 0x6, 0x0)
Error: PROCESS_HAS_LOCKED_PAGES
Bug check description: This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






