BSOD Registry Error

wptski · 03 Mar 2015

Dual boot, W7 is the default OS. Start up boots into W10TP instead of BIOS selection screen without asking for password. Chrome won't open, reboot, asks for password this time and get Chrome back, somehow! Posting in a forum, BSOD for registry error.

This is the first BSOD in a long time.

Download BSOD logger app to desktop, run but zip is empty! Try twice, same thing. Reboot, download again, run, zip is empty again but shows "SFdebugfile" on desktop. Double-click, windows can't open, right click on the folder to check location and it BSOD for registry again.

I did clear the %TEMP% folder, may try again. Here's what get, unsure if it's empty or not now: Attachment 13631

Yep, empty again!

usasma · 04 Mar 2015

Please provide these 3 things:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): http://www.carrona.org/setmini.html
More info on dump file options here: http://support.microsoft.com/kb/254649

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

wptski · 04 Mar 2015

Too late! It seemed to settle down so I went create an image. Somewhere between 90% and 100% done it crashed again. I wasn't sure if it completed so I was doing an integrity check of the image and shorty after starting, it crashed again.

From an recovery drive, I tried to use a system restore point and that errored out so I restored from an eight day old image. I deleted that old image as I don't trust it really although its integrity checked good from WinPE. Created a new image, build it back up with no BSODs during that time so I'm good till the next time.

Is that common for that logger app to not work on some systems?

usasma · 04 Mar 2015

The logger app has been changed several times since it was originally started by Captain Jack over at Vistax64 forums (I think).
There hasn't been a great deal of testing with the logger app on Win10 systems, so it's hard to tell if the problem was Windows or the app.

But, AFAIK, the app really isn't involved in kernel mode functions - so it shouldn't be responsible for BSOD's.
I saw the source code for the original app, but haven't been privy to the source for the latest versions.

wptski · 04 Mar 2015

Using MyBluescreenViewer on the BSODs it showed registry but caused by the NT Kernel & System. My last BSOD was back on 2/25/15 but was NFTS caused and all others I've had in the past were all NFTS caused.

NTFS caused BSODs triggers CHKDSK on all system drives but these just caused the W10TP drive to be checked for errors. I've manually checked the disk prior to booting and it's clean before at least.

I did use Testdisk from CgSecurity which "might" have caused my problems but who knows! I won't be running that from W10TP anyways.

usasma · 04 Mar 2015

NT Kernel & System is ntoskrnl.exe - the kernel (core) of the OS
NTFS is the file system on the disk - so chkdsk is one of the tools to be used, but there are other possible problems.

Testdisk is a possibility here. Their page doesn't show Win8 (nor Win10) as being compatible.
This is a possible cause, but it's uncertain at this point.
It all depends on what it did to the file system - and how Win10 reacted to it.

wptski · 04 Mar 2015

Others using Testdisk ran into the same usage problem as I did, recovered a file, it copied it but it can't be found! One reply outlined how set a destination path but suggested that it "probably" copied to one's main drive and that could be an issue with W10TP but it wasn't on W7. Like you stated, it not listed for W8/8.1 so I was taking a chance using it.

Arc · 10 Mar 2015

wptski said:

Download BSOD logger app to desktop, run but zip is empty! Try twice, same thing.

Right click on it and run as administrator. it should work.

Attachment 14071

If it is a stop 0x51 (as it appears from your original post), then you should test your HDD and scan the system for virus using a bootable tool. Seatools for DOS will be a good option for testing the HDD and Windows Defender Offline is a good bootable scanner. .

wptski · 11 Mar 2015

The app doesn't stop. It gathers, it copies, it creates and it finishes but creates an empty zip folder. It's a WD drive and its diagnostics app finds no problems. I've had no issues since I restored either.

The app did work on W7.

Arc · 11 Mar 2015

Sort of strange because it works just fine for me, and I also use 10TP.

Attachment 14164

Anyway, its good to know that you havent had this issue lately. You may consider the issue as solved if you think that it is really over.