BSOD on startup, occurs regularly

Sorry but it seems to be executing in parts as soon as I paste the script in.
Does it matter though, all the information appears to be there?

I've also had another BSOD after giving the PC a cold boot after being left turned off for a few hours.
Its at least the 3rd time its had a BSOD from cold boot. I'm fairly sure I could recreate the BSOD if needed.

Link to the .dmp file:
Dropbox - MEMORY.DMP - Simplify your life

- - - Updated - - -

Memore Modules:

Tag BankLabel Capacity(GB) Manufacturer PartNumber Speed
--- --------- ------------ ------------ ---------- -----
Physical Memory 1 BANK 1 8 Corsair CMK16GX4M2D3200C16 2133
Physical Memory 3 BANK 3 8 Corsair CMK16GX4M2D3200C16 2133


Total Memory:
16GB

Total Memory Slots:
4

Used Memory Slots:
2
PS C:\Windows\system32>

Also another BSOD has occurred after boot-up.
Dropbox - MEMORY2.DMP - Simplify your life

1) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)


Please make sure that all devices attached to the computer are displayed in the "My Computer" section.


The latest dump, Tue May 14 22:46:05.638 2019 (UTC - 5:00), occurred during the use of a printer/fax displaying the process: spoolsv.exe

See if you are able to use the computer for several days without the printer attached.
If there was no printer/fax attached then this was a windows process.

There was no misbehaving driver displayed as the cause of the BSOD.

The memory dump files were the identical size so they were likely duplicate entries for the same BSOD crash.
After downloading the second memory it was confirmed as a duplicate.

zbook,

I have confirmed that my System Specs are all listed correctly.

There was no printer attached to the PC on that date. Although there was a scanner plugged in at one point there hasn't been for over a week and there has been multiple crashes without it attached.

What is the next step in troubleshooting? I feel like we are going in circles here and I'm not any closer to solving my issue.

1) Make a new restore point

2) Make sure the Macrium backup image is up to date

3) Restart windows driver verifier with these 19 simultaneous customized tests:
https://answers.microsoft.com/en-us/...3-c48669e4c983

4) Run the tool for 36 hours

5) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

6) If there are no BSOD then place the computer into safe mode with networking:
Boot into Safe Mode on Windows 10

plus1group said:

zbook,

I have confirmed that my System Specs are all listed correctly.

There was no printer attached to the PC on that date. Although there was a scanner plugged in at one point there hasn't been for over a week and there has been multiple crashes without it attached.

What is the next step in troubleshooting? I feel like we are going in circles here and I'm not any closer to solving my issue.

I'm sorry you feel like you are going round in circles. Looking at your crash dumps there is a consistent pattern that points to memory failure. With DDR4 memory modules there is no reliable method for testing them which is why you seem to be going round in circles, the tests sometimes reveal problems but not always. In your system the only way to test is to try one module at a time and operate your PC as normal. You work on the assumption that one module is faulty and try to identify which one it is. Operate with one module doing what you know will cause the BSOD. Then repeat with the other. Hopefully one will BSOD and not the other. This will be confirmation that you need to replace the RAM. There is also the possibility that both modules are faulty and so it is handy to have a known good module for testing, however, you may not have one and so we will assume for now that only one of your modules is faulty.

One further comment: the slots in the motherboard where the RAM is inserted can sometimes cause these errors so for full testing you will need to re check the modules in different slots to rule this out. Hopefully you can work out a test sequence such as test each RAM in the same slot, then repeat with other slots until you confirm what the problem is.

Sorry for the delayed reply.

I've been doing some tests and here is what I've found;
-Driver Verifier has not produced a BSOD once through at least the 36 hours that I tested it for. Having said that I don't use the PC very often.
-I've had 4 BSOD's this morning, on all of these occasions I had a external HDD plugged into various USB 3.0 ports. On all occasions the PC appears to boot to the start screen then BSOD's before I can type the password.
-When the external HDD has been removed I haven't been recreate a single BSOD.
-I also tried switching the RAM from slots 1 and 3 to 2 and 4. Based on that variable no BSOD occurred.

I've attached the .dmp file link and log collector results for one of the BSOD's this morning.

Microsoft services

Does this give us anything else to go on?