Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows Update - BSOD

20 Feb 2017   #1
ITuser07

Windows 7 - 64 bit
 
 
Windows Update - BSOD

A windows update seems to have hosed to of my laptops, same make/model. Dell Latitude E7470. I just installed windows and was doing updates, I rebooted for what I believe was the last batch up updates and now both are blue screening with 0x6F.

---
Actual Error:
Session3_Initialization_Failed

Technical Information

***Stop: 0X6F (0XFFFFFFFFC000012F)
---

Things i've tried:
  • Startup repair
  • System Restore
  • Copying the regback files back to the config folder
  • check disk
  • SFC /scannow /offbootdir=c:\ /offwindir=c:\windows
  • MacriumReflects BootFix
  • EasyRe Automated Repair
  • LastKnownGood Config
  • Safemode
Nothing seems to make them boot back up. Any ideas?


My System SpecsSystem Spec
.
20 Feb 2017   #2
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Hello and welcome ITuser now that error code is not a common one and to have two machine similarly affected either just bad luck or that something has been changed in those machines before the install ?? new hard drives or RAM??

Were the machines running Windows 7 before? and just what media are you using to install 7 on those machines? Now that media could be an OEM for each one or a retail copy but there again it can only be used on one machine at a time so you would need two retail copies or two OEM copies.
My System SpecsSystem Spec
21 Feb 2017   #3
ITuser07

Windows 7 - 64 bit
 
 

Quote:
Hello and welcome ITuser now that error code is not a common one and to have two machine similarly affected either just bad luck or that something has been changed in those machines before the install ?? new hard drives or RAM??

Were the machines running Windows 7 before? and just what media are you using to install 7 on those machines? Now that media could be an OEM for each one or a retail copy but there again it can only be used on one machine at a time so you would need two retail copies or two OEM copies.
Hi There, happy to be apart of this community. Thank you for responding to my question and being willing to assist with this.

This was 2 brand new laptops that were unboxed freshly imaged using a FOG imaging server, the image is good, we've used it on several other computers and it was working fine until the last batch of windows updates was installed. I came in yesterday morning and saw the one laptop that was just sitting on the lock screen on Friday had been automatically rebooted and now just bluescreens. I tried everything I could think of to fix it to no resolution. Then I booted the other laptop back up, I thought I was finished with it on Friday so I had shut it down. Upon turning it on I logged in and everything was fine, I seen I had about 35 more updates to run so I ran them and upon rebooting BAM..bluescreen(Exact same issue as the other laptop)
My System SpecsSystem Spec
.

21 Feb 2017   #4
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

Hi Ituser07,
Bit hard to diagnose without any logs.
But i dont think its a driver the comp hasn't got that far before it falls over
So a few Questions

is it actually a Blue or Black SOD

How old is that syspep image??
im wondering if it had the W10 installer on it, KB3033583, tried to install and failed.

Can you get into Bios and reset it to default (F2), or. Factory reset (F8)
How to restore your Windows 7 computer to factory settings | Dell US

