Forum Topic

Gives me BSOD problems (ntoskrnl.exe)

  • Lagi nalang nag BSOD yung pc ko. I conducted stress tests several times. Maghapon.. Di nagbu- bluescreen, And no problems with the hardware. Napansin ko rin na madalas mag crash mga running applications ko..
    Nakakainis na nakakailang format na rin ako.. Possible ba na software issue ito? (Software bug)?


    Here's the BSOD crash dumps :






    You have performed a crash dump test. The test succeeded and the crash dump file was properly written out.

    On Mon 1/28/2013 7:31:41 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012713-16754-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x41287, 0x400747, 0x0, 0x0)
    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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 1/28/2013 7:31:41 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: 0x1A (0x41287, 0x400747, 0x0, 0x0)
    Error: MEMORY_MANAGEMENT
    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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 1/28/2013 7:02:47 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012713-15927-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF8000347AD59)
    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 1/26/2013 11:26:02 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-16395-01.dmp
    This was probably caused by the following module: atapi.sys (atapi+0x1EE1)
    Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800035348A7)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atapi.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: ATAPI IDE Miniport Driver
    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 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 Thu 1/24/2013 3:55:15 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-17097-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034D242C, 0xFFFFF8800C893F40, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 1/23/2013 6:38:06 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012213-17690-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xAD8AB)
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF960000CD8AB)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    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 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 Mon 1/21/2013 11:48:24 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012113-18626-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3D (0xFFFFF88009640FB0, 0x0, 0x0, 0xFFFFF800032703A3)
    Error: INTERRUPT_EXCEPTION_NOT_HANDLED
    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 appears very infrequently.
    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 1/20/2013 5:09:02 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012013-15912-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x0, 0x1, 0xFFFFF80003293B63)
    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 1/19/2013 6:58:13 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011913-16504-01.dmp
    This was probably caused by the following module: atapi.sys (atapi+0x1EE1)
    Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF8000333C8A7)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atapi.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: ATAPI IDE Miniport Driver
    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 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 Sun 1/13/2013 6:51:07 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011313-20966-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF800033073B7)
    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 1/13/2013 7:08:49 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011213-28158-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF800032B4FB7)
    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 1/12/2013 12:43:15 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011113-67236-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3D (0xFFFFF88009DCCFB0, 0x0, 0x0, 0xFFFFF800032704A4)
    Error: INTERRUPT_EXCEPTION_NOT_HANDLED
    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 appears very infrequently.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 1/11/2013 6:04:41 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011013-20420-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035B8151, 0xFFFFF8800B2C2720, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 1/9/2013 8:55:14 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010913-25006-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
    Bugcheck code: 0xA (0x2000600052, 0x2, 0x1, 0xFFFFF8000337C0BF)
    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.




    Please help.. Thanks fellow friends :*(
  • try mo sir itest yung memory modules mo
  • ok ang memory sir e.. pati processor/ gpu... nag reformat ako ok na.. palagay ko mag software problem.
  • I have the same problem sir. OK na ba PC mo?
  • bump sir same tayo ng mobo ganto din prob ko ... mdami ako unit same specs ok yung iba ... ano ginawa mong reformat sir sang software nag kjaprob?
  • I\'ve downloaded the drivers from the Lenovo Website and also through the Access Connections software and the problem still persists. I followed the installation instructions and this error:

    Intel(R) PRO/Wireless Network Connection software is unable to install. Please verify that a \"Found New Hardware\" dialog box is not open and the installer is only launched once.

    still shows up when I try to install the driver. I\'ve tried going in the Device Manager to install the driver and this \"works\" in the sense that the computer will find the driver and install it, but once I try accessing the wireless device (to find the closest wireless point), my computer goes BSOD and I get the IRQL_NOT_LESS_OR_EQUAL error. Then with subsequent reboots, I will constantly get the same BSOD whenever the computer tries to access the wireless during the start up.
    <click here for link>

    -- edited by albabeti on Apr 01 2015, 05:35 PM