BSODs & SFCFix needs personal pampering from preferably you...

G

gyurika

Active member
Joined
Aug 7, 2015
Posts
36
Location
New York
Hi,
Woww, wish I had found the program sooner (on my desktop from all places)
I have spent about 2 months trying to resolve my crash waking up from Hibernation. (Sometimes sleep too.) (My best guess is that something prevented the computer to shut down completely.) Always got 2 culprit file in minidump: aiStoreB.sys or ntoskrnl.exe and different strings either the IRQL or the KMODE not handled... correspondingly to the two causative drivers.
So eventually I ran Driververifier. It BSOD immediately. Could not get back to windows except by some clever workaround got in to safe mode where I am. :banghead:
One BSOD culprit since Verifier I managed to uninstall, (Bad_pool_Caller) - the one that remained is a SYSTEM_SERVICE_EXCEPTION. Just stops the boot midway.

So that is when I found SFCfix, ran it, and will be enclosing the txt report. In the past sfc /scannow would always report that it could find corruptions but could not fix them.

All my drivers, BIOS and the paint on the chassis (kiddin) are as new as I could get it, - you can imagine during 2 months... I am now mentally finished...:confused2:

Hope my upload was good, and I will go to eat because I do not know what will happen now.
Thank you. I do not know if you need anything, my email is xxxxx and phone is xxxxx
 

Attachments

Last edited by a moderator:
Re: SFCFix needs personal pampering from preferably you...

This the error in the txt file:
AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json
 
Re: SFCFix needs personal pampering from preferably you...

Hi gyurika. :smile9:
Did you already check if you have installed all the windows updates (control panel, windows updates)?
Did you already tried the DISM tool (from an elevated command prompt)?
Code: 
DISM /Online /Cleanup-image /Restorehealth
 
Re: SFCFix needs personal pampering from preferably you...

Hi,
Thank you.... I am not too much back with updates - but my understanding is that in safe mode the Windows Update option is not shown anywhere.
The other tool I have not heard of will go figure now and thank you again.
 
Are you still in safe mode?
Open an elevated command prompt (right-click on windows start, click command prompt(admin)) and run the following command:
Code: 
verifier /querysettings|find /i "verifier flags"
If the result is different from Verifier Flags: 0x00000000, i.e. if it is different than zero, and I think it should be another number because I think you didn't reset verifier settings, try to reset verifier using this command:
Code: 
verifier /reset
Re-try the first command to check if the result is now Verifier Flags: 0x00000000:
Code: 
verifier /querysettings|find /i "verifier flags"
Then you can try to restart/reboot your PC in normal mode.

Hope this helps to exit from the safe mode... Safely!
 
Hi,
I am little bit sensitive to that, because my whole problem is a result of running verifier in the first place... Basically ever since I ran it, Windows tries to fix my boot, it cannot and it is crashing into the System_Service_Exception error with a 3b. I came to the conclusion that was video, so I nuked Nvidia. That did not do it. Stoppe Intel RST. Disabled 2 more services that came up in perfmon one was Workstation, - ???? Anyway I get a warning that I did not connect to some network. but in the mean time that did not solve it either. So now let me send up a SysnativeFileCollectionApp zip file and then try your suggestion, will need a shot before I do that... And every time I have ntoskrnl.exe as the address
 
Hi,
So it was a little less traumatic: nothing has happened! I entered the code (with "...") at the end, and I simply got the prompt back. ??? Very appreciatively anyway...
 
You are a Genious. (I am a vice genious.)
As I have written to you the "code" did not do anything, did not return a number. So I was sitting bummed.
And then I thought, the fact that verifier maybe ****ed up (excuse) and not returning a number, I could still try to reset it, - as a matter of fact even more so. So I did, and because last time I forgot to set Msconfig back to safe mode, suddenly my desktop lit up. The moral of this, that after verify BSOD my system, I could not even get into safe mode, like people so nonchalantly advice "dontchu worry go into safe mode and delete the offending file" First you cannot get in there, second is which file did you say??? So anyway I eventually found a very convoluted way to get into safe mode, and then I tried to stop disable send verify generally into hell, and it reported "no" to every function, but still I could not boot. I do not know what transpired inside my computer, but clearly some remnant of Verifier was sabotaging my life. Now I will start putting back the RAM sticks I already installed Nvidia, but then I realized I have to thank you before you come up with some more tricks... Amazingly surprising outcome, - better get used to it I could tell myself with computers-Windows rather...
Thank you again a lot, George
 
Hi,
I am still waking up (from hibernation) to the same BSOD. The culprit (with one exception yesterday) is still aiStoreB.sys or ntoskrnl.exe. The error in the sFCfix log is also the same:

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json

I was quiet here, because in the mean time I have changed all the memory and the mouse and squared with Webroot - to eliminate these possibilities.
Please let me know what other info is needed, and obviously my life is not complete until somebody could help me get rid of these.
Oh by the way RTS is disabled I tried to uninstall but is did not, and the IDE ATA/ATAPI controllers never re-appeared in device manager as it should have according to the article. (And then of course I could not boot for half a day.) So I am still having the aiStoreB.sys the participate in the crashes. I will attach the crash log.
 
The corruption is a false positive, it is caused by a Windows Update package which belongs to the upgrade for Windows 10.
 
gyurika said:
Hi,
I am still waking up (from hibernation) to the same BSOD. The culprit (with one exception yesterday) is still aiStoreB.sys or ntoskrnl.exe. The error in the sFCfix log is also the same:

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json

I was quiet here, because in the mean time I have changed all the memory and the mouse and squared with Webroot - to eliminate these possibilities.
Please let me know what other info is needed, and obviously my life is not complete until somebody could help me get rid of these.
Oh by the way RTS is disabled I tried to uninstall but is did not, and the IDE ATA/ATAPI controllers never re-appeared in device manager as it should have according to the article. (And then of course I could not boot for half a day.) So I am still having the aiStoreB.sys the participate in the crashes. I will attach the crash log.
Click to expand...

Hello,

You'd be best off to re-run the Sysnative File Collection App at this point so we have up-to-date info to work with. I am curious as to what you mean by: "squared with Webroot" though, as that seems to be the cause of pretty much all of the dump files in December. As an aside, I'm not able to find any information on "aiStoreB.sys".
 
Xer said:
gyurika said:
Hi,
I am still waking up (from hibernation) to the same BSOD. The culprit (with one exception yesterday) is still aiStoreB.sys or ntoskrnl.exe. The error in the sFCfix log is also the same:

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json

I was quiet here, because in the mean time I have changed all the memory and the mouse and squared with Webroot - to eliminate these possibilities.
Please let me know what other info is needed, and obviously my life is not complete until somebody could help me get rid of these.
Oh by the way RTS is disabled I tried to uninstall but is did not, and the IDE ATA/ATAPI controllers never re-appeared in device manager as it should have according to the article. (And then of course I could not boot for half a day.) So I am still having the aiStoreB.sys the participate in the crashes. I will attach the crash log.
Click to expand...

Hello,

You'd be best off to re-run the Sysnative File Collection App at this point so we have up-to-date info to work with. I am curious as to what you mean by: "squared with Webroot" though, as that seems to be the cause of pretty much all of the dump files in December. As an aside, I'm not able to find any information on "aiStoreB.sys".
Click to expand...

Hi, thanks, - I posted the answer as a new thread as per the suggestion there. Looking forward with qualified hope... - really...
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top