I did find this MS artical relating to that code, and a fix
(allthough it states XP its still relevant to W7.


If you mean you are getting a STOP error that says something like:

SESSION3_INITIALIZATION_FAILED

*** STOP: 0x0000006F (0xc0000034, 00000000, 00000000, 00000000)

It's not RAM, it has nothing to do with chkdsk.

There is no Windows Boot Manager, no Tools, no Memory Diagnostics option in XP...

So far, these Support Engineer suggestions sound like just bad guesses.

One would have to actually see it and learn how to fix the various SESSSION messages.

The usual culprit is some antivirus software - perhaps Avast!, AVG or Avira that has
deleted or quarantined necessary XP files such as the Windows Session Manager file:

c:\windows\system32\smss.exe

You may be able to boot in Safe Mode somebody said and replace the missing file from there.

I suppose the file could have been really infected and quarantined, but that has never been my experience.

What antivirus software are you running and did you just use it prior to this incident?

If the files have been quarantined or deleted, you can just replace them from the copies that are already on your HDD, but to do so you must boot your system into the Windows XP Recovery Console.

Boot into the Windows Recovery Console using a bootable XP installation CD, or create on a
bootable XP Recovery Console CD.

This is not the same as any recovery disks that might have come a store bought system. If
you are not sure what kind of bootable CD you have, make a bootable XP Recovery Console CD and be sure.

There are at least four possibilities (that I know of) for these missing files that result in the
SESSION3 or SESSION5 type message:

Windows\System32\smss.exe <-------- most likely, so replace this one first
Windows\System32\ntdll.dll
Windows\System32\ntoskrnl.exe
Windows\System32\drivers\ftdisk.sys
Windows\System32\winlogon.exe

After booting into the XP Recovery Console, you should be in the C:\WINDOWS folder. If you are not in the C:\WINDOWS folder you have some other problem that you need to fix first.

When copying files, you may be replacing existing files with the copies, so respond in the affirmative if asked to overwrite existing files. If the copy succeeds, you should see a message that the file was copied successfully.

In the Recovery Console, from the C:\WINDOWS prompt, enter the following commands:

cd system32
copy c:\windows\system32\dllcache\smss.exe
Reply in the affirmative to any "are you sure" messages so 1 file(s) is copied
exit (your system will restart)

Depending on your system configuration, you may need to copy the files from another location, so if they are not in the dllcache folder for some reason, enter the commands like this:

cd system32
copy c:\windows\ServicePackFiles\i386\smss.exe
exit (your system will restart)

Roy
My System SpecsSystem Spec
21 Feb 2017   #5
ITuser07

Windows 7 - 64 bit
 
 

Quote   Quote: Originally Posted by torchwood View Post
Hi Ituser07,
Bit hard to diagnose without any logs.
But i dont think its a driver the comp hasn't got that far before it falls over
So a few Questions

is it actually a Blue or Black SOD

How old is that syspep image??
im wondering if it had the W10 installer on it, KB3033583, tried to install and failed.

Can you get into Bios and reset it to default (F2), or. Factory reset (F8)
How to restore your Windows 7 computer to factory settings | Dell US

I did find this MS artical relating to that code, and a fix
(allthough it states XP its still relevant to W7.


If you mean you are getting a STOP error that says something like:

SESSION3_INITIALIZATION_FAILED

*** STOP: 0x0000006F (0xc0000034, 00000000, 00000000, 00000000)

It's not RAM, it has nothing to do with chkdsk.

There is no Windows Boot Manager, no Tools, no Memory Diagnostics option in XP...

So far, these Support Engineer suggestions sound like just bad guesses.

One would have to actually see it and learn how to fix the various SESSSION messages.

The usual culprit is some antivirus software - perhaps Avast!, AVG or Avira that has
deleted or quarantined necessary XP files such as the Windows Session Manager file:

c:\windows\system32\smss.exe

You may be able to boot in Safe Mode somebody said and replace the missing file from there.

I suppose the file could have been really infected and quarantined, but that has never been my experience.

What antivirus software are you running and did you just use it prior to this incident?

If the files have been quarantined or deleted, you can just replace them from the copies that are already on your HDD, but to do so you must boot your system into the Windows XP Recovery Console.

Boot into the Windows Recovery Console using a bootable XP installation CD, or create on a
bootable XP Recovery Console CD.

This is not the same as any recovery disks that might have come a store bought system. If
you are not sure what kind of bootable CD you have, make a bootable XP Recovery Console CD and be sure.

There are at least four possibilities (that I know of) for these missing files that result in the
SESSION3 or SESSION5 type message:

Windows\System32\smss.exe <-------- most likely, so replace this one first
Windows\System32\ntdll.dll
Windows\System32\ntoskrnl.exe
Windows\System32\drivers\ftdisk.sys
Windows\System32\winlogon.exe

After booting into the XP Recovery Console, you should be in the C:\WINDOWS folder. If you are not in the C:\WINDOWS folder you have some other problem that you need to fix first.

When copying files, you may be replacing existing files with the copies, so respond in the affirmative if asked to overwrite existing files. If the copy succeeds, you should see a message that the file was copied successfully.

In the Recovery Console, from the C:\WINDOWS prompt, enter the following commands:

cd system32
copy c:\windows\system32\dllcache\smss.exe
Reply in the affirmative to any "are you sure" messages so 1 file(s) is copied
exit (your system will restart)

Depending on your system configuration, you may need to copy the files from another location, so if they are not in the dllcache folder for some reason, enter the commands like this:

cd system32
copy c:\windows\ServicePackFiles\i386\smss.exe
exit (your system will restart)

Roy
Thanks for responding Roy, I seen that HBK as well and even though i'm working with Windows 7, I attempted to copy a known good smss.exe to this machine and still got the same results unfortunately. We are using Symantec Endpoint Encryption in our organization. This is an actual Blue Screen, not black unfortunately it's not even creating a minidump folder so it's not like a typical dump/crash.

Here is an image of the BSOD:

My System SpecsSystem Spec
21 Feb 2017   #6
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

Found another known culprit to try

C:WindowsSystem32Wldap32.dll

Roy
My System SpecsSystem Spec
21 Feb 2017   #7
ITuser07

Windows 7 - 64 bit
 
 

After much research, I think this may be related to Dell DDP Encryption. I'm currently working to decrypt the drive to see if that helps.
My System SpecsSystem Spec
Reply

 Windows Update - BSOD




Thread Tools




Similar help and support threads
Thread Forum
BSOD after last Windows update
I get the BSOD when windows comes up, even if I don't login. This happened last month after the last windows update. I can boot in Safe mode and able to copy the DUMP file to a USB drive (attached). I tried to download your DM Log Collector file but my Norton 360 blocks and deletes it saying it...
BSOD Help and Support
BSOD when trying to update Windows
Hey guys. I'm can't figure this one out. Every time I try to update Windows I get a BSOD. When I finally get the PC back up and running and try to finish updates they fail. I currently have 144 update that keep failing. I have included my most recent dump information. I've tried to wipe the...
BSOD Help and Support
BSOD on Windows Update; BSOD when playing games
NOTE: DM log collector seem to be getting stuck when collecting msinfo32.nfo, so the attached file can be incomplete. Please let me know if it can take longer than 10 minutes to collect this data so i will run the program again. BSOD #1: It started at around January 15th - basically when i shoot...
BSOD Help and Support
BSOD during Windows Update
I was just redownloading Windows 7 Home Premium to fix any possible errors and BSOD'd.
BSOD Help and Support
Windows Error and BSOD - Windows Update installed on wrong drive (?)
Hello, my computer has been dead for the last few days so to speak. For two days ago I turned on my computer - it started up just like any other day. I saw the Desktop and bang, blue screen of death. This has not happened since I installed Windows on my new SSD Harddisk (I'm running with two...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:49.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App