locked
hal.dll and ntoskrnl.exe error RRS feed

  • Question

  • Greetings:

    I have moved my home brew computer from one wall to another and now ever since I moved it, it's crashing with errors of 0x9c, 0x124 and 0x101. I have used WhoCrashed to find out what caused the system to crash and according to it, hal.dll and ntoskrnl.exe have pretty much crashed the system, with some sprinkling of win32k.sys and ntfs.sys pulling up the rear. I just found that my BIOS was out of date and that has been updated however it only lessened the BSoD's to about once every day rather than 2-5 times a day. It seems that it happens more when I have to really put some processing power to the CPU, the computer just BSoD's and off it goes. I have about 15 crash files so far in minidump. I have attempted to upgrade to Windows 8, and Windows 8.1 still is producing the same issue. I'd just like to get this fixed so I can moderately enjoy Windows 8. 

    Thanks.

    Sunday, November 24, 2013 9:43 PM

Answers

  • WolfOrg

    Nive of 15 point to Intel.  Four are inconclusive, two misc.  If you have the expertise to re-seat the cpu (and while you are at it add thermal paste) that might be a good place to start

    BugCheck 9C, {0, fffff88002fdfc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff8800317cc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 124, {0, fffffa800ecff028, b2000000, 70150}
    Probably caused by : GenuineIntel
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff88002fdfc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 124, {0, fffffa800e95f028, b2000000, 70150}
    Probably caused by : GenuineIntel
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff880009f6c70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by WolfOrg Monday, November 25, 2013 4:38 PM
    • Unmarked as answer by WolfOrg Monday, November 25, 2013 4:44 PM
    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Monday, November 25, 2013 12:14 AM
  • WO

    If you hadn't moved it possible.  Given that you have and the problem started up I am thinking vibration/movement.  While you are in there you might as well do the thermal paste (artic silver) as it will make it run cooler.

    There is a really slim chance it is something other than the move but I am not real fond of co-ncidences.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Monday, November 25, 2013 1:34 AM
  • WO

    If it isnt heat the only thing I can suggest is to start pulling hardware off to see if something else isnt the problem.  My gut tells me its the CPU.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Wednesday, November 27, 2013 2:01 AM

All replies

  • Hello WolfOrg,

    If the problem started straight after you physically moved the machine, then this is likely to be a hardware problem.

    I would take anti-static precautions, and ensure that the RAM modules are securely seated.

    If necessary these may need to be taken out and then put back. Sometimes swapping them around works (Example: You have two RAM modules - take them both out and put them back in, but not back in their original sockets).

    Ensure there are no lose connections from the power supply to all areas of the machine.

    Run chkdsk to check the hard disk for physical errors (bad sectors).

    I hope this helps.

    Regards,

    Robert339

    Sunday, November 24, 2013 10:06 PM
  • Greetings Robert:

    I am an IT specialist, so I am well versed in this. I removed the RAM and put it back in. I have disassembled the box and put it back together.

    Sunday, November 24, 2013 10:08 PM
  • Hello WolfOrg,

    Understood! Your experience is likely to be greater than my own, however you may need to consider seeking out other compatible RAM to check if your current RAM modules may be damaged. As you know, anti-static precautions must be taken before touching the RAM. If such precautions were not taken, then the RAM may be damaged.

    Another matter occurs to me. If the motherboard had been in use for some time, it may have attracted a lot of dust which can cause shorting. If so, it needs to be carefully brushed so the dust is collected to a clear area within the case, and then vacuumed away using a special anti-static protected vacuum cleaner (example "Convac 3000").

    As you know, no attempt at repairing software installations can be successful if the cause of the problem still remains with the hardware.

    Do also check the hard disk for physical damage.

    In addition, I would also use a tester to check that the power unit is not faulty.

    Regards,

    Robert339.


    • Edited by Robert339 Sunday, November 24, 2013 10:31 PM
    Sunday, November 24, 2013 10:30 PM
  • Why the RAM though? Why are we hovering around the RAM?
    Sunday, November 24, 2013 10:38 PM
  • Hello WolfOrg,

    Perhaps the messages on the following webpage may be helpful, since it has one of your machine's symptoms, and also advises on the importance of testing the Memory.

    The testing method suggested, may perhaps be more convenient to you.

    http://www.sevenforums.com/bsod-help-support/23643-ntoskrnl-exe-bsod.html

    The RAM is one of the hardware items you need to be certain are working normally.

    I hope this helps.

    Regards,

    Robert339.



    • Edited by Robert339 Sunday, November 24, 2013 10:56 PM
    Sunday, November 24, 2013 10:54 PM
  • WO

    Those error codes are hardware related and we can tell you which from the DMP files.   You can use these instructions to find and upload the DMP files.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer.  They can be found here

    If you have any questions about the procedure please ask

    *

    @Robert339

    That thread is 3+ years old and not related to this problem.  USAMSA & I worked together on it.


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Sunday, November 24, 2013 11:49 PM
    Sunday, November 24, 2013 11:46 PM
  • https://skydrive.live.com/redir?resid=A0EB472D793676F3!717&authkey=!AFNnr70hvFNNLkE&ithint=folder%2c.dmp

    That should be all of it. 

    Sunday, November 24, 2013 11:52 PM
  • WolfOrg

    Nive of 15 point to Intel.  Four are inconclusive, two misc.  If you have the expertise to re-seat the cpu (and while you are at it add thermal paste) that might be a good place to start

    BugCheck 9C, {0, fffff88002fdfc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff8800317cc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 124, {0, fffffa800ecff028, b2000000, 70150}
    Probably caused by : GenuineIntel
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 101, {19, 0, fffff880009b3180, 4}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff88002fdfc70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 124, {0, fffffa800e95f028, b2000000, 70150}
    Probably caused by : GenuineIntel
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9C, {0, fffff880009f6c70, 0, 0}
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by WolfOrg Monday, November 25, 2013 4:38 PM
    • Unmarked as answer by WolfOrg Monday, November 25, 2013 4:44 PM
    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Monday, November 25, 2013 12:14 AM
  • Possible overheat problem? In the meantime - I will reseat it.
    Monday, November 25, 2013 12:17 AM
  • WO

    If you hadn't moved it possible.  Given that you have and the problem started up I am thinking vibration/movement.  While you are in there you might as well do the thermal paste (artic silver) as it will make it run cooler.

    There is a really slim chance it is something other than the move but I am not real fond of co-ncidences.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Monday, November 25, 2013 1:34 AM
  • After reseating the CPU, I found that the plastic clips worn and I had to get a new heat sink.

    Thanks for the help. 

    Monday, November 25, 2013 4:39 PM
  • I just got after posing the comment below a BSoD that was 124. Need the dump?
    Monday, November 25, 2013 4:45 PM
  • I am still getting 0x124 and 0x9C errors like no tomorrow. Ideas, short from getting a new processor?
    Tuesday, November 26, 2013 9:29 PM
  • WO

    If it isnt heat the only thing I can suggest is to start pulling hardware off to see if something else isnt the problem.  My gut tells me its the CPU.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by 暁北 Wednesday, December 4, 2013 12:22 PM
    Wednesday, November 27, 2013 2:01 AM