Windows 10: BSOD when updating W10 Insider Preview (installation)

Now that the disk errors have been corrected the OP needs to attempt the upgrade again. If it continues to fail then I think MS needs to be sent feedback in case it is a problem that relates to the new insider build.

 

I did. And got BSOD again.

I don't know if it's build-related, as I've seen only few people having this issue? Also it happened to me on the latest 2 builds.

I left Memtest86+ running when I left to work this morning. Will post the new minidumps when I get back home.

 

It seems it managed to do only 3 passes in 11 hours using only 1 core. If I used 4/4 it got stuck.

Here are the new dumps.DESKTOP-1FK4B9B-Tue_11_28_2017_174248_26.zip

 

I would expect the memtest86+ to require around 24h for 16GB of RAM - possibly even longer. The test must run for at least 8 passes to be sure you have thoroughly tested the RAM.

 

New BSOD new minidumps.

DESKTOP-1FK4B9B-Tue_11_28_2017_205716_77.zip

 

For Memtest86+ version 5.01 it will display 1 core while testing and this normal.
Testing takes approximately 1 - 2 hours /GB RAM
The computer has 16 GB RAM.
There are 2 DIMM in use with 8 GB RAM in each DIMM.
Testing will take approximately 24 hours to test 16 GB RAM.
The testing needs to be made as 1 continuous test.
The testing is not done by time but by passes.
The greater the number the better the test.

All of the BSOD mini dumps when debugged displayed bugcheck C2
Bug Check 0xC2: BAD_POOL_CALLER
The BAD_POOL_CALLER bug check has a value of 0x000000C2.
This indicates that
the current thread is making a bad pool request.

For the workup of this bugcheck, RAM testing and Windows driver verifier, are suggested tools to find the cause.
Read the links below but do not turn on windows driver verifier.
We will let you know if and when to use the tool.

Download and install Everything: voidtools
It will index files on all drives.
The software can be set to start on boot or start when you need it.
In comparison to file explorer search as you type a character into search there will be instantaneous results.
The more the characters the narrower the search results.

Windows generates hidden files and folders when there are failed upgrades.
By default the Panther files may be hidden.
Everything search should be able to display them if they are available.
Search for these folders and files and for any of the files found use one drive or drop box to post share links into the thread.

C:\$windows.~BT\sources\panther
C:\windows\panther
setuperr.log
setupact.log
setupmem.dmp
setupapi/dev/log
bluebox.log
$windows.~bt\sources\rollback*.evtx
C:\$windows.~bt\sources\rollback

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

 

Saw a lot of setuperr/setupact files.

No setupmem.dmp, though.

Hope I got the right files.

Desktop(2)

 

One of the files was blank.
Please re-post the setuperr log

0x800704C7
0x80070005

 

I will post the one from system32 folder, since the one from the Panther folders are already uploaded in the windows/panther folders.





setuperr.log

 

The setuperr logs are very different in size. The 12 KB file size on 11/9 is probably the one that needs review. That file is now 20 days old.

1) Tomorrow 11/30/2017 see if you can perform an in place upgrade repair to generate fresh log files.
2) Make a brand new restore point tomorrow 11/30.
3) Uninstall any non-Microsoft AV product and only use Windows defender.
4) Disconnect any attached unnecessary hardware (printer, headset, xbox, etc.)
5) Download and install a Windows 10 iso: Download Windows 10
6) If there is a mechanical method to turn off wireless use a keyboard key.
7) Disconnect Ethernet.
8) Insert the Windows 10 iso flash drive into any USB port
9) Power on the computer and open file explorer
10) Identify the Windows 10 iso flash drive within file explorer
11) click on setup or setup.exe and launch it
12) In case there are unique issues with Insider Preview where internet access is needed you can connect Ethernet but indicate that in the thread
12) Run through the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
If the upgrade works the troubleshooting will be completed.
If the upgrade fails please post into the thread any new Panther logs generated on 11/30 /2017

 

Been out of town but now I'm back. Managed to follow your steps. still got BSOD.

Attaching logs right now.

Found no setupmem.dmp anywhere. As well as no C:\$windows.~bt\sources\rollback. setupapi/dev/log was instead setupapi.dev.log and the setuperr log file from /windows had 0kb.

bsod

 

When upgrades fail they typically create Panther logs.
The Panther logs have the Windows reporting for the failure.
Using everything search: voidtools
look for files that have these in the name:

C:\$windows.~BT\sources\panther
C:\windows\panther
setuperr.log
setupact.log
rollback
bluebox
setupmem.dmp
setupapi

Whichever files you find then can be posted into the thread for troubleshooting.


The bsod have implicated the memory.
Please post results (camera or smart phone camera) into the thread for the Memtest86+ version 5.01 testing for 8 or more passes:
Memtest86+ - Advanced Memory Diagnostic Tool
Memtest86+ - Advanced Memory Diagnostic Tool
See post #8

 

I already posted the logs with everything search in my last post. Will do a memory test soon.

 

See post #23.
In the left lower corner search type: winver
In the pop up view the windows version and build and see if this is the latest.
Did you attempt a new upgrade?
The failure to upgrade can be a windows update failure or a windows upgrade failure.
For failure of windows updates you can open administrative powershell and type or copy and paste: Get-WindowsUpdateLog
This may take 5 - 10 minutes to complete. Then post the log file into the thread using one drive or drop box.

If there is no problem with windows updates and only problems with failure to upgrade then:
If you were able to upgrade to the latest Windows version and build then there is no troubleshooting needed as it was successful.
If you were not able to upgrade there should be new Panther logs.
Searching for new panther logs after the latest failed upgrade then can be troubleshooted.


For Memtest86+ version 5.01 the quality of the test is important.
The quality of the test is based on the number of passes.
The more the passes the better the test.
Testing with fewer than 8 passes has a significant number of false negatives.
A false negative is a test pass when there is malfunctioning RAM.

So the more the passes the better the test.
Sometimes it may take passes in the 20s to find malfunctioning RAM.

After the testing has completed 8 or more passes use a camera or smart phone camera to take a picture and post the results into the thread.

 

I will be running memtest86+ next weekend, so I won't have to use my laptop for anything.

I didn't upgrade to the new build. I got BSOD during the installation from USB, no internet or other hardware connected.

Here is the log from powershell

Link to panther logs -> bsod