Windows 10: Different BSOD´s, mostly on boot

Hello,

i have many bsod. Sometimes every day, mostly every 2 or 3th.
Most time they occure on Startup, but the last one was during a download from Steam and sometimes there is nothing for days.

There were many more, but i reinstalled my os one time.

I already tried memtest, reinstall Windows 10, only 1 ram out of 2, win debug tool but i cant find the error.
Im near to throw my pc out of the window... *cry

The Zip from your tool is attached

:)

 

blue screen

i keep getting constant bsod on my windows 10 laptop.

So i installed a different windows 10 but i still get the occasional bsod

Ive observed its mostly after i do a windows update..

please help

***Post moved by the moderator to the appropriate forum category.***

 

How to retrieve my Windows 10 product key

Hi,

It will make a huge difference... mostly noticeable at boot, but program loading as well...

 

The latest dumpfile is
Code: BugCheck 12B, {ffffffffc00002c4, 83b, 11d1f830, ffffe2808645d000} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 000000000000083b, physical page number Arg3: 0000000011d1f830, zero Arg4: ffffe2808645d000, zero Debugging Details: ------------------ BUGCHECK_STR: PAGE_NOT_ZERO CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: MemCompression[/quote] Usual causes:* Hardware memory error

It looks that your memory is faulty
Please start with diagnosing the system RAM first.
You can use the free tool "Memtest86+" to stress test the RAM.

How to run "Memtest"
MemTest86+ - Test RAM - Windows 10 Tutorials
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

 

<LocalGenuineState>SL_GEN_STATE_INVALID_LICENSE</LocalGenuineState>

please activate Windows or get a valid license for further help

 

Attachment 121280

I have a valid license but not activated cause i reinstalled win10 but my pc is still useless at this moment.

Anyway, thanks so far.

 

In a few of the dumpfiles there is mentioning of NTFS.sys.

Did you already test your HD and SSD for faults.
Is the firmware of your SSD up to date.

In the unloaded driver modules i found many NTIOLib_X64.sys
Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.

Recently (Nov 2014) there have been numerous instances of this driver in memory dumps. Analysis reveals that they are scattered throughout the filesystem by the installed MSI command utilities. For now I suggest uninstalling them all.
Driver Update Site: MSI Global - The best gaming gear maker in the world

One of the MSI utilities is Ramdisk, are you using this one?

You said;

Another MSI utility is Fast Boot are you using this one?

 

To be 100% sure every faulty Driver is gone i reinstalled, once again, Windows.
Checked my SSD´s with ssd-z and it seems like ist everything ok.
Installed every Driver from msi Homepage and after second boot i got my first bsod on boot.
This time i havent installed any msi tool.

It is attached *Sad

 

