Windows 10: Intermittent BSOD, no discernible pattern.

Been getting BSODs on a several month old pc that I built.

I just went through Device Manager and updated all the drivers that it was able to automatically update, but I don't know that that would have fixed the problem.

I've uploaded the requested information and any help would be greatly appreciated. Thanks!

:)

 

Windows 10 1607 performance degrades significantly between reboots

Thank you Gerry for this very detailed and helpful response. I've downloaded RAMMAP and will test this further today to see if I can discern any patterns in the standby usage.

Best,

Philip

 

Losing sound and start menu/taskbar simultaneously

Checking in again; I'm still getting the issues. Unfortunately they seem to occur in no discernible pattern, so it's very hard to duplicate. I'm trying to update any more drivers in case there's something I missed.

 

Hi alias,

Welcome to the 10forums.

Please update your Razer software, it has a few old drivers.
Please uninstall Google Chrome, it has caused several issues for a lot of users.
Please check the BIOS and verify the voltage and frequency of the memory is supported by both the memory and motherboard.
Please test your hard drives using SeaTools and chkdsk, with SSD please only chkdsk.
Please test your memory using MemTest86+
Please run driver verifier if both the hard drives tests and MemTest86+ both come clean.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.






Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums






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 follow this tutorial to run driver verifier.

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 when you have a bluescreen, whatever 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 in safe mode driver verifier, 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.

Code: STACK_TEXT: ffffd000`23314e38 fffff801`f93655c5 : ffffd000`23314f70 ffffc000`14fe9ac8 00000000`00000000 ffffe000`06c088c8 : nt!IoGetRelatedDeviceObject+0x12 ffffd000`23314e40 fffff801`f8eb871f : ffffd000`23315170 ffffd000`23315328 ffffe000`04108af8 00000000`00000001 : nt!FsRtlAcquireFileForCcFlushEx+0x51 ffffd000`233150f0 fffff801`f8ec1aa7 : 00000000`00000000 ffffb000`7a62a400 00000000`00000000 ffffd001`56704800 : nt!MmFlushSection+0x19b ffffd000`233151b0 fffff801`f8f1f58a : ffffe000`03d6faa8 00000000`00000000 ffffe000`00000000 00000000`00000000 : nt!CcFlushCachePriv+0x6b7 ffffd000`233152b0 fffff801`091b968d : ffffc000`15cce700 ffffd000`23315770 ffffe000`06c088c8 ffffc000`15cce701 : nt!CcFlushCache+0x16 ffffd000`233152f0 fffff801`091b7ae3 : ffffe000`06c088c8 ffffc000`15cce700 ffffe000`06c088c8 00000000`00000000 : NTFS!NtfsFlushUserStream+0xb9 ffffd000`23315370 fffff801`091379f0 : ffffc000`183f1f30 ffffe000`0648ea00 ffffc000`183f1f30 ffffe000`0648ea00 : NTFS!NtfsFlushVolume+0x423 ffffd000`233154f0 fffff801`0912d97d : ffffe000`06c088c8 ffffe000`0648ead0 ffffe000`020c8db0 ffffe000`00516101 : NTFS!NtfsVolumeDasdIo+0x188 ffffd000`233155a0 fffff801`09110312 : ffffe000`06c088c8 ffffe000`0648ead0 00000000`00000201 ffffe000`0d000000 : NTFS!NtfsCommonRead+0x1d44d ffffd000`23315740 fffff801`07b051c4 : ffffe000`00ebc8f0 ffffe000`0648ead0 ffffe000`0648ead0 ffffe000`0648ee70 : NTFS!NtfsFsdRead+0x1f2 ffffd000`233157f0 fffff801`07b03a16 : 00000000`000007ff ffffd001`56713000 00000000`00000401 00000000`00000801 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4 ffffd000`23315870 fffff801`f92b51fb : 00000000`00000000 ffffd000`23315951 ffffe000`04d6ef20 00000000`00100081 : FLTMGR!FltpDispatch+0xb6 ffffd000`233158d0 fffff801`f92b4e47 : ffffe000`04d6ef01 00000000`00000004 ffffe000`04d6ef70 ffffe000`04d6ef20 : nt!IopSynchronousServiceTail+0x16b ffffd000`233159a0 fffff801`f8fdd963 : fffff6fb`5ffe95c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x667 ffffd000`23315a90 00007ffa`80a8355a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000099`9d6ad248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`80a8355a[/quote] Code: MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xffffd000249e83e0 ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE BUCKET_ID: MEMORY_CORRUPTION_STRIDE[/quote] Code: DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: chrome.exe ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre[/quote] A write error, a driver tried to write to invalid or wrong memory address.
Code: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffa806486b268, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff803a5548ae0, address which referenced memory[/quote] Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU and cooling system.How to fill in your system specs:

 

Thank you! I will get back to you with results on this as I won't have time to do these things until Friday, most likely.

 

Take the time you need, there is no rush.

 

Update:

I noticed that the BSODs seem like they happen when my computer is waking up from sleep or hibernate mode. This isn't always the case, but the last several times it has been. Don't know if that helps.

To Do list Progress:
Please update your Razer software, it has a few old drivers. - Done, using Razer Synapse. Hopefully, that got all of them.

Please uninstall Google Chrome, it has caused several issues for a lot of users. - Not done yet, I really prefer this browser, so I'd like to keep it unless it does end up being one of the reason for the crashes and there isn't a fix.

Please check the BIOS and verify the voltage and frequency of the memory is supported by both the memory and motherboard. - I'm not sure how to check whether or not the voltage and frequency are supported, but all of the options are on "auto" in bios and the voltage is 1.5v and the frequency is 1333MHz.

Please test your hard drives using SeaTools and chkdsk, with SSD please only chkdsk. - Done, both came back clear

Please test your memory using MemTest86+ - Done, 8 passes 0 errors.

Please run driver verifier if both the hard drives tests and MemTest86+ both come clean. - Next on the list, will update again when finished.