Randoms BSOD since ~1 week. WhoCrashed - ntoskrnl.exe and ntkrnlmp.exe

Hello there,

After browing the Internet for about 5 full days and still getting my BSODs, I'm creating this thread because of how desperate this is making me.

I've tried formating and reinstalling Windows three times, with two different boot ISOs.
The second seemed to worked better than the first (who did almost nothing beside making me loose 3hours, because the install was ****ed up and I couldn't install W7 SP1. Hence why I switched to a second ISO with SP1 already built-in).

Anyhoo. I'm now with Windows 7 Pro 64bits with SP1 installed, and after rebooting after a few installs, and I had 3-4 BSODs while booting before it finally working.

Here's the WhoCrashed analyze :

Code:

On Sat 16/03/2013 22:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-7675-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Sat 16/03/2013 22:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-7597-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F45D1C, 0xFFFFF880046246A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sat 16/03/2013 22:35:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F45D1C, 0xFFFFF880046246A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sat 16/03/2013 22:34:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-7628-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR

The sfc /scannow keeps getting errors too (can't repair files) (uploaded as attachment).

chkdsk is clear
I've ran a Memtest for 2hours and got no error. I'll try running it for an entire day if I can't get anything better since then.

Edit: SF.rar added
Also worth noting that I have troubles when Windows session has booted (explorer.exe not working sometimes, or Desktop Window Management stopped working).

Please post the files following: Blue Screen of Death (BSOD) Posting Instructions

Are you having BSOD's on a vanilla install of windows?

Start with hardware diagnostics here: Diagnostics

2 out of 3 dumps are corrupted. Are/were you overclocking any hardware?

Start by testing RAM and HDD:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo Standard Edition
• How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

No need to test the SSD. There are no tools for testing SSD's.

The caution indication can be converted to good using CrystalDiscInfo. Click on the caution Button, you will get another window ....


In the resulting window, there are three sliders in the left. Drag them to the ultimate left, and notice the values at the right side are converting to zeros.


Now click the apply button, and notice that the caution is gone.

Hello,

everything was fine and I didn't get crashes since Saturday. But today as I booted I got one again, here's the report :

Code:

On Tue 19/03/2013 12:26:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-8533-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002BB75E8, 0xFFFFF88002BB6E40, 0xFFFFF80002EBDB45)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Not the first time I see a ntfs.sys crash, as it was one of the 3 reasons I had BSOD's before starting my formating-spree trying to fix them.


(PS.: Memtest TBD this night)

Edit: Had another one while my D:\ HDD was solicited doing a Repair on a game install:

Code:

On Tue 19/03/2013 13:59:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-7332-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053DB640, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I need the info from the SF diag tool grab: Blue Screen of Death (BSOD) Posting Instructions

From the text above I believe you are having either bad RAM or bad Hard drive(s).

Please proceed with memtest and let us know the results when completed.

Nothing suggestive from those dumps so I will wait for the results from memtest.

• STOP 0x00000024: NTFS_FILE_SYSTEM
  
  Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

• STOP 0x0000001A: MEMORY_MANAGEMENT
  
  Usual causes: Device driver, memory, kernel