Windows 10: Regular BSOD after Win 10 upgrade from 8.1

Hi, I'm experiencing issues much like those reported here: Random BSODs following update to W10Pro from W8.1Pro..

Regular, intermittent BSOD in Win10 since the upgrade. Never experienced a BSOD in the previous two years with this laptop running Win 8x.

I'm attaching the mini dump files. Hoping someone can point me in the right direction to determine which driver(s) are causing the problem.

Thanks.

Edit: Updated on 8.21 with file created with the utility downloaded from this forum

:)

 

System freezing at regular intervals after windows 10 update

Hi team,

Mine is a HP laptop with i7 and 12 GB RAM configuration. I have upgraded from Windows 8.1 to windows 10.

I had no issues in Win 8 or Win 8.1 but after recent update to Win 10 I face a terrible issue of system freezing very frequently with regular intervals.

I have no black screen problem or any other issues. The only issue I face is system freezing for about 5 secs at regular intervals (say some 60 secs once).

Let me know if there is a fix for this?

If not, tell me how to roll back to Win 8.1?

How do I find on which date I have upgraded to Windows 10?

 

Blue screen of death (BSoD) error 0xc000021a windows10

Thank you.

I upgraded win 10 from win 8.1 and it was activated.

I just figured out that my third party antivirus conflicted with win 10 and causes bsod. I uninstalled it and every thing is fine.

For further info, it was bkav antivirus pro.

 

hello, Sunsethill. I have looked at your last several dump files and this is what they all say.

Code: MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 000000000000003f, The subtype of the bugcheck. Arg2: 0000000000000285 Arg3: 00000000a7b9786f Arg4: 00000000f1da952e Debugging Details: ------------------ SYSTEM_SKU: ASUS-NotebookSKU SYSTEM_VERSION: 1.0 BIOS_DATE: 10/01/2012 BASEBOARD_PRODUCT: N56DP BASEBOARD_VERSION: 1.0 BUGCHECK_P1: 3f BUGCHECK_P2: 285 BUGCHECK_P3: a7b9786f BUGCHECK_P4: f1da952e ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation. The data read from storage does not match the original data written. This indicates the data was corrupted by the storage stack, or device hardware.[/quote] Would you please add any additional system specs to the bottom left of your last post by clicking system specs and edit system specs. Please add tour hard drive.

Please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Please let me know the results. Do you have an ISO file of Windows 10 10240 or the install media for it?

 

Hi and thanks for the reply. I've added more information about my system and also attached a new set of files. The scannow process found no errors.

Attachment 33469

 

The last upload included 6 dump files dated 8/23. 5 of the 6 stated

Code: Use !analyze -v to get detailed debugging information. BugCheck 1A, {3f, f6ac5, 3bc404c0, da68a739} Probably caused by : memory_corruption ( nt!MiValidatePagefilePageHash+285 ) Followup: MachineOwner[/quote] The other one stated
Code: MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 000000000000003f, The subtype of the bugcheck. Arg2: 00000000000035d8 Arg3: 00000000d43b000d Arg4: 0000000077773860 Debugging Details:[/quote] ---------

Please Run Memtest86+




Information Please download from this site only Memtest86+ - Advanced Memory Diagnostic Tool in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

It is a long test and should take you around 9-10 hours to run it. It requires a minimum of 8 complete passes unless you get an error. If you see an error, you can stop the test. Even 1 error is a fail. You can start it at night and let it run over night.

 

I should point out that four days ago I installed a new Radeon driver and the laptop didn't crash until this morning after I installed the free version of Avast anti virus. I subsequently uninstalled Avast about 5 hours ago and there was just one crash after that... I think Avast is responsible for 5 of the 6 crash reports mentioned in your post. Are you aware of issues with Avast and Windows 10?

 

I am only aware that many of the Anti Virus programs have not been optimized for Windows 10 yet. Whether Avast is one of them, I don't know. You can run this utility to completely remove it. Avast Uninstall Utility | Download aswClear for Avast Removal. I see no mention of Avast in the dump files. This is your first dump file.

Code: Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\steve\AppData\Local\Temp\Temp2_LAPTOPWIN8-Sun_08_23_2015_191245_65.zip\082315-31281-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\SymCache*Symbol information Symbol search path is: SRV*C:\SymCache*Symbol information Executable search path is: Windows 8 Kernel Version 10240 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 10240.16431.amd64fre.th1.150810-2333 Machine Name: Kernel base = 0xfffff800`6fa83000 PsLoadedModuleList = 0xfffff800`6fda8030 Debug session time: Sun Aug 23 06:46:48.196 2015 (UTC - 5:00) System Uptime: 0 days 0:31:45.981 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ......... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {3f, f71f0, ec5c7df0, 543ec6ac} Probably caused by : memory_corruption ( nt!MiValidatePagefilePageHash+285 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 000000000000003f, The subtype of the bugcheck. Arg2: 00000000000f71f0 Arg3: 00000000ec5c7df0 Arg4: 00000000543ec6ac Debugging Details: ------------------ BUGCHECK_STR: 0x1a_3f CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre TRAP_FRAME: ffffd00024186080 -- (.trap 0xffffd00024186080) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffd000241862d0 rbx=0000000000000000 rcx=ffffd000244f3000 rdx=ffffd000244f3000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8006fba4c90 rsp=ffffd00024186210 rbp=000000ddc775af92 r8=000000ddc775aef0 r9=ffffd000244f3ea0 r10=000000ddc775aef0 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!RtlDecompressBufferXpressLz+0x50: fffff800`6fba4c90 418b02 mov eax,dword ptr [r10] ds:000000dd`c775aef0=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8006fca227d to fffff8006fbd0d00 STACK_TEXT: ffffd000`24185c38 fffff800`6fca227d : 00000000`0000001a 00000000`0000003f 00000000`000f71f0 00000000`ec5c7df0 : nt!KeBugCheckEx ffffd000`24185c40 fffff800`6fbf4d24 : ffffe000`2004e580 00000000`00010000 ffffd000`24185d80 ffffe000`2004e560 : nt!MiValidatePagefilePageHash+0x285 ffffd000`24185d00 fffff800`6fab2b32 : ffffe000`1a367c78 ffffd000`24185ee8 ffffe000`1a367c78 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x15424 ffffd000`24185e50 fffff800`6faa223d : 00000000`c0033333 ffffe000`1a367c78 000000dd`c775aef0 ffffd000`00000000 : nt!MiIssueHardFault+0x1b2 ffffd000`24185f30 fffff800`6fbd9dbd : ffffd000`00000000 ffffd000`241869d0 ffffd000`241863c8 ffffd000`00000031 : nt!MmAccessFault+0x39d ffffd000`24186080 fffff800`6fba4c90 : ffffd000`244f3000 ffffd000`244f3000 00000000`00001000 fffff800`6fb48f84 : nt!KiPageFault+0x13d ffffd000`24186210 fffff800`6fb48f84 : ffffe000`1eaa8050 fffff800`6fd06920 ffffd000`244f3000 ffffd000`24186400 : nt!RtlDecompressBufferXpressLz+0x50 ffffd000`24186230 fffff800`6fb94c6e : 00000000`00000002 000000dd`c775aef0 ffffe000`1eaa8050 00000000`00000000 : nt!RtlDecompressBufferEx+0x64 ffffd000`24186280 fffff800`6fb94aae : ffffe000`1e0ac9c0 ffffc6eb`a6e620c0 ffffe000`1a9ae040 fffff800`6fb9627c : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x186 ffffd000`24186360 fffff800`6fb948b5 : 00000000`00000002 ffffe000`21dfa210 ffffe000`1eaa8050 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6 ffffd000`241863c0 fffff800`6fb945ed : ffffe000`ffffffff 00000000`00000aef fffff6bf`00000269 ffffe000`1e0ac9c0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1 ffffd000`24186460 fffff800`6fb93cad : ffffd000`24186650 ffffe000`1e0ac9c0 00000000`00000040 ffffe000`1a558520 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1 ffffd000`24186520 fffff800`6fb93be1 : ffffe000`1eaa8000 ffffe000`1e0ac9c0 ffffe000`1eaa8000 fffff800`6fb93bc8 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x91 ffffd000`24186590 fffff800`6faff1f5 : ffffe000`1e0ac9c0 ffffd000`24186650 ffffe000`1eaa91d4 fffff800`6fb69cb0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x19 ffffd000`241865c0 fffff800`6fb93af3 : 00000000`00000003 fffff800`6fdc62c0 ffffe000`1a9ae000 ffffe000`1eaa8000 : nt!KeExpandKernelStackAndCalloutInternal+0x85 ffffd000`24186610 fffff800`6fb925b8 : ffffe000`1e0ac9c0 00000000`00000801 ffffe000`1eaa8000 00000000`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xb7 ffffd000`241866e0 fffff800`6fb9225f : ffffe000`1e0ac9c0 ffffe000`1e0ac9c0 ffffe000`1eaa8000 fffff800`6fdc62c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1c8 ffffd000`24186740 fffff800`6fb90401 : 00000000`0000000c ffffe000`1e4c1f50 00000000`00000001 ffffe000`1e4c1ea0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc7 ffffd000`241867d0 fffff800`6fb90295 : ffffe000`1e4c1e50 ffffd000`24186890 ffffd000`00000001 00007ff5`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165 ffffd000`24186850 fffff800`6fab4881 : ffffd000`3000ee32 ffffd000`241868e0 00000000`67ea7d00 ffffe000`1d19e8c8 : nt!SmPageRead+0x75 ffffd000`24186890 fffff800`6fab2ae8 : 00000000`00000002 ffffe000`1d8a4c78 ffffe000`1e4c1e50 00000000`00000000 : nt!MiIssueHardFaultIo+0x129 ffffd000`24186910 fffff800`6faa223d : 00000000`c0033333 ffffe000`1d8a4c78 00007ff5`eccf93b8 00000008`00000000 : nt!MiIssueHardFault+0x168 ffffd000`241869b0 fffff800`6fbd9dbd : ffffe000`1a558080 00000000`00000000 00000000`00000000 ffffe000`1df81980 : nt!MmAccessFault+0x39d ffffd000`24186b00 00007ffb`71d4384e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d 00000008`2eeff2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`71d4384e STACK_COMMAND: kb FOLLOWUP_IP: nt!MiValidatePagefilePageHash+285 fffff800`6fca227d cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiValidatePagefilePageHash+285 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 55c9bcb6 IMAGE_VERSION: 10.0.10240.16431 IMAGE_NAME: memory_corruption BUCKET_ID_FUNC_OFFSET: 285 FAILURE_BUCKET_ID: 0x1a_3f_nt!MiValidatePagefilePageHash BUCKET_ID: 0x1a_3f_nt!MiValidatePagefilePageHash ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1a_3f_nt!mivalidatepagefilepagehash FAILURE_ID_HASH: {08ffd102-c8c9-2cf6-fee5-98ecbf727366} Followup: MachineOwner[/quote]