Infinite reboot loop, safemode loads fine

[unknowniac]

Hi and thanks for taking the time to read this,

I'm currently experiencing a very frustrating issue that I've seen people post about before, however none of the answers provided have helped me so far. Specifically, what happens is that when I try to boot Windows normally it gets to the Windows logo animation, then my screen goes black and my system reboots.

If I switch to any of the safemodes I am able to load fine, [strike]but if I attempt the Windows system repair it will load to the initial repair screen menu but my mouse and keyboard aren't powered (tried switching them around to different USB ports, but don't have PS2 peripherals to try). [/strike] My mouse and keyboard now work on the system repair screens, though Windows couldn't find any problems to repair.

I've tried disabling all of my startup programs, uninstalling and reinstalling graphics and audio drivers, resetting BIOS, and even checked my RAM with Memtest86+ which showed a 100% pass after 8 passes.

I'm really out of ideas short of wiping my SSD and reinstalling Windows, but I'd rather avoid that as I no longer have my install disk. Below is the BSOD problem signature:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050033
BCP3: 00000000000506F8
BCP4: FFFFF80003918640
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Thank you for your help!

 

[unclebun]

The 7f code can be a driver issue, which being able to run in Safe Mode seems to point to. Have you run MSCONFIG to get to the diagnostic startup mode?

The other thing that can cause 7f codes is hardware failure. You've tested your memory, but it can also come from power supply or gpu failure.

 

[SirSub42]

A full dump would provide additional information if you'd be so kind.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. We need at least 2 DMP FILES to diagnose and confirm

The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on your site, MS doesnt have this)
*Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
Link for how to upload below.
http://www.wikihow.com/Use-SkyDrive

To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Please also run MSinfo32 and upload the output as well.
To run MSinfo32 please go to start>run>MSinfo32
Go to "file" "save" and upload the saved file with the DMPS
System specs are extremely useful so please include whatever you know.
Team Zigzag3143.com

 

[unknowniac]

The 7f code can be a driver issue, which being able to run in Safe Mode seems to point to. Have you run MSCONFIG to get to the diagnostic startup mode?

The other thing that can cause 7f codes is hardware failure. You've tested your memory, but it can also come from power supply or gpu failure.

I can run msconfig but I'm not sure how to utilize the diagnostic startup mode. What do I need to do after I select it?

 

[SirSub42]

I believe this should cover it.

https://www.tenforums.com/tutorials/2304-boot-into-safe-mode-windows-10-a.html

 

[unknowniac]

A full dump would provide additional information if you'd be so kind.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. We need at least 2 DMP FILES to diagnose and confirm

The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on your site, MS doesnt have this)
*Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
Link for how to upload below.
http://www.wikihow.com/Use-SkyDrive

To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Please also run MSinfo32 and upload the output as well.
To run MSinfo32 please go to start>run>MSinfo32
Go to "file" "save" and upload the saved file with the DMPS
System specs are extremely useful so please include whatever you know.
Team Zigzag3143.com

I included the 4 latest DMP files from today, but have lots more if more is useful.
https://1drv.ms/f/s!ArPFeinhZIEVhHg7AEu2kjr1Fqro

 

[SirSub42]

Try this:
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Seems to be a bad driver causing a memory corruption. Hopefully I read that right.

 

[unknowniac]

Try this:
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Seems to be a bad driver causing a memory corruption. Hopefully I read that right.

Here is the DMP after turning on the verifier
https://1drv.ms/u/s!ArPFeinhZIEVhHrk491FUEIU8g-R

 

[unknowniac]

From what I can gather from the minidump it's the ntoskrnl.exe file that's causing the issue. I updated ALL of my drivers using Snappy Driver Installer, but still no luck booting in normal Windows mode.

 

[jr9]

- An nVIDIA display driver is running in your dump files. Uninstall everything nVIDIA related in safe mode and shutdown. Connect your display cable to your motherboard's video or just leave it connected the GPU, it will still work with the GTX 980 but will will run in low resolution mode with no drivers installed. Do not install another driver and report if it crashes or you cant boot into normal Windows.

- Uninstall you Avast security suite or anything Avast in safe mode and see if you can load into Windows.

 

[jr9]

From what I can gather from the minidump it's the ntoskrnl.exe file that's causing the issue. I updated ALL of my drivers using Snappy Driver Installer, but still no luck booting in normal Windows mode.

Just to add some things:

- None of the dump files that are 256K in size will open in any of my debuggers. Only 2 of those crash dump I could open.

- I see ntoskrnl and ntkrnlmp using a more advanced debug tool. These are core Windows files. These two things give no valuable information. They were blamed for the crash but are not responsible.

- Automatic driver update programs can cause more programs then they solve. I don't recommend using them ever.

 

[unknowniac]

- An nVIDIA display driver is running in your dump files. Uninstall everything nVIDIA related in safe mode and shutdown. Connect your display cable to your motherboard's video or just leave it connected the GPU, it will still work with the GTX 980 but will will run in low resolution mode with no drivers installed. Do not install another driver and report if it crashes or you cant boot into normal Windows.

- Uninstall you Avast security suite or anything Avast in safe mode and see if you can load into Windows.

I uninstalled Avast and everything NVIDIA and deleted all associated files, and was able to successfully boot in normal mode. NVIDIA was giving me some real trouble about uninstalling things too, but after just hard-deleting all of the files it seems to work.

Thanks everyone for your help!

 

[jr9]

- Display Driver Uninstaller tool will find and remove every trace of any display drivers on your system. I use it personally and my shop uses it every time we do a graphics card upgrade. It is the nail polish remover of display drivers (which are the #1 cause of BSOD)

- Recommend installing Avast and rebooting to see if the issue returns. I suggested it because it had several drivers and all the newest ones on the system. It may not have been the culprit.