RicaNeaga Posted August 7, 2012 Share Posted August 7, 2012 Sorry for the delay, I'm more on the optimist side when it comes to aproximate time.Yes, I can confirm 100% that the Disable Mapped Drive Checking on Startup::Disable Checking tweak generates the BSOD.Sorry for not solving this earlier, but I used the old preset when testing, since the only addition to the new one was this tweak, and I couldn't believe it could be so problematic. Great however we finally know the answer. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted August 7, 2012 Share Posted August 7, 2012 Thank youAlready fixed, tested and it's now working Quote Link to comment Share on other sites More sharing options...
Mark Strelecki Posted August 7, 2012 Share Posted August 7, 2012 I can confirm I was using the Disable Mapped Drive Checking on Startup::Disable Checking tweak.Sounds like you discovered it and fixed it. Congratulations! I will resume building activities after 6PM EDT tonight.It will be great to be back in the saddle again.MARK STRELECKIAtlanta, GA. USA Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted August 7, 2012 Share Posted August 7, 2012 It confirmed working on was in release v53. I've also added code to prevent me from doing the same mistake again. Quote Link to comment Share on other sites More sharing options...
berkieboy Posted August 7, 2012 Author Share Posted August 7, 2012 Hello,I used v54 and the 0x67 config_initialization_failed BSOD was solved :dancing:Thank you Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.