ntoskrnl.exe has caused BSOD


  1. Posts : 9
    64
       #1

    ntoskrnl.exe has caused BSOD


    I have had 4 BSOD.
    Today, I was streaming using to Twitch with QuickSync on a Intel i3 2120.
    Boom a BSOD. I was also downloading something on steam also.
    I have noticed something very interesting in the "BlueScreenView" Application.
    3 of the .dmp files have been caused by the "ntoskrnl.exe"
    My 2nd BSOD cause was caused by "PLTGC.sys"
    I think this was because of too much CPU usage or some driver I have no idea but what I do know is that while these BSOD's were happening I would not read what happened cause it went away in 5 seconds.
    i3 2120 3.3 ghz
    sapphire radeon hd 7950
    Asrock z87 motherboard.
    Corsair Vengeance 8GB of RAM
    Last edited by craftingffa; 20 Aug 2014 at 14:29.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2
      My Computer


  3. Posts : 9
    64
    Thread Starter
       #3

    I have and I also provided the .zip


    Also there is now another BSOD and while I was browsing nothing but then while using steam it happened.
    It's name was atikmdag.sys
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Where is the zip then?
      My Computer


  5. Posts : 9
    64
    Thread Starter
       #5

    Very Sorry


    I thought I uploaded it.
    Anyway its there now.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    And still it is incomplete.

    Upload your MSINFO32.nfo file.

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.

    I will be back again after 18/19 hours.

    _________________________________________
    Code:
    BugCheck D1, {0, 2, 8, 0}
    
    *** WARNING: Unable to verify timestamp for PLTGC.sys
    *** ERROR: Module load completed but symbols could not be loaded for PLTGC.sys
    Probably caused by : PLTGC.sys ( PLTGC+3e2b )
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm PLTGC
    start             end                 module name
    fffff880`0445e000 fffff880`045ee000   PLTGC    T (no symbols)           
        Loaded symbol image file: PLTGC.sys
        Image path: \SystemRoot\system32\drivers\PLTGC.sys
        Image name: PLTGC.sys
        Timestamp:        Thu Nov 15 07:34:25 2012 (50A44DA9)
        CheckSum:         00153102
        ImageSize:        00190000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  7. Posts : 9
    64
    Thread Starter
       #7

    Ok


    There ya go :)
    If you need anything else to solve the problem please ask..
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    It is Plantronics GameCom. (c:\windows\system32\drivers\pltgc.sys).

    Search for a possible update to the driver from Plantronics Gamecom.
      My Computer


  9. Posts : 404
    Dual Booting Windows 7 64-Bit Ultimate Edition and Fedora 16.
       #9

    Hello,

    This, should be informative.
    Also, I had the same problem once and I ended up pin pointing it to memory problems. Don't be scared though, its one of the possible reasons of all the possible reason.
    If you have spare memory modules, try swapping them with your current ones. If it is working good, we know your sticks are bad.
    Also, you mentioned aitkmdag, I solved this one by installing the drivers from windows update (downgrading from the one on ATI's website)

    Hope this helps.
    ybl
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:43.
Find Us