[SOLVED] SFCFix crashing - Win10

fireweed · Oct 14, 2021

Hello, I'm trying to sort out some weirdness on my computer, but I am running into issues getting SFCFix to run. It was a decent way through the first time when it crashed. Now all the other times I run the program it crashes well reading cbs.log.

I've made sure my windows is updated, and I've ran SFC a few times and dism once after the first crash. Some system corruption was repaired, though SFCFix is still crashing. I've restarted my computer a few times, too.

CBS attached, and here is the link to the CrashDumps file.

Thanks for your help!

philc43 · Oct 15, 2021

Hello fireweed,

The crashes all seem to be caused by msvcp80.dll which is a component of MS Visual Studio 2005. Please try temporarily uninstalling Visual Studio and see if it makes a difference.

fireweed · Oct 15, 2021

Thank you for the advice! The machine is my surface from work and though I do work at an IT company and have permission to work on my machine to try and repair it, I need to check with our internal IT team to make sure I can uninstall it without messing with any of the programs they install on it. I will hopefully get permission from them and let you know how the uninstall and rescan goes.

philc43 · Oct 16, 2021

Hello fireweed,

OK. I realise my previous post was very brief and I did not have much time to write up the analysis. I now realise you would probably appreciate more details so here goes.

I analysed the crash dumps you provided using WinDBG Preview (available from the Microsoft Store) and they were very similar. The main finding is the exception that was raised and which caused the crash.

At the time of the crash the stack showed the following was being executed - read from the bottom up to get the sequence of events.

Code:

STACK_TEXT:
006fd31c 6f7d8e89     e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x62
006fd354 6f74b3e7     006fd374 6f758fb4 2c69538f msvcr80!_CxxThrowException+0x46
006fd3c4 6f7300c1     6f7b8a94 006fd904 00000100 msvcp80!std::_String_base::_Xran+0x3e
006fd3d8 6f731c9e     006fd940 ffffffff ffffffff msvcp80!std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >::assign+0x18
006fd3ec 6f731df2     006fd940 ffffffff ffffffff msvcp80!std::basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >::basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >+0x24
006fd404 00c6dae2     006fd904 ffffffff ffffffff msvcp80!std::basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >::substr+0x17
WARNING: Stack unwind information not available. Following frames may be wrong.
006fd9c4 00c454c9     6f72e0a4 0142b6f8 6f7f975b SFCFix+0x2dae2
006fdf50 00c7a889     00000000 01428d00 01428d1c SFCFix+0x54c9
006fe0c4 00c7ae27     006fe58c 006fe674 006fe618 SFCFix+0x3a889
006fe6a0 00ca55d0     00d092a0 00000001 00000000 SFCFix+0x3ae27
006ff97c 00c4133e     00000001 01421640 014204f8 SFCFix+0x655d0
006ff9c0 76d0fa29     0054e000 76d0fa10 006ffa2c SFCFix+0x133e
006ff9d0 77027a9e     0054e000 de89666b 00000000 kernel32!BaseThreadInitThunk+0x19
006ffa2c 77027a6e     ffffffff 77048a4d 00000000 ntdll!__RtlUserThreadStart+0x2f
006ffa3c 00000000     00c41483 0054e000 00000000 ntdll!_RtlUserThreadStart+0x1b

The key line from the rest of the analysis that identifies the failure is this:
FAILURE_BUCKET_ID: CPP_EXCEPTION_e06d7363_msvcp80.dll!std::_String_base::_Xran

Other information provided is here:
FAULTING_SOURCE_LINE: f:\dd\vctools\crt_bld\self_x86\crt\src\string.cpp
FAULTING_SOURCE_FILE: f:\dd\vctools\crt_bld\self_x86\crt\src\string.cpp
FAULTING_SOURCE_LINE_NUMBER: 18
FAULTING_SOURCE_CODE:
No source found for 'f:\dd\vctools\crt_bld\self_x86\crt\src\string.cpp'

To be honest I'm not entirely sure if this is a problem with SFCFix (which is a Sysnative tool) or to do with Visual Studio. I would need one of the developers to check this.

fireweed · Oct 16, 2021

Thank you for the more in-depth reply, Phil. I wasn't sure the best program to download for viewing dumps so I'll definitely check it out.

I'd love to have spent a few hours on this at work but with the current focus on "billable" and "utilization" hours I don't really want to spend my whole work day on it. And of course I forgot my charger at work so I wanted to try and find a solution a bit faster. Researching some internal programs I cant see why any of them would need VS05 but hopefully I get the OK to remove it soon.

If you do check with the devs I'd be very curious to know the cause of the issue!

fireweed · Oct 20, 2021

Hey Phil,

I have an update for you. I got the all good to try and get any VS2005 things off my machine but there were none in programs. I decided to see if I could temporarily remove the specific dlls and get the scan working but after fighting with trustedinstaller I got a prompt that our monitoring agent for remote access was using the dll, so I guess that explains that! I'll have to check on another work PC but if my hunch is right then SFCFix isnt compatible with the current version of the NCentral Windows Agent, which would kinda suck because I like the tool and would like to be able to use it on client machines if I need.

I'll check when I'm back in on Thursday.

philc43 · Oct 20, 2021

I suspect you are right. You are possibly the first one to discover this anomaly. I'll make sure the developers see it. I'm sorry that it doesn't work but maybe we can still help by manually performing some of the fixes.

fireweed · Oct 20, 2021

I think that I may be alright for now? SFC is finally coming up clean after various scans and some dumb luck, I think. My webcam is working again and updates are completing. The computer even seems to be running better now, or as well as it can run as a dinky surface with 8GB RAM that I use at ~90% CPU and RAM usage all day.

I'll continue keeping an eye on it, unless you have any other recommendations for getting it working the best?

philc43 · Oct 20, 2021

That does sound promising. If you are now up to date and the scans show no problems I think you are ok. Just keep an eye on it.

fireweed · Oct 20, 2021

Will do, thank you for your help with this!

Search

Search

[SOLVED] SFCFix crashing - Win10

fireweed

Active member

Attachments

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

fireweed

Active member

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

fireweed

Active member

fireweed

Active member

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

fireweed

Active member

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

fireweed

Active member