The last dumpfile is
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 139, {3, ffffc3806831c1f0, ffffc3806831c148, 0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: ffffc3806831c1f0, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffc3806831c148, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ TRAP_FRAME: ffffc3806831c1f0 -- (.trap 0xffffc3806831c1f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffff830836fd1ca0 rbx=0000000000000000 rcx=0000000000000003 rdx=ffff83082ea5d540 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80129cce807 rsp=ffffc3806831c380 rbp=0000000000000000 r8=ffff83082d9e7a20 r9=ffff83083a61b540 r10=0000000000000000 r11=ffff83082e2f5ce0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!ExDeferredFreePool+0x1067: fffff801`29cce807 cd29 int 29h Resetting default scope EXCEPTION_RECORD: ffffc3806831c148 -- (.exr 0xffffc3806831c148) ExceptionAddress: fffff80129cce807 (nt!ExDeferredFreePool+0x0000000000001067) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x139 PROCESS_NAME: System CURRENT_IRQL: 1 ERROR_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen. EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Er is een bufferoverschrijdingsfout opgetreden voor stack-buffer in deze toepassing. Via deze overschrijdingsfout kan een kwaadwillige gebruiker de controle over deze toepassing verkrijgen. EXCEPTION_PARAMETER1: 0000000000000003 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre EXCEPTION_STR: 0x0 LAST_CONTROL_TRANSFER: from fffff80129bd5629 to fffff80129bca510 STACK_TEXT: ffffc380`6831bec8 fffff801`29bd5629 : 00000000`00000139 00000000`00000003 ffffc380`6831c1f0 ffffc380`6831c148 : nt!KeBugCheckEx ffffc380`6831bed0 fffff801`29bd5990 : ffffbc7c`020df0e0 00000000`00000000 00000000`000000e0 fffff801`29ac6b17 : nt!KiBugCheckDispatch+0x69 ffffc380`6831c010 fffff801`29bd4973 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0 ffffc380`6831c1f0 fffff801`29cce807 : ffffd408`50c3c140 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf3 ffffc380`6831c380 fffff801`29ccc86d : ffff8308`2f7e8de0 ffffd408`50c3c140 ffffd408`50c3c140 00000000`00000000 : nt!ExDeferredFreePool+0x1067 ffffc380`6831c400 fffff804`1650721b : ffff8308`2f9df450 ffffd408`51ccc018 00000000`00000000 ffff98fa`00000020 : nt!ExFreePoolWithTag+0x86d ffffc380`6831c4e0 fffff804`16ebbc2f : ffff8308`2fae6d20 ffff8308`2fae6d20 ffffd408`51e289d0 fffff804`16f35077 : FLTMGR!FltReleaseFileNameInformation+0xab ffffc380`6831c520 fffff804`164d81f8 : ffff8308`2fae8340 ffffd408`51ccc018 ffffd408`50f0be28 ffffffff`00000017 : fileinfo!FIStreamCleanup+0xbf ffffc380`6831c580 fffff804`165044bf : ffffd408`50f0be30 00000000`00000000 00000000`00000000 ffffd408`54827d58 : FLTMGR!DoReleaseContext+0x78 ffffc380`6831c5c0 fffff804`165062fe : ffffd408`50f0be28 00000000`00000705 ffffffff`ffffffff ffffd408`548277e0 : FLTMGR!FltpDeleteContextList+0xaf ffffc380`6831c5f0 fffff804`16507dd2 : ffffd408`50f0bde0 ffffd408`50c44180 ffffd408`50f0bd02 00000000`00000705 : FLTMGR!CleanupStreamListCtrl+0x4a ffffc380`6831c630 fffff801`29f75cde : 00000000`00000000 fffff804`16f6e05b ffffc380`6831c760 ffffc380`6831ca00 : FLTMGR!DeleteStreamListCtrlCallback+0x92 ffffc380`6831c670 fffff804`17014fb0 : ffff8308`2fae85f0 ffffd408`50f0bde8 ffffc380`6831c7a8 ffffd408`50c44180 : nt!FsRtlTeardownPerStreamContexts+0x5a ffffc380`6831c6c0 fffff804`17014daf : ffffd400`01010000 00000028`5cdeaa00 00000000`00000000 00000000`00000000 : NTFS!NtfsDeleteScb+0x130 ffffc380`6831c750 fffff804`16f656f3 : ffffd408`50f0bee0 ffff8308`2fae85f0 00000000`6366744e fffff801`29ccc34b : NTFS!NtfsRemoveScb+0x5f ffffc380`6831c7a0 fffff804`17014b30 : ffff8308`2fae84b0 ffffc380`6831ca00 ffffd408`51ccc018 00000000`00000001 : NTFS!NtfsPrepareFcbForRemoval+0x63 ffffc380`6831c7e0 fffff804`16f7ede0 : ffffd408`51ccc018 ffffc380`6831c8e3 ffff8308`2fae88c0 ffff8308`2fae84b0 : NTFS!NtfsTeardownStructures+0x90 ffffc380`6831c860 fffff804`1705e6cb : ffffc380`6831ca38 ffff8308`2fae88c0 ffffc380`6831ca00 ffff8308`0000000a : NTFS!NtfsDecrementCloseCounts+0xd0 ffffc380`6831c8a0 fffff804`17068b8e : ffffd408`51ccc018 ffff8308`2fae85f0 ffff8308`2fae84b0 ffffd408`50c44180 : NTFS!NtfsCommonClose+0x40b ffffc380`6831c970 fffff801`29b16fd9 : fffff801`29e3d100 ffffd408`558e3280 fffff801`00000000 fffff801`00000000 : NTFS!NtfsFspCloseInternal+0x1a2 ffffc380`6831cb00 fffff801`29a82729 : 00000000`00000000 00000000`00000080 ffffd408`50c2b5c0 ffffd408`558e3280 : nt!ExpWorkerThread+0xe9 ffffc380`6831cb90 fffff801`29bcf9d6 : fffff801`29dc2180 ffffd408`558e3280 fffff801`29a826e8 00000000`00000246 : nt!PspSystemThreadStartup+0x41 ffffc380`6831cbe0 00000000`00000000 : ffffc380`6831d000 ffffc380`68316000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80129ac6b63 - nt!MiMakeDriverPagesPrivate+3af [ fa:93 ] fffff80129ac6bad - nt!MiMakeDriverPagesPrivate+3f9 (+0x4a) [ fa:93 ] 2 errors : !nt (fffff80129ac6b63-fffff80129ac6bad) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_large FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c} Followup: memory_corruption ---------[/quote] Again in the stack many references to NTFS.sys
Do you have update your SSDs to the latest firmware?
Are your SSDs compatible with your mobo, see supportpage.
Do you have the latest BIOS installed, if not maybe there is a newer version with better compatibility for SSD etc.

All your drivers seems to be up to date.
Maybe Driver Verifier will point to a specific faulty driver?

You can enable "Driver Verifier" according to instructions from the below link.
Driver Verifier - Enable and Disable in Windows 10
"Verifier" is a Microsoft's own tool to stress test third party drivers and find the buggy one. If it detects a violation, a blue screen will be created immediately and the dump will give us the name of offending driver straight forward. After enabling "Verifier" , system will be a bit slow and laggy during to the background verification process. After you got two or more blue screens, please upload the new crash dumps and we will know whether the issue is caused by third party drivers or low level hardware (a verifier enabled dump which blames Windows system files is a clear confirmation of hardware problem).
"Verifier" should be only used to monitor third party drivers. Selecting Microsoft system drivers is totally unnecessary and doing so may make the system non bootable.