Windows 8 and 8.1 Forums


How to debug BSOD on W8 caused by ntoskrnl or ntfs.sys :(

  1. #11


    Posts : 8
    Windows 8


    Well, I do not have another one so I'm installing a linux to be able to run some tests...
    I will launch a memtest during the night and will update this thread tomorrow.
    Thanks for your help.

      My System SpecsSystem Spec

  2. #12


    Posts : 8
    Windows 8


    Here are some news :

    I installed a new Windows and ran it at noon yesterday. No bsod so far but I did a first memtest with my 2 ram sticks to start and here is the result after one hour :
    Visionneuse images - Noelshack

    Well, I will contact my provider and test each stick in the meantime.
    Thanks !
      My System SpecsSystem Spec

  3. #13


    Posts : 2,480
    Windows 10 Pro x64


    Your RAM has errors. Please replace it.
      My System SpecsSystem Spec

  4. #14


    Posts : 8
    Windows 8


    Hey,

    I did replace my RAM with 2x2Go Corsair, Memtest is OK after 10 hours so that's great.
    Bsod are gone but I still have random crash (after 10 minutes or after 4 hours) on every games I'm playing. The crash won't only close the game, it will also crash every applications on background such as Firefox or Thunderbird... I got some freezes on youtube video also.
    Moreover, sometimes I can hear a "crick" sound coming from my computer when I open a video, a new folder, launch a game... It can't be the drive cause it's a SSD so... What could it be?

    I have the feeling that all this stuff is related to my problem but I can't be sure and I really don't know what is the composant which is failing. Could it be the power supply? This sound may be an electri arc, I don't know.
      My System SpecsSystem Spec

  5. #15


    Posts : 2,480
    Windows 10 Pro x64


    Please try to do this hw tests (skip the memory for now). Hardware Diagnostics
      My System SpecsSystem Spec

Page 2 of 2 FirstFirst 12
How to debug BSOD on W8 caused by ntoskrnl or ntfs.sys :(
Related Threads
Solved Having randons BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
:ar: THIS THREAD WAS SOLVED BY CHANGING THE MOTHER BOARD. THIS TOPIC WAS CHANGED TO TENFORUMS: Having randons BSOD caused by ntoskrnl.exe - Windows 10 Forums Since I bought my PC, randons BSOD appear (all of them caused by ntoskrnl.exe) >WHEA_UNCORRECTABLE_ERROR, ...
BSOD caused by ntoskrnl.exe randomly in BSOD Crashes and Debugging
Hi everybody, I have been experiencing some random BSOD with error 0x0000000a and 0x00000139 caused by driver ntoskrnl.exe. I have run my desktop for 1 year and seldom experienced such BSODs until this month. I have run memtest to 250% coverage and no errors are found. I also have run disk...
My computer, since I built it around 6 months ago, has been constantly crashing, 1-3 times per day. I have tried re-seating the ram modules and graphics card, and reinstalling windows 8. On the current install I have installed no third party drivers, and left everything to windows update. My...
I just bought a brand new Asus g750jm-bsi7n23 and I keep getting a BSOD called DRIVER_POWER_STATE_FAILURE which is being caused by ntoskrnl.exe. It is getting really irritating, because I just dished out $1,300 on a new laptop and it has already crashed 3-4 times. Any help would be GREATLY...
BSOD caused by dxgmms1.sys / ntoskrnl.exe in BSOD Crashes and Debugging
I have freshly installed windows 8.1 Enterprise (x64) and also installed the latest drivers for everything. My configuration: ASUS P8Z77-M Intel i5-3570K 2X4GB DDR3 Kingston HyperX Predator ATI Radeon HD6950 2GB WD 1TB Caviar Black CoolerMaster 550W Real Power
Hi All, I upgraded my PC from win8 to win8.1 and i get BSOD very frequently. Tried to solve it by update all drivers, but it doesn't helps. I ran memory diagnostic before, it show no errors. Please advice.:cry: Attached with my dump files. Thanks in advance
BSOD probably caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi folks - having some trouble troubleshooting a BSOD on a Lenovo Yoga 13. BSOD screen had dpc_watchdog_violation listed, but when running the minidump through Windbg I got to this: Probably caused by : ntoskrnl.exe ( nt+14dca0 ) Wasn't quite sure where to go from here seeing as that...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook