1. Joined : Oct 2016
    Posts : 1
    Windows 10 , 10.0, build: 14393
       12 Oct 2016 #1

    BSOD ntoskrnl.exe, ntkrnlmp.exe driver errors, can't identify the 3rd


    Hi There,
    Who can assist me with identifying the 3rd party driver that is causing my PC to crash with a BSOD. I have had several crashes, and for as much as I can identify all caused by one or more faulty/buggy driver(s).

    Much appreciated, rene

    PC-RENE-12_10_2016_134422_12.zip
      My System SpecsSystem Spec


  2. Joined : Apr 2014
    Space coast of Florida
    Posts : 4,055
    Windows 10 Pro X64 14393.105
       12 Oct 2016 #2

    You have 3 different kinds of memory installed. This can lead to problems like you are seeing (Bugcheck A for instance).

    Code:
    [Memory Device (Type 17) - Length 27 - Handle 0010h]
      Physical Memory Array Handle  000eh
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM0
      Bank Locator                  BANK0
      Memory Type                   01h - Other
      Type Detail                   0080h - Synchronous
      Speed                         1066MHz
      Manufacturer                  FF04000000000000
      Serial Number                        
      Asset Tag Number                          
      Part Number                   RMB2GB484CA4-13HC 
    [Memory Device (Type 17) - Length 27 - Handle 0011h]
      Physical Memory Array Handle  000eh
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM1
      Bank Locator                  BANK1
      Memory Type                   01h - Other
      Type Detail                   0080h - Synchronous
      Speed                         1066MHz
      Manufacturer                  FF04000000000000
      Serial Number                        
      Asset Tag Number                          
      Part Number                   RMB2GB484CA4-13HC 
    [Memory Device (Type 17) - Length 27 - Handle 0012h]
      Physical Memory Array Handle  000eh
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM2
      Bank Locator                  BANK2
      Memory Type                   01h - Other
      Type Detail                   0080h - Synchronous
      Speed                         1066MHz
      Manufacturer                  CE80000000000000
      Serial Number                        
      Asset Tag Number                          
      Part Number                   M378B5673FH0-CH9  
    [Memory Device (Type 17) - Length 27 - Handle 0013h]
      Physical Memory Array Handle  000eh
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM3
      Bank Locator                  BANK3
      Memory Type                   01h - Other
      Type Detail                   0080h - Synchronous
      Speed                         1066MHz
      Manufacturer                  4F01000000000000
      Serial Number                        
      Asset Tag Number                          
      Part Number                   TS256MLK64V3U
    Try removing the DIMMs in BANK 2 and BANK 3 and run for awhile, see how things are if okay theneither stay with 4GB or find 4 matching memory modules to run with.

    You could also try testing memory before doing this, to see what it shows you:

    ===================================================
    RAM:

    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    information   Information

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
    ===================================================

    Even if no errors, remove the 2 memory modules and test.

    Also, the BIOS in this PC is old, BIOS Release Date 07/21/2009 There are nor drivers for anything above Windows 7 and no drivers at all available on the HP web site for this PC.
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
BSOD caused by ntoskrnl.exe and ntkrnlmp.exe on startup
This happened after Dell came out and installed a new monitor in the machine. I am posting this from Safe Mode as we speak from the computer with the issue. I have tried running a chkdsk on the computer and it fixed some errors. I tried finding...
BSOD Crashes and Debugging
Windows 10 BSOD related to ntoskrnl.exe, ntkrnlmp.e
Recently I began experiencing a frequent BSOD. Error: DRIVER_POWER_STATE_FAILURE WhoCrashed says the following; This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of...
BSOD Crashes and Debugging
BSOD Randomly DRIVER_POWER_STATE_FAILURE ntoskrnl.exe and ntkrnlmp.exe
Hello, I've recently upgraded to windows 10 and I've encountered this problem many, many times. I've also done a clean install of Windows 10 afterwards, but the problem persists. I'm currently on the Asus X550J Laptop, with 8gb ram, i7 4710...
BSOD Crashes and Debugging
Solved BSOD - ntoskrnl.exe & ntkrnlmp.exe
Hi all! I've just encountered this BSOD and I tried to analyze it myself using WhoCrashed. It tells me that it was probably caused by ntoskrnl.exe & ntkrnlmp.exe. I've looked into it but I haven't been able to find a fix to this and I was wondering...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:24.
Find Us
Twitter Facebook Google+



Windows 10 Forums