hello there i have crashed every time i boot up "turn on not restart" to the windows with BSOD with different errors :

BAD_POOL_HEADER , kernel security check failure , memory mangment , NTFS_FILE_SYSTEM and other.

those BSOD's comes every startup i mean every time i turn on my pc but after the windows collect the inf. and restart , i boot normally into windows , but on next day i turn my pc on , i get an error BSOD then restart after collect info. then boot to windows normally .

my PC :

i5-4670K | 2x GTX 760 SC EVGA ACX SLI | ASUS Z87-A | 4x 4 GB Corsair Vengeance 1600mhz | Seasonic Gold X-850W | 120 Samsung 840 SSD | WD 1TB Blue | Corsair C70 Black Case | Windows 8.1 PRO x64 Monitor DELL U2312HM | RAZER 2013 accessory

• Edited by Meryqat Saturday, February 22, 2014 6:40 AM

Could you upload the minidump file that we can analyze it?

Advanced system settings --> Advanced --> Settings --> Write debugging information (Small memory dump)

Dump files are located to the %SystemRoot%\Minidump folder.

• Edited by T. Kujala Saturday, February 22, 2014 8:49 AM

here is the file :

https://onedrive.live.com/redir?resid=8A668A19B0841354%21482

Hi

Check this document, and find the solution there

http://msdn.microsoft.com/en-us/library/ff557433(v=vs.85).aspx

• Edited by britishdhez Monday, February 24, 2014 3:09 AM

These crashes were related to memory corruption (probably caused by a driver). 

Please run this test to find which driver is causing the problem.  
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

Driver verifier (for complete directions see our wiki here) Co-Authored by  JMH3143

Hi,

A STOP 0x24 error is an error that involves the NTFS.sys driver - which is the driver for the filesystem on your hard drive.
As such,it is very likely that something in the storage sub-system is causing this. CHKDSK is the tool of choice for fixing NTFS problems.

So,in addition to Zig mentioned,I suggest you run the CHKDSK command on all hard drives to check the result.

Regards,

i did the chkdsk not help :(

here is the minidumb files after the verifier test :

https://onedrive.live.com/redir?resid=8A668A19B0841354%21632

Meryqat

The one driver verified DMP file was related to your video driver (nvlddmkm.sys).  There is a known problem with the december 2013 driver (yours).  I would install a much older driver (say 6 months) until a new and less buggy driver is released.

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\New folder\030714-20734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`47605000 PsLoadedModuleList = 0xfffff800`478c9990
Debug session time: Fri Mar  7 08:47:56.423 2014 (UTC - 5:00)
System Uptime: 0 days 0:01:42.124
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 224, ffffe000045b1900, fffff80001d42295}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9b295 )



DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000224, Handle value being referenced.
Arg3: ffffe000045b1900, Address of the current process.
Arg4: fffff80001d42295, Address inside the driver that is performing the incorrect reference.

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  nvspcaps64.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80047c716a8 to fffff80047752ca0

STACK_TEXT:  
ffffd000`27381758 fffff800`47c716a8 : 00000000`000000c4 00000000`000000f6 00000000`00000224 ffffe000`045b1900 : nt!KeBugCheckEx
ffffd000`27381760 fffff800`47c76f98 : ffffe000`045b1900 00000000`00000000 00000000`00000000 fffff800`47c803ac : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`273817a0 fffff800`47b3ee73 : 00000000`000000c0 ffffe000`001759e0 ffffd000`27381c20 00000000`00000000 : nt!VfCheckUserHandle+0x1b8
ffffd000`27381880 fffff800`479af5d5 : ffffe000`045bec00 ffffc000`00000002 ffffe000`001759e0 ffffd000`27381900 : nt! ?? ::NNGAKEGL::`string'+0x10503
ffffd000`27381920 fffff800`479f2861 : 00000000`00000000 00000000`00000000 ffffd000`27381950 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
ffffd000`27381970 fffff800`479f21d1 : ffffc000`099727d0 ffffc000`099727a0 00000000`00000000 ffffc000`099727d0 : nt!CmObReferenceObjectByHandle+0x29
ffffd000`273819b0 fffff800`4775e4b3 : ffffc000`00086c50 ffffd000`27381bc0 00000000`00000000 fffff800`479d0a4e : nt!NtSetValueKey+0x135
ffffd000`27381b30 fffff800`47756900 : fffff800`01d42295 00000000`00000008 ffffd000`27381db1 00000000`00000013 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`27381d38 fffff800`01d42295 : 00000000`00000008 ffffd000`27381db1 00000000`00000013 ffffffff`80000b88 : nt!KiServiceLinkage
ffffd000`27381d40 00000000`00000008 : ffffd000`27381db1 00000000`00000013 ffffffff`80000b88 ffffd000`273829ac : nvlddmkm+0x9b295
ffffd000`27381d48 ffffd000`27381db1 : 00000000`00000013 ffffffff`80000b88 ffffd000`273829ac ffffd000`00000004 : 0x8
ffffd000`27381d50 00000000`00000013 : ffffffff`80000b88 ffffd000`273829ac ffffd000`00000004 00000000`00000000 : 0xffffd000`27381db1
ffffd000`27381d58 ffffffff`80000b88 : ffffd000`273829ac ffffd000`00000004 00000000`00000000 ffffe000`00154880 : 0x13
ffffd000`27381d60 ffffd000`273829ac : ffffd000`00000004 00000000`00000000 ffffe000`00154880 00000000`00000224 : 0xffffffff`80000b88
ffffd000`27381d68 ffffd000`00000004 : 00000000`00000000 ffffe000`00154880 00000000`00000224 fffff800`00160014 : 0xffffd000`273829ac
ffffd000`27381d70 00000000`00000000 : ffffe000`00154880 00000000`00000224 fffff800`00160014 ffffd000`273828ba : 0xffffd000`00000004


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+9b295
fffff800`01d42295 488b4dcf        mov     rcx,qword ptr [rbp-31h]

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  nvlddmkm+9b295

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc

FAILURE_BUCKET_ID:  0xc4_f6_nvlddmkm+9b295

BUCKET_ID:  0xc4_f6_nvlddmkm+9b295

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc4_f6_nvlddmkm+9b295

FAILURE_ID_HASH:  {ef78d4e5-5a2f-ec7e-90e0-5dacbf4d6f2e}

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