Windows 10: Random freezes or BSODs (In windows drivers)

Hi,

I've had many an issue with this PC before, but recently have realised that they are a good 3-6 months between them, and a good clean out usually fixes any issue. I was starting to have an issue a couple of weeks ago, so I cleaned out the PC and that sorted it for then. Since then yesterday suddenly my PC started freezing (and even once crashing) every single time it booted within an hour, since then I have been forced to use it in safe mode.

I've attached the collector thing.

I am not OC'ing any hardware.

I have ran chkdsk, seatools long drive self test (I am not sure of the result though as it crashed before I could check), sfc /scannow and DISM /Online /Cleanup-Image /CheckHealth. All returning no errors etc.

As I have had tonnes of issues with this PC I have ran memtest for over 50+ passes now with no issue, but will be happy to run it again, however I am leaning towards a driver issue, what do you think?

Thanks for any help in advance!

:)

 

Windows 10 Freezes randomly Minidump/Verifier file added

Hi!

I get these random freezes since I've updated to Windows 10. Did not happen with Windows 7. Freezes are random and take about 10-15sec each time. Driver Verifier causes BSOD.

MiniDump from Driver Verifier:

https://onedrive.live.com/redir?resid=7338DC61BA740D54!218&authkey=!ADeslHmeos0SJzE&ithint=file,dmp

MSInfo saved file:

https://onedrive.live.com/redir?resid=7338DC61BA740D54!219&authkey=!AEjosYPn7doNs_w&ithint=file,nfo

Anybody whom could please help me find the problematic driver/cause?

Best regards,

/Nader Iano

 

Drivers possibly causing random computer freezes/crashes

Hello,

I have a computer running windows 10 that over the last month has been experiencing seemingly random freezes and sometimes BSOD errors. I believe it is likely related to a driver, and wanted to paste my dump file here from the last crash to see if anyone
had any ideas.

Dump file:

MEMORY.DMP

Thanks

 

As the crash dump from today does not indicate any driver you will need to run Driver Verifier to see if it can pinpoint any drivers causing trouble. Unfortunately this will have to be run in normal mode not safe mode. PLease see the following tutorial and pay particular attention to the warnings. I strongly advise you to make backups of all your important files, have a system backup and turn on system restore points.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Hi,

as phil descriped running the driver verifier should be the first step you should do.

But what I see is, there are many different bugchecks in the dumpfiles.
The cause for different error codes are usually hardware and lower level problems.

1. There are many indices that indicate problems with the disks configuration. Maybe the disk itself or the controllers seem to have problems. There are signs and traces in the crash dumps which show problems and errors on storage/raid/ntfs/usb.

2. It seems theres an misconfigured hardware or software raid. Maybe wrong or incomplete RAID Level configuration?

3. Are u using special raid controller or an storage device which has raid and is connected via USB?

Have u look at the text which is marked red:


