Windows 10: BSOD Randomly, multiple Error Codes but all from same address

Like the title sais i have been getting BSOD randomly every few days for the last 2 weeks, there is nothing in particular i have been able to find that triggers this. The BSOD is always caused by Driver ntoskrnl.exe + 14e7co. I recently built this PC about 3 weeks ago as im taking it to University with me.

I've attached a zip file of 2 of my most recent BSOD and the dm log collector file i was specified to do so, thanks for the assistance.

:)

 

DRIVER_OVERRAN_STACK_BUFFER Windows 10

Hello Microsoft Community,

I have been getting BSODs recently so much and the error code is DRIVER_OVERRAN_STACK_BUFFER

I have a Acer Laptop with

i5-8250U

Nvidia GeForce MX150

6GB DDR4 Ram

1 TB HDD

The BSOD happens Randomly

And i have searched on Google and i found out it's driver issue and i got other BSOD code and it's driver error too but i didn't do any driver changes recently

Moved from: Windows / Windows 10 / Devices & drivers

 

Same address but different passwords!

My cell phone "My Phone" address is different than my computer's "My Phone" address and now I can't find the data that I synchd to the computer. Unfortunately, the passwords are the same! Should I change the sending or the receiving address...and how
to do it???

 

Agreed that all the dumps indicate ntoskrnl but that is not a driver, it's part of the Windows kernel and not the cause of the problem. It just happens to be in control (which it often is) when the problem occurs.

All the dumps indicate some kind of memory corruption. This can be caused by defective RAM or by a faulty driver. You have 16GB of ram so lets check that first and if okay then turn on Driver Verifier and see if that shows anything.

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. It can take 12 to 20 hours to run 8 passes against 16GB of ram so be patient.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

 

Ok i will do these two things when i get back from work after college, in the meantime i had another BSOD late last night but this time it didn't show ntoskrnl as the cause. It showed a driver named FLTMGR.sys, Ive attached another log like before with the new BSOD on. Thanks again for the assistance.

 

The latest dumpfile also mentioned memory management.
Did you already tested your memory?

According to your manual the recommend memory configuration when using 2 modules are Dimm A2 and Dimm B2.
You have used Dimm A1 and A2.
Change this to A2 and B2 and maybe this will stop the BSOD.

 

I did what you said and installed the modules into Slots A2 and B2 and the computer refused to boot, i could still access the bios fine but the second i tried to boot windows the screen would freeze and no output on mouse or keyboard. I swapped the modules back to A1 and A2 and it boots fine now. Any idea why this might be? Also i did the Mem test and it came back with 0 errors.

My RAM if it helps - Corsair CMK16GX4M2A2666C16 Vengeance LPX 16GB (2x8GB) DDR4 2666Mhz CL16 XMP 2.0 High Performance Desktop Memory Kit, Black: Amazon.co.uk: Computers & Accessories

 

According to the Corsair forum your memory must be compatible see AMD Ryzen DDR4 Compatibility - The Corsair User Forums

But according to the dumpfile you are running it at 2133 mhz.

Are you using the XMP 2.0 settings?
Did you check the BIOS if the correct clock timings and voltages are used?
Did you try to set the settings manually?
What happens if you install only 1 memory module at once ? (system Boot up or not with each of the module installed).
Did you test your memory with only 1 module installed? ( it happens that with 2 modules tested no faults, with 1 module faults).

 

I tried to enable XMP (D.O.C.P) and the PC refused to load at all, it would cycle on and back off continuously. The only way i could fix this was to load into the bios and change it back was by removing one of the modules and the computer booted with one module in dimm A2, i tested the other module in this dimm and it worked fine too so i dont think the RAM is the issue. the voltage for the ram was set to 1.2v which is the recommended amount for the modules. I'll test B1 and B2 dimm slots when i get back from work

 

When you make changes like putting the RAM in different slots it is always a good idea to reset the BIOS settings to default values and in some cases you might have to use the jumper to clear all CMOS values before it will boot. @lifetec is right, you need to use the recommended way to insert your RAM (slots A2 and B2) if you want to take advantage of the dual channel configuration and use D.O.C.P. to get the maximum speed.

 

Before a dump is saved, the data in the RAM is validated to prevent the BSOD from saving corrupted data to the disk.
The following indicates that this may be an issue with the RAM.
Code: Event[463]: Log Name: System Source: volmgr Date: 2017-03-16T19:09:40.897 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-66NLTIG Description: Crash dump initialization failed! 21/03/2017 21:16 Windows Error Reporting Fault bucket BAD_DUMPFILE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 761a779c-4d4f-43cb-b429-437bceb8cf13 Problem signature: P1: 50 P2: ffff829380dd36b8 P3: 0 P4: fffff8028936550f P5: 2 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\032117-25828-01.dmp \\?\C:\Windows\Temp\WER-49859-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16EE.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 80a11096-14ec-4fa0-9a3f-423b94be3ee4 Report Status: 0 Hashed bucket: 21/03/2017 19:47 Windows Error Reporting Fault bucket BAD_DUMPFILE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 22130ca7-f2c4-41cd-9e66-6f16b72d501e Problem signature: P1: 3d P2: fffff803d390dd38 P3: fffff803d390d560 P4: 0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\032117-27359-01.dmp \\?\C:\Windows\Temp\WER-48187-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D06.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: d53bdeff-c905-4ba0-ad18-6508d0302f3b Report Status: 0 Hashed bucket:[/quote]