Windows 7: BSoD at random times, error 0x000000C4 (STOP): Ntfs.sys

1. The initial 'Probably caused by' source was the ntoskrnl.exe binary
2. No analysis was available through '!analysis -v'
3. Having activated the 'Driver verifier', I restarted normally. The login screen appeared, but when I logged in, another BSoD appeared, but the dump didn't work (stuck, I rebooted forcefully). Still the Ntfs.sys file
4. I restarted again in normal mode, letting the system finish to work on the HDD (the little light stopped flashing intensively). When I logged, BSoD as before. Still the Ntfs.sys file
5. I restarted in Safe Mode, then I could log in without problem. No new DMP file existed in the Minidump directory, proof that the dump indeed didn't work at all.
6. I downloaded, burned and rebooted on the MemTest86+ software, making only 1 pass on the whole RAM, without error. I stopped there because I already have enough suspicions about some other hardware component...
7. Having rebooted under normal mode, I am now running Prime95, if by any chance that's useful...

1. The system's filesystem driver crashes (Ntfs.sys)
2. When the verifier has been activated the system is unable to write to the disk (that's in coherence with a filesystem's crash: no access to it)
3. Filesystem is one of the most immediate thing used, the crash at login time probably means that an early faulty action has been done

• Troubleshoot Application Conflicts by Performing a Clean Startup

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

• Hard Drive Diagnostic Procedure

• SeaTools for Windows

• SeaTools for DOS
• SeaTools for DOS tutorial

• Speccy - System Information - Free Download

What antivirus do you use?

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

• SFC /SCANNOW Command - System File Checker

• Dump Files - Configure Windows to Create on BSOD
  

• Anti-rootkit utility TDSSKiller

• Free Online Virus Scanner | ESET

1. I configured Windows to make a clean boot (without startup software) and I reactivated drivers verifier to check if the BSoD was still happening. Good news: it doesn't. Seems maybe the problem came from somewhere else
2. I downloaded and installed CrystalDiskInfo and exported the informatio nfrom it. Lighter then pictures, I copied data with the provided function (Edit > Copy) to make a text file with all the information. You'll find that as attachement
3. I configured Windows to make small memory dumps and not kernel memory dumps anymore. I'll check information in those dumps at the next occurrence of a BSoD
4. I downloaded the drive testing utility from Seagatefor my HDD. I burned it and I am about to start the test

1. I ran the SeaTool's 'Long test' on my Seagate primary drive (where the OS is installed). No error at all.
   Since it took 1h 1/2, I didn't make the check for the other HDD. I install all my applciations on the first one anyway, the second one is storage.
2. I discovered something very interesting about the BSoD on boot with the drivers verifier: if I startup with every application and all services but one, the BSoD disappears. Then I activated that service only and deactivated all startup programs and other services and the BSoD came back.
   The service is called ASLDR and it is the program from ASUS which captures hotkeys. No dump has ever been made with those ones.
3. I then used the whole day to seek on the ASUS support website every last version of every driver (the ones listed for my computer are old, probably the ones available when the model went out).
4. I tried again with the verifier but with the very same service triggers the very same behavior.
   I just can't remove that service, or the vast majority of my keyboard shortcuts (screen luminosity, sound volume, keyboard lightning, diaporama mode, touchpad toggle, etc.) don't work anymore.
   When booting without the service with the verifier, I tried something funny: going in the directory of the service binary and start it manually... Immediate BSoD, the same as before again.

• Stop 0x124 - what it means and what to try

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {4, fffffa80041a0038, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000004, PCI Express Error
Arg2: fffffa80041a0038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  b

STACK_TEXT:  
fffff880`033fba78 fffff800`03615a3b : 00000000`00000124 00000000`00000004 fffffa80`041a0038 00000000`00000000 : nt!KeBugCheckEx
fffff880`033fba80 fffff800`031a7b13 : 00000000`00000001 fffffa80`0417cb10 00000000`00000000 fffffa80`0417c1b0 : hal!HalBugCheckSystem+0x1e3
fffff880`033fbac0 fffff880`0119dbcf : fffffa80`00000750 fffffa80`0417cb10 00000000`00000000 fffffa80`0419f010 : nt!WheaReportHwError+0x263
fffff880`033fbb20 fffff880`0119d5f6 : 00000000`00000000 fffff880`033fbc70 fffffa80`04161d80 fffff980`09641000 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`033fbb80 fffff800`03095e1c : fffff880`033d3180 fffff880`033fbc70 fffffa80`04161d80 00000690`4ecbec01 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`033fbbf0 fffff800`03091ca2 : fffff880`033d3180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`033fbd80 00000000`00000000 : fffff880`033fc000 fffff880`033f6000 fffff880`033fbd40 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS

BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS

Followup: MachineOwner
---------

Start Menu\Programs\COMODO	Public:Start Menu\Programs\COMODO	Public
Start Menu\Programs\COMODO\COMODO Antivirus	Public:Start Menu\Programs\COMODO\COMODO Antivirus	Public

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    • Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Version du BIOS/Date	American Megatrends Inc. 207, 25/12/2009