Boot Manager Error (Not sure if this is technically a BSOD)

[voiplo]

Work through these Troubleshooting Steps for Windows 7 to check it out, gather clues and learn more about your PC and the way to troubleshoot it.

Newest problem after running HD Diagnostic and MEMTEST. Has happened twice while idling for 10 hours.
Start menu becomes empty, programs will not open, skype gives me an I/O error. That I/O error code is the same one as my Boot Manager error on the first page.

 

[gregrocker]

What were the results of the HD Diagnostics extended CD scan and Disk Check? Sounds like a HD problem.

 

[voiplo]

What were the results of the HD Diagnostics extended CD scan and Disk Check? Sounds like a HD problem.

HD Diagnostics Long Test said PASSED. I will do a Disk Check too.

 

[gregrocker]

Test the RAM - Test with Memtest86+ for 5-6 passes or overnight to stress test it.

 

[Arc]

Hello Borna.

Uninstall Super AntiSpyware. A storport.sys error may either cause by a faulty disc (I guessed you have checked the SSD for error, and it is passed, as you reported); or by any disc emulator (no SPTD.sys is present there, so we can ignore this part too) or by virus/rootkit (you scanned earlier and came clean) or by a AV program which uses a filter manager, and affecting the system's filter manager adversely. During Scanning with Super, the BSOD with storport.sys indicates that it is the program that is causing the issue. Anyway, a spyware is not very easily available. So you may easily remove it.

After removing it, scan the system for possible virus infection, again.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

BTW, have you taken ownership of your files? And, are you sure that you have installed the latest realtek network drivers?


If possible, free up some space in the SSD, too.

 

[voiplo]

Hello Borna.

Uninstall Super AntiSpyware. A storport.sys error may either cause by a faulty disc (I guessed you have checked the SSD for error, and it is passed, as you reported); or my any disc emulator (no SPTD.sys is present there, so we can ignore this part too) or by virus/rootkit (you scanned earlier and came clean) or by a AV program which uses a filter manager, and affecting the system's filter manager adversely. During Scanning with Super, the BSOD with storport.sys indicates that it is the program that is causing the issue. Anyway, a spyware is not very easily available. So you may easily remove it.

After removing it, scan the system for possible virus infection, again.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

BTW, have you taken ownership of your files? And, are you sure that you have installed the latest realtek network drivers?


If possible, free up some space in the SSD, too.

How do you take ownership of your files?
Yes, my realtek netwrok driver is completely up to date, I made sure of it through the realtek website.
I have removed it and I'm going to do what you suggested now.
Would this also be the problem for my I/O error that I've been getting since I got this computer though?

 

[Arc]

Do the memtest that Greg suggested.

Whendone, if RAM shows any error, RMA those. If it come clean, configure minidump, so that we may get some detailed info about the I/O violation.

First configure minidump. Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Then enable Driver Verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

During DV enabled, use the system normally as usual. Specially the crash prone actions. Say scan with MBAM. Let us know the results, with the subsequent crash dumps, if any.

Can you access the start menu All Programs list, and can open programs?

 

[voiplo]

Do the memtest that Greg suggested.

Whendone, if RAM shows any error, RMA those. If it come clean, configure minidump, so that we may get some detailed info about the I/O violation.

First configure minidump. Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Then enable Driver Verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

During DV enabled, use the system normally as usual. Specially the crash prone actions. Say scan with MBAM. Let us know the results, with the subsequent crash dumps, if any.

Can you access the start menu All Programs list, and can open programs?

memtests passed, DV enabled, Avast + MBAM scanned and cleaned, approaching 3 hours with no BSOD yet. I opened up DV and clicked on Existing Settings to make sure it is enabled, and it is. Programs are opening, Start Menu is working fine. I will let you know when it does crash. It's lasted a surprisingly long time with DV active, I usually get BSOD instantly.

 

[Arc]

OK.... disable DV now. and, use the computer normally.

Reoprt us the situation, either after a reasonable time that you think reasonable, or when you face the next issue, which one is earlier.

 

[voiplo]

First BSOD in 4 days. No dump file created for it. Error was KERNAL_DATA_INPAGE_ERROR. Stop code 0x0000007A.

 

[Arc]

First BSOD in 4 days. No dump file created for it. Error was KERNAL_DATA_INPAGE_ERROR. Stop code 0x0000007A.

Crash dumps are really needed to have a closer look

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[voiplo]

First BSOD in 4 days. No dump file created for it. Error was KERNAL_DATA_INPAGE_ERROR. Stop code 0x0000007A.

Crash dumps are really needed to have a closer look

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

I've already done Option Two, Point 2 almost a week ago. My BSOD settings are set up, I've run the .reg file and I know how to get to the Minidump folder.

The Minidump folder doesn't exist. When I get a BSOD, it hangs at Initializing data for crash dump... and it never creates the crash dump.

 

[voiplo]

Giving this thread one last bump since I just wanted some closure. After the final report above, I received multiple BSODs, all being In Page Kernal Errors.

I formatted and installed Windows 8 and haven't had a crash, restart, or anything harmful in over a month. Was it an OS issue? What was the problem here?

 

[Arc]

Oops, sorry mate, I missed it somehow

If it is working good with 8, and if you like 8 use it

 

[gregrocker]

Was likely the install rather than the OS.

Compare your install methods and tools to these same steps compiled based on tens of thousands of reinstalls we've helped with here: Clean Reinstall - Factory OEM Windows 7.

For example you'll notice that drivers are completely automated in Win8, using advancements developed in Win7. Users get in trouble when they use the XPired method of importing a bunch of drivers to overwrite the ones Win7 installer and Updates provides.