Windows 10: [BSOD] I got random BSOD with ntoskrnl, please save me!

Discus and support [BSOD] I got random BSOD with ntoskrnl, please save me! in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, my PC recently has been receiving a lot of random BSODs . It comes suddenly when I surf the internet, or watching youtube videos. I was... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by lynhbn, Apr 14, 2017.

  1. lynhbn Win User

    [BSOD] I got random BSOD with ntoskrnl, please save me!


    Hello, my PC recently has been receiving a lot of random BSODs . It comes suddenly when I surf the internet, or watching youtube videos.

    I was thinking that it all comes from my VGA card, but I can still play games such as Dota2 in Ultra settings for hours without any errors.

    I've already installed BlueScreen viewer then noticed something. Firstly it comes from Ntoskrnl.exe +14e7c0, then it changed to Ntoskrnl.exe +0x0000001e but I am not able to analyze the minidump file. Please help me!!! Thank you so much!

    Belows are my files, please help me to take a look!

    :)
     
    lynhbn, Apr 14, 2017
    #1

  2. BSOD ntoskrnl, plz help!

    Hello, I'm having bsod when I launch benchmark with sisoft sandra.

    I got 2 different bsod DRIVER_CORRUPTED_XPOOL and DRIVER_OVERRAN_STACK_BUFFER all with the same driver ntoskrnl.

    what to do?

    i'm using win10 64bit.

    thank you
     
    S_Bourghol, Apr 14, 2017
    #2
  3. While i was playing rust i got this random bsod

    Original Title: New bsod some help please

    Hello everyone, today while i was playing rust i got this random bsod it never happened before on my new system everything was working fine i have windows 10 16 GB ram,and gt x 970 graphic card can someone please check the bsod for me thank you all

    Dropbox - Error
     
    charbelbernaba, Apr 14, 2017
    #3
  4. philc43 Win User

    [BSOD] I got random BSOD with ntoskrnl, please save me!

    Hello lynhbn,

    Sorry for the delay in replying. I have looked at your crash dump files in the logs, the first two both indicate hardware related problems:
    Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffd98d7c700028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. 0: kd> !errrec ffffd98d7c700028 =============================================================================== Common Platform Error Record @ ffffd98d7c700028 ------------------------------------------------------------------------------- Record Id : 01d2b4d5b8a97b7b Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 4/14/2017 4:27:22 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffd98d7c7000a8 Section @ ffffd98d7c700180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000206a7 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffd98d7c7000f0 Section @ ffffd98d7c700240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : a7 06 02 00 00 08 10 00 - ff e3 ba 1f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffd98d7c700240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffd98d7c700138 Section @ ffffd98d7c7002c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 0 Bank 3) Status : 0xbe00000000800400 Address : 0x00003809c332c4aa Misc. : 0x000000000003ffff[/quote] The other errors suggest memory corruption whioch could be driver related or bad RAM.

    I would suggest you perform two tests and report back on the results:





    [BSOD] I got random BSOD with ntoskrnl, please save me! [​IMG]
    Diagnostic Test
    [BSOD] I got random BSOD with ntoskrnl, please save me! [​IMG]
    RAM TEST
    *Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums


    [BSOD] I got random BSOD with ntoskrnl, please save me! [​IMG]
    Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
     
    philc43, Apr 18, 2017
    #4
  5. lynhbn Win User
    Thank you so much philc43 for your comment. Sorry for my late reply. I just want to report about my analysis
    After plenty of BSODs, I try to unplug my dedicated sound card from my PC (I'm using Focusrite Solo Gen 1 as a device for recording & playback)
    After that, no BSODs happen for 2 weeks!
    I was just thinking that it is the root cause!

    But today, I suddenly expricenced BSOD again. This time the cause is from nvlddmkm.sys+620738 and ntoskrnl.exe
    *cry*cry*cry

    Please help me to take a look to my attached files. Thank you!!!!!*Sad*Sad*Sad
     
    lynhbn, Apr 26, 2017
    #5
  6. philc43 Win User
    Run the DM_Log_collector again and post a new set of files
     
    philc43, Apr 26, 2017
    #6
  7. lynhbn Win User
    Hi,

    I re-attached the file. Please help me to take a look.

    Best regards,
     
    lynhbn, Apr 27, 2017
    #7
  8. philc43 Win User

    [BSOD] I got random BSOD with ntoskrnl, please save me!

    Did you run the CPU and RAM tests? The first crash is hardware related but this can sometimes be triggered by a faulty driver.

    The second crash has indicated the following drivers may be involved.

    Code: BugCheck 1E, {ffffffffc000001d, fffff802cc53b6bc, fffff802cc891a40, ffffda003480dc10} *** WARNING: Unable to verify timestamp for athuw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athuw8x.sys *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : athuw8x.sys ( athuw8x+228060 )[/quote] Please update the NVidia driver. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

    The other driver is the wireless network adapter, your driver details are shown below:
    Code: 0: kd> lmvm athuw8x Browse full module list start end module name fffff808`25fa0000 fffff808`26270000 athuw8x T (no symbols) Loaded symbol image file: athuw8x.sys Image path: \SystemRoot\System32\drivers\athuw8x.sys Image name: athuw8x.sys Browse all global symbols functions data Timestamp: Tue May 14 05:06:43 2013 (5191B853) CheckSum: 002D0C6B ImageSize: 002D0000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] See if you can find more recent drivers for your wireless network card.
     
    philc43, Apr 27, 2017
    #8
  9. lynhbn Win User
    Thank you very much for your analysis. I've just updated the clean version for the vga driver and buy a new wifi adapter (because my previous one TL-WN722N_V1 do not have any native driver for windows 10)

    I'm monitoring if the BSOD may happen again, I will inform you soon.

    Best regards!
     
    lynhbn, Apr 5, 2018
    #9
Thema:

[BSOD] I got random BSOD with ntoskrnl, please save me!

Loading...
  1. [BSOD] I got random BSOD with ntoskrnl, please save me! - Similar Threads - BSOD got random

  2. ntoskrnl bsod

    in Windows 10 Software and Apps
    ntoskrnl bsod: My pc has been bsod-ing for 2-3 years now and i recently decided to try and fix it. I use bluescreen view and always see that the bsods are always caused by ntoskrnl.exe. heres all of the stuff ive to try and fix it.Used 1 8gb ram stick at a timeused different ram slotsused...
  3. ntoskrnl BSOD

    in Windows 10 Software and Apps
    ntoskrnl BSOD: Hello, I have quite a persistent problem here.I often get BSOD or straight out system restarts the latter don't have any trace in minidump. In the past few days, they were too recurrent and got to a point where I had to reinstall Windows because my laptop actually got slowed...
  4. Random BSOD ntoskrnl, ntkrnlmp executables

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD ntoskrnl, ntkrnlmp executables: I have a Lenovo laptop with the following specs: Intel Core i7-8550U 4C / 8T, 1.8 / 4.0GHz, 8MB Integrated Intel UHD Graphics 620 Intel SoC Platform 16GB Soldered DDR4-2400 512GB SSD M.2 2280 PCIe NVMe 13.9" UHD 3840x2160 IPS 300nits Glossy I started getting random...
  5. Got BSODs , please help me

    in Windows 10 BSOD Crashes and Debugging
    Got BSODs , please help me: Hello all, I got these following BSODs for a few times : INTERNAL_POWER_ERROR and MEMORY_MANAGEMENT . Here are the links of the minidumps : 061620-10250-01 061820-13375-01 After I got the MEMORY_MANAGEMENT BSOD , I ran DISM and scf/scannow and got this :...
  6. I got a random BSOD

    in Windows 10 BSOD Crashes and Debugging
    I got a random BSOD: Attached is the rar file with the minidump and the system info. It was a ramdon blue screen, computer works but very curious since the laptop is very new. Thank you. https://1drv.ms/u/s!Ans80qCg3IZRwxJCHAN8KRKGGdKv...
  7. Please review minidump - ntoskrnl bsod

    in Windows 10 BSOD Crashes and Debugging
    Please review minidump - ntoskrnl bsod: Minidump files can be found at https://1drv.ms/u/s!AkyF9KTuD2MFjHq9RkGAnQi2EIIQ?e=gLFpPS Please help diagnose what they can tell me is causing my BSOD. Thanks...
  8. Random BSODs (ntoskrnl,memory_management)

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs (ntoskrnl,memory_management): Hello, first timer here. Long story short, after i updated to windows 10 from 8.1 i started experiencing some randomly BSODs. So i downloaded the ISO and made a clean install.Immidiatelly after my newly formated pc i installed Avast,mozilla and Asrock's Suite to check for...
  9. Random BSOD CRITICAL_STRUCTURE_CORRUPTION or NTOSKRNL

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD CRITICAL_STRUCTURE_CORRUPTION or NTOSKRNL: Hi there! And thank you in advance for your help! AORUS-X7-DT-V6-30_10_2017__01924,84.zip Some time ago I started getting idle BSODs after reverting to an older System Image everything was fine until the creators update kicked in. Now I am getting random BSODs (not only...
  10. Bsod ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    Bsod ntoskrnl: Hi guys, Any help would be massively appreciated. My computer is BSOD at least two times a day. As far as I can tell, all drivers are up to date including Nvidia. Could somebody take a look at the attached and let me know if you find anything? I've ran a system check...