Code: 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (25.07.2017 01:24:35) [Windows 10] CAUSED BY: memory_corruption NTFS.sys [10.08.1990] * NT File System Driver (Windows System File) PROCESS: OSBuddy64.exe ffffe480`e018d028 fffff805`f3744304 crashdmp!CrashdmpWrite+0x204 ffffe480`e018d050 fffff805`f374eb50 crashdmp!Context+0xd0 ffffe480`e018d078 fffff805`f374eb50 crashdmp!Context+0xd0 ffffe480`e018d098 fffff801`3c0b699b hal!HalSetEnvironmentVariableEx+0x13b ffffe480`e018d0a8 fffff801`3c0c5a66 hal!HalpTimerUpdateApiConsumers+0x32 ffffe480`e018d100 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018d148 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018d3f8 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018d4e0 fffff805`f2429000 FLTMGR!FltpVerifierCodeSectionHandle <PERF> (FLTMGR+0x29000) ffffe480`e018d4e8 fffff805`f2400000 FLTMGR!FltpCleanupAfterDataScanConflict <PERF> (FLTMGR+0x0) ffffe480`e018d810 fffff805`f2e56700 NTFS!g_RpcBindingHandleBound <PERF> (NTFS+0x86700) ffffe480`e018d818 fffff805`f2400000 FLTMGR!FltpCleanupAfterDataScanConflict <PERF> (FLTMGR+0x0) ffffe480`e018d820 fffff805`f2429510 FLTMGR!FltpVerifierCodeSectionHandle <PERF> (FLTMGR+0x29510) ffffe480`e018d828 fffff805`f2400000 FLTMGR!FltpCleanupAfterDataScanConflict <PERF> (FLTMGR+0x0) ffffe480`e018d830 fffff805`f242930c FLTMGR!FltpVerifierCodeSectionHandle <PERF> (FLTMGR+0x2930c) ffffe480`e018d920 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018da10 fffff805`f2dfa65b NTFS!memset+0xdb ffffe480`e018da38 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018da88 fffff910`338c130f cdd!DrvCopyBits+0x4f ffffe480`e018de98 fffff910`335dd1d9 win32kbase!PushThreadGuardedObject+0x79 ffffe480`e018e108 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018e200 fffff805`f2dfa65b NTFS!memset+0xdb ffffe480`e018e308 fffff805`f2dda7df NTFS!NtfsPreRequestProcessingExtend+0x4f ffffe480`e018e378 fffff805`f2407572 FLTMGR!FltGetStreamContext+0x42 ffffe480`e018e3a8 fffff805`f2ddac15 NTFS!NtfsInitializeIrpContext+0x115 ffffe480`e018e3b8 fffff805`f2d2f141 fileinfo!FIStreamGet+0x51 ffffe480`e018e418 fffff805`f2ddb92d NTFS!NtfsFsdRead+0x1dd ffffe480`e018e438 fffff805`f2d21a94 fileinfo!FIPreReadWriteCallback+0x104 ffffe480`e018e448 fffff805`f2d4348c Wof!WofAcquireFileSystemRundown+0x44 ffffe480`e018e698 fffff805`f240563d FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x18d ffffe480`e018e708 fffff805`f24034d6 FLTMGR!FltpDispatch+0xb6 ============================================================================================================== 0x000000C2: BAD_POOL_CALLER (13.05.2017 11:30:16) [Windows 10] CAUSED BY: storport.sys ***** Invalid * Microsoft Storage Port Driver (Windows System File) cng.sys ***** Invalid * Kernel Cryptography, Next Generation (Windows System File) PROCESS: System ffffbf80`502b6608 fffff808`7f980950 cng!g_pool+0xb0 ffffbf80`502b6630 fffff808`7f980940 cng!g_pool+0xa0 ffffbf80`502b6698 fffff800`2161b810 hal!HalPutScatterGatherList+0x50 ffffbf80`502b66a8 fffff808`7feb81d2 storport!TranslateResultToScsiRequestBlock+0x1b80e ffffbf80`502b66c8 fffff808`7feac12c storport!RaidAdapterPoFxIdleComponent+0x2c ffffbf80`502b66f8 fffff808`7fe98e75 storport!RaidUnitCompleteRequest+0x4f5 ffffbf80`502b6828 fffff808`8192b492 amdppm!C1Halt+0x2 ffffbf80`502b6878 fffff808`7feacb68 storport!RaidpAdapterRedirectDpcRoutine+0x88 ffffbf80`502b6978 fffff808`7feacae0 storport!RaidpAdapterRedirectDpcRoutine ffffbf80`502b6b20 fffff808`7feacae0 storport!RaidpAdapterRedirectDpcRoutine ============================================================================================================== 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP (13.05.2017 10:38:24) [Windows 10] CAUSED BY: memory_corruption PROCESS: lsass.exe ffffb400`d50e3878 fffff809`e41db0d2 FLTMGR!FltpFsControlCompletion+0x12 ffffb400`d50e3a88 fffff809`e39ba103 NTFS!NtfsCleanupIrpContext+0x173 ffffb400`d50e3c18 fffff809`e39badef NTFS!NtfsInitializeTopLevelIrp+0x3f ffffb400`d50e49d8 fffff800`5b418ef5 hal!HalSendSoftwareInterrupt+0xa5 ffffb400`d50e4ba8 fffff800`5b418ef5 hal!HalSendSoftwareInterrupt+0xa5 ============================================================================================================== 0x0000003B: SYSTEM_SERVICE_EXCEPTION (12.05.2017 16:18:27) [Windows 10] CAUSED BY: hardware PROCESS: csrss.exe ffffdf81`8d31d090 ffff8bdb`5753b000 win32kfull!State <PERF> (win32kfull+0x33b000) ffffdf81`8d31d098 ffff8bdb`57200000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffffdf81`8d31d3d8 fffff80b`760c1dfb USBPORT!USBPORT_ProcessURB+0x7cb ffffdf81`8d31d428 fffff80b`76455720 usbccgp!WPP_becd29c949e535e2d495960e1cc8580a_Traceguids ffffdf81`8d31d4d0 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31d620 ffff8bdb`57264f0f win32kfull!NtUserCallNoParam+0x2f ffffdf81`8d31d698 fffff80b`762695c6 usbhub!UsbhGenDispatch+0x66 ffffdf81`8d31d8a8 fffff803`82e99ef5 hal!HalSendSoftwareInterrupt+0xa5 ffffdf81`8d31d918 fffff80b`7648241e hidusb!HumWriteReport+0x26e ffffdf81`8d31d958 fffff80b`76487100 hidusb!WPP_53aa6b43d48232cbe153da7efdb6be71_Traceguids ffffdf81`8d31daf0 fffff80b`764ba488 HIDCLASS!WPP_c88aa066c266392bb595528843f1b3bc_Traceguids ffffdf81`8d31db08 fffff80b`764a207e HIDCLASS!HidpMajorHandler+0x14e ffffdf81`8d31db98 fffff80b`764e2050 kbdhid!KbdHid_SetLedIndicators+0x2c0 ffffdf81`8d31dc38 ffff8bdb`57258dd0 win32kfull!RawInputThread ffffdf81`8d31dc48 ffff8bdb`57200000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffffdf81`8d31dc50 ffff8bdb`5753d9a0 win32kfull!State <PERF> (win32kfull+0x33d9a0) ffffdf81`8d31dc58 ffff8bdb`575a0000 win32kbase!DxgkEngColorFillViaGDI <PERF> (win32kbase+0x0) ffffdf81`8d31dc60 ffff8bdb`5773d574 win32kbase!__PchSym_ <PERF> (win32kbase+0x19d574) ffffdf81`8d31dc68 ffff8bdb`57200000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffffdf81`8d31dc70 ffff8bdb`5753ddf0 win32kfull!State <PERF> (win32kfull+0x33ddf0) ffffdf81`8d31dce0 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31dce8 ffff8bdb`57259884 win32kfull!RawInputThread+0xab4 ffffdf81`8d31dcf0 ffff8bdb`57259875 win32kfull!RawInputThread+0xaa5 ffffdf81`8d31dd08 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31dd20 ffff8bdb`57730200 win32kbase!gPowerDisplayState+0x10 ffffdf81`8d31ddf0 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31de00 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31de80 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31de88 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31ded8 fffff803`82e99ef5 hal!HalSendSoftwareInterrupt+0xa5 ffffdf81`8d31e3e0 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31e550 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31e568 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31e5e0 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31e6f0 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31e700 ffff8bdb`577302e0 win32kbase!gRemoteContext ffffdf81`8d31e768 ffff8bdb`57259874 win32kfull!RawInputThread+0xaa4 ffffdf81`8d31e850 ffff8bdb`574e64e0 win32kfull!`string' ffffdf81`8d31e928 ffff8bdb`575dc27e win32kbase!UserSessionSwitchLeaveCrit+0x2e ffffdf81`8d31e968 ffff8bdb`575dbfee win32kbase!UserThreadCallout+0x13e ffffdf81`8d31e9e8 ffff8bdb`575dc6e8 win32kbase!W32CalloutDispatch+0x388 ffffdf81`8d31ea48 ffff8bdb`575dc27e win32kbase!UserSessionSwitchLeaveCrit+0x2e ffffdf81`8d31ea88 ffff8bdb`5761a72e win32kbase!xxxCreateSystemThreads+0x12e ffffdf81`8d31eac8 ffff8bdb`57264f0f win32kfull!NtUserCallNoParam+0x2f ============================================================================================================== 0x0000003B: SYSTEM_SERVICE_EXCEPTION (10.05.2017 19:23:24) [Windows 10] CAUSED BY: memory_corruption PROCESS: csrss.exe ffff8900`2c165090 ffffacb5`46d3b000 win32kfull!State <PERF> (win32kfull+0x33b000) ffff8900`2c165098 ffffacb5`46a00000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffff8900`2c165408 fffff803`d97911c1 usbccgp!USBC_Dispatch+0x1b1 ffff8900`2c165428 fffff803`d97a5720 usbccgp!WPP_becd29c949e535e2d495960e1cc8580a_Traceguids ffff8900`2c1654d0 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c165620 ffffacb5`46a64f0f win32kfull!NtUserCallNoParam+0x2f ffff8900`2c165698 fffff803`d95b95c6 usbhub!UsbhGenDispatch+0x66 ffff8900`2c1657e8 fffff803`d74e1c44 WppRecorder!WppAutoLogTrace+0x164 ffff8900`2c165b18 fffff800`ba49f53d hal!HalRequestSoftwareInterrupt+0xcd ffff8900`2c165b98 fffff803`d98e2050 kbdhid!KbdHid_SetLedIndicators+0x2c0 ffff8900`2c165c38 ffffacb5`46a58dd0 win32kfull!RawInputThread ffff8900`2c165c48 ffffacb5`46a00000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffff8900`2c165c50 ffffacb5`46d3d9a0 win32kfull!State <PERF> (win32kfull+0x33d9a0) ffff8900`2c165c58 ffffacb5`46da0000 win32kbase!DxgkEngColorFillViaGDI <PERF> (win32kbase+0x0) ffff8900`2c165c60 ffffacb5`46f3d574 win32kbase!__PchSym_ <PERF> (win32kbase+0x19d574) ffff8900`2c165c68 ffffacb5`46a00000 win32kfull!ShrinkDIB_CY_SrkCX <PERF> (win32kfull+0x0) ffff8900`2c165c70 ffffacb5`46d3ddf0 win32kfull!State <PERF> (win32kfull+0x33ddf0) ffff8900`2c165ce0 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c165ce8 ffffacb5`46a59884 win32kfull!RawInputThread+0xab4 ffff8900`2c165cf0 ffffacb5`46a59875 win32kfull!RawInputThread+0xaa5 ffff8900`2c165d08 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c165d20 ffffacb5`46f30200 win32kbase!gPowerDisplayState+0x10 ffff8900`2c165df0 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c165e00 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c165e80 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c165e88 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c1660a8 fffff803`d9f533f5 dxgkrnl!SetPointerShapeForDisplaySource+0x55d ffff8900`2c1661e8 fffff803`d9f52620 dxgkrnl!DxgkReleaseSessionModeChangeLock+0xc0 ffff8900`2c1663e0 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c166550 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c166568 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c1665e0 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c1666f0 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c166700 ffffacb5`46f302e0 win32kbase!gRemoteContext ffff8900`2c166768 ffffacb5`46a59874 win32kfull!RawInputThread+0xaa4 ffff8900`2c166850 ffffacb5`46ce64e0 win32kfull!`string' ffff8900`2c166860 ffffacb5`46f328c0 win32kbase!gspklGlobalActive ffff8900`2c166928 ffffacb5`46ddc27e win32kbase!UserSessionSwitchLeaveCrit+0x2e ffff8900`2c166968 ffffacb5`46ddbfee win32kbase!UserThreadCallout+0x13e ffff8900`2c1669e8 ffffacb5`46ddc6e8 win32kbase!W32CalloutDispatch+0x388 ffff8900`2c166a48 ffffacb5`46ddc27e win32kbase!UserSessionSwitchLeaveCrit+0x2e ffff8900`2c166a88 ffffacb5`46e1a72e win32kbase!xxxCreateSystemThreads+0x12e ffff8900`2c166ac8 ffffacb5`46a64f0f win32kfull!NtUserCallNoParam+0x2f[/quote] Code: 2017-07-15 11:03:32 Warning: The following service is taking more than 3 minutes to start and may have stopped responding: User Data Storage_5718e5c 2017-07-20 10:45:02 Warning: The following service is taking more than 3 minutes to start and may have stopped responding: User Data Storage_eb32dc2 2017-07-21 10:02:55 Warning: The following service is taking more than 3 minutes to start and may have stopped responding: User Data Storage_10d517f5[/quote]
1) Did u run the correct version of memtest?
MemTest86+ - Test RAM - Windows 10 Forums


2) U should do an forced file system repair:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these five commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
sfc /scannow
chkdsk C: /F /R /X
fsutil dirty set C:

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...


3) U should also check your HDD with HDtune and CrystalDiskInfo:





Diagnostic Test

HDD TESTS


Run HDTune to check health and scan for errors.







Note It may take some time, but look for signs of any errors or failure.

You can also run a disk or health check using chkdsk. Refer to the tutorial for details of how to do this.

Take Screenshots of it and post it here.

 

I have set up driver verifier and will report back.

As for the RAID I have never fiddled with any of that, the PC came with windows installed on the default hard drive and I haven't changed or added anything since then.

 

Yep thats the memtest version I was using, I can run it again tonight though if you want to double check that?

As mentioned before I ran dism /restorehealth sfc/scannow and chkdsk yesterday, but can run them again with those other commands if it helps.

What part of crystal disk info and HDtune would you like me to test/screenshot?

Thanks!

 

If you run this version 8 passes or more you dont have to double check I think. Maybe an 10 pass run is worth a try.

Yes, please post screenshots from all tabs of hdtune and from crystaldiskinfo (theres just one)

But please dont do this when driver verfier is running. Do that testing stuf before or after driver verifier run.

Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
You can upload it to an cloud service like dropbox or onedrive.

 

I'll run a 10 pass tonight and let you know.

I'll upload the screenshots when the verifier is off, (should I turn it off after the first crash (if there is one)?)

Dump attached. (Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.)

I am running those commands now.

Thanks again, really appreciated! *Smile

 

Also do the commands need to be run in that exact order, its just last time I did chkdsk (lastnight) it took about 5 hours so I may do it overnight?

 

no, exact order isnt important.

 

Some very peculiar dates on your drivers

At least half a dozen in the Future.
In the event logs these immediately preceed the Bsod's

Where did you get your install media??


Roy

 

All done via either windows update (genuine), install cd's and the vendors websites, which ones stand out?

 

Thier mostly system drivers
Thats why i asked
Where did you get your install media from.

Roy

 

These strange dates for system drivers have appeared since the Creators Update, it seems to be an odd effect of how the dates are extracted and although it has been reported no explanation has been given.