Windows 10: Multiple BSOD when adding password or profile pic to local account

The DM log collector file: Attachment 15253

Background:

A HP ProBook 4530S laptop. As my specs show another PC, here are the essential specs of this one:

Attachment 15254
Main account an MS Account, 10041 x64 EN-GB installed clean. To test language packs I created additional local accounts (all standard user) for US English, Finnish, Swedish and German. Started the process to personalize these accounts before installing the language packs, went first to local account English. Uploaded a profile pic, got BSOD when logging out to set a profile pic for the next new account.

Windows did not let me select the user when rebooted after the BSOD but instead signed in to this account English. Repeated the profile pic upload, again a BSOD. Again reboot to account English, thought I need to set password to that account in order to be able to select user if the BSOD reboots again. Setting up the password and signing out caused again a BSOD.

I suspect these crashes might have something to do with the fact that as I intend to use this laptop for sysprep testing, the last install / sysprep test yesterday involved removing all store app.

Any assistance and ideas appreciated.



:)

 

How to completely remove all traces of a Microsoft Account from a local User Account

I dont understand why logging in using microsoft account in a private computer for application like paint 3d should allow my microsoft account profile pic being set as local account profile pic... this is absurd.

 

Problems with Switching between profiles in Windows 10

I recently upgraded my children's computer to Windows 10. There are multiple profiles, 2 that are password protected and 1 that is not. When switching profiles (without logging off) from a profile that is password protected to any of the other two, switching
works like expected. However, when switching profiles from the account that does not have a password to either of the other two profiles, Windows 10 goes out to the user selection screen then immediately logs back into the same profile that is not password
protected. I can resolve this by adding a password to the third profile, but would prefer not to as this is for my youngest that is 5 and not quite able to write or exactly type yet. Is there a way to correct this. This was not an issue with windows 8.1.
Any suggestions would be appreciated. Thanks in advance.

 

I'm not an expert on these things at all but perhaps this will help until someone else can have a look...

The error in your dumps seems to be due to ATI Video driver (atikmpag.sys, Feb 28 2015) and suggestion is to remove Catalyst and install only the video driver. Driver Reference Table - atikmpag.sys

Code: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80318093fdc, Address of the instruction which caused the bugcheck Arg3: ffffd000a2933810, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. FAULTING_IP: nt!KeAcquireGuardedMutex+2c fffff803`18093fdc f00fba3700 lock btr dword ptr [rdi],0 CONTEXT: ffffd000a2933810 -- (.cxr 0xffffd000a2933810;r) rax=0000000000000001 rbx=ffffe0002e3073a0 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000030 rip=fffff80318093fdc rsp=ffffd000a2934230 rbp=ffffd000a29342b0 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=ffffe0002c81f660 r12=ffffe0002c6b3bc0 r13=ffffd000a2934590 r14=0000000000000002 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!KeAcquireGuardedMutex+0x2c: fffff803`18093fdc f00fba3700 lock btr dword ptr [rdi],0 ds:002b:00000000`00000030=???????? Last set context: rax=0000000000000001 rbx=ffffe0002e3073a0 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000030 rip=fffff80318093fdc rsp=ffffd000a2934230 rbp=ffffd000a29342b0 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=ffffe0002c81f660 r12=ffffe0002c6b3bc0 r13=ffffd000a2934590 r14=0000000000000002 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!KeAcquireGuardedMutex+0x2c: fffff803`18093fdc f00fba3700 lock btr dword ptr [rdi],0 ds:002b:00000000`00000030=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: atieclxx.exe CURRENT_IRQL: 1 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff800aed89699 to fffff80318093fdc STACK_TEXT: ffffd000`a2934230 fffff800`aed89699 : ffffe000`2ce75010 00000000`00000000 ffffe000`2a90cf40 00000000`00000801 : nt!KeAcquireGuardedMutex+0x2c ffffd000`a2934260 ffffe000`2ce75010 : 00000000`00000000 ffffe000`2a90cf40 00000000`00000801 00000000`00000002 : atikmpag+0x19699 ffffd000`a2934268 00000000`00000000 : ffffe000`2a90cf40 00000000`00000801 00000000`00000002 fffff800`aed947bd : 0xffffe000`2ce75010 FOLLOWUP_IP: atikmpag+19699 fffff800`aed89699 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: atikmpag+19699 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 54f15ba7 STACK_COMMAND: .cxr 0xffffd000a2933810 ; kb FAILURE_BUCKET_ID: 0x3B_atikmpag+19699 BUCKET_ID: 0x3B_atikmpag+19699 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x3b_atikmpag+19699 FAILURE_ID_HASH: {fa3a18f1-43cb-a622-48cf-3cb2f44d7575} Followup: MachineOwner --------- 3: kd> lmvm atikmpag start end module name fffff800`aed70000 fffff800`aee0c000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys Image name: atikmpag.sys Timestamp: Sat Feb 28 07:09:43 2015 (54F15BA7) CheckSum: 00097362 ImageSize: 0009C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

OK, so my thought about removed Store apps seems to have nothing to do with this?

 

The dumps blame the ATI driver - that all I'm competent enough to say. It is worth trying a different one from here Support Drivers and see if it helps until someone can analyse them properly.

 

Thanks Adam. Will try this.

 

OK, that was it. I uninstalled the ATI drivers automatically installed by Windows and replaced them with ones from HP support & drivers site. The driver & CCC are now a bit older but work OK. I can now sign oyut from accounts without BSOD.

Thanks Adam.

 

Didn't see Kari's post when composing the response below.
"Nothing succeeds like success!"
Good job!

Store apps mostly work in the user space - and are pretty much isolated from the kernel space (which is where BSOD's come from).
That being said, there are circumstances where actions in the user space can affect the kernel space. A common example of this is when adjusting printer settings.

Onwards to the BSOD analysis......

You don't have any Windows Updates. Please get all available updates.
I just installed build 9926 and already have 6 updates before updating to the latest build (I'm also installing the new tools that were released).

You have problems with these devices in Device Manager:

The first device has problems and was stopped by Windows. Try reinstalling the drivers for this device.
The next device doesn't have drivers installed, It's most likely HP ProtectSmart HD Protection or HP 3D DriveGuard. Please install it
The last 2 devices are most likely your JMicron Card Reader. The driver package from HP should install both of them, but check to be sure after you've installed the package.

The WER section of MSINFO32 shows several BSOD's due to the video drivers (as do the memory dumps, as adamf noted earlier).
Sp the first step is to try new video drivers. If that doesn't work, then I'd suggest trying Driver Verifier and some hardware diagnostics in order to rule out some problems. Here's instructions for Driver Verifier for Win8.1 - the screens for Win10 should be similar: Driver Verifier Settings . The link for the hardware diags is here: Hardware Diagnostics

I normally don't discuss this, but as you've mentioned the apps stuff, I'll give it a go.
The stack text from the memory dumps contains a lot of gibberish.
Most times this gibberish is because the minidump only shows kernel mode stuff - so I make the assumption that the gibberish is most likely user mode stoff that the minidump couldn't process fully. If I'm correct in this assumption, then it's possible that the user mode stuff is doing things that don't translate well into kernel mode things (and have caused the crashes). Unfortunately, there's no easy way of verifying that (although looking at full memory dumps could help - and may be needed later on).

A look at the raw stack text shows that both the AMD video drivers and the DirectX driver (dxgkrnl.sys) were involved in these crashes.
And there's new features with DirectX that may/may not be compatible with your video card (so now we've increased the possibilities from just hardware or software to hardware/software/compatibility *Sad

The errors that the system has spit out are of the type that are usually responsive to Driver Verifier.
This doesn't mean that Driver Verifier will find anything, but it's another step to make to rule out something else (in kernel mode) that's causing the AMD drivers to crash).

Your BIOS dates from 2013. Check to see if HP has a more updated BIOS for your system - and if so, install it immediately.

Your wdcsam64.sys driver dates from 2008, is likely not compatible w/Win10, and is a known cause of BSOD's in earlier versions of Windows on some systems. Please uninstall the Western Digital software and then verify that the driver has been removed (after a reboot).

The list of 3rd party drivers in the memory dumps is fairly short. Another hint of a hardware/compatibility/Windows driver problem is having such a short list. Again, this isn't a definitive diagnosis - but it does help to point us in a direction to look.

Video drivers for a laptop are best obtained from the laptop manufacturer. The reason for this is that most manufacturers modify the standard video drivers to accomodate switching software and to make the drivers work well with other video drivers on the system. In your case, there are also Intel graphics drivers present in the memory dumps.
An option in this case would be to disable the AMD graphics card to see if the BSOD's stop.
Or, you can disable the Intel graphics card and update the AMD card with drivers from the AMD website.

Please look at the older drivers listed in the memory dumps below and update them from the HP site as you are able.
The links below the list will get you started on finding updates.
You can also find updates for the HECIx64.sys driver (for the Intel Management Engine Interface) from Intel Download Center

Analysis:
The following is for informational purposes only.
Code: **************************Tue Mar 24 07:53:57.043 2015 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\032415-17421-01.dmp] Windows 8 Kernel Version 10041 MP (4 procs) Free x64 Built by: 10041.0.amd64fre.fbl_impressive.150313-1821 System Uptime:0 days 0:02:43.751 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :atikmpag.sys ( atikmpag+19699 ) BugCheck 3B, {c0000005, fffff803006f8fdc, ffffd0002465a810, 0} BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b) Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff803006f8fdc, Address of the instruction which caused the bugcheck Arg3: ffffd0002465a810, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_STR: 0x3B DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: atieclxx.exe FAILURE_BUCKET_ID: 0x3B_atikmpag+19699 CPUID: "Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz" MaxSpeed: 2400 CurrentSpeed: 2395 BIOS Version 68SRR Ver. F.40 BIOS Release Date 03/12/2013 Manufacturer Hewlett-Packard Product Name HP ProBook 4530s Baseboard Product 167C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Tue Mar 24 07:50:49.481 2015 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\032415-21500-01.dmp] Windows 8 Kernel Version 10041 MP (4 procs) Free x64 Built by: 10041.0.amd64fre.fbl_impressive.150313-1821 System Uptime:0 days 0:03:34.189 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :atikmpag.sys ( atikmpag+19699 ) BugCheck 3B, {c0000005, fffff80318093fdc, ffffd000a2933810, 0} BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b) Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80318093fdc, Address of the instruction which caused the bugcheck Arg3: ffffd000a2933810, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_STR: 0x3B DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: atieclxx.exe FAILURE_BUCKET_ID: 0x3B_atikmpag+19699 CPUID: "Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz" MaxSpeed: 2400 CurrentSpeed: 2395 BIOS Version 68SRR Ver. F.40 BIOS Release Date 03/12/2013 Manufacturer Hewlett-Packard Product Name HP ProBook 4530s Baseboard Product 167C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Tue Mar 24 07:46:33.935 2015 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\032415-28484-01.dmp] Windows 8 Kernel Version 10041 MP (4 procs) Free x64 Built by: 10041.0.amd64fre.fbl_impressive.150313-1821 System Uptime:0 days 1:20:53.643 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :atikmpag.sys ( atikmpag+19699 ) BugCheck A, {f, 2, 0, fffff803c6691be1} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: 000000000000000f, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff803c6691be1, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: atieclxx.exe FAILURE_BUCKET_ID: AV_atikmpag+19699 CPUID: "Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz" MaxSpeed: 2400 CurrentSpeed: 2395 BIOS Version 68SRR Ver. F.40 BIOS Release Date 03/12/2013 Manufacturer Hewlett-Packard Product Name HP ProBook 4530s Baseboard Product 167C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Mon Mar 23 23:06:55.694 2015 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\032415-29750-01.dmp] Windows 8 Kernel Version 10041 MP (4 procs) Free x64 Built by: 10041.0.amd64fre.fbl_impressive.150313-1821 System Uptime:0 days 7:31:42.402 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :atikmpag.sys ( atikmpag+19699 ) BugCheck 3B, {c0000005, fffff80295a84fdc, ffffd000257dc810, 0} BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b) Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80295a84fdc, Address of the instruction which caused the bugcheck Arg3: ffffd000257dc810, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_STR: 0x3B DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: atieclxx.exe FAILURE_BUCKET_ID: 0x3B_atikmpag+19699 CPUID: "Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz" MaxSpeed: 2400 CurrentSpeed: 2395 BIOS Version 68SRR Ver. F.40 BIOS Release Date 03/12/2013 Manufacturer Hewlett-Packard Product Name HP ProBook 4530s Baseboard Product 167C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` [/quote] 3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: **************************Tue Mar 24 07:53:57.043 2015 (UTC - 4:00)************************** wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C) HECIx64.sys Tue Oct 19 19:33:43 2010 (4CBE2AD7) snp2uvc.sys Mon Nov 19 22:01:44 2012 (50AAF298) igdkmd64.sys Thu Oct 31 14:28:01 2013 (5272A131) amdkmpfd.sys Tue Sep 16 21:45:39 2014 (5418E7C3) athwnx.sys Fri Oct 24 04:30:20 2014 (544A0E1C) rt640x64.sys Wed Jan 28 16:19:48 2015 (54C95274) atikmpag.sys Sat Feb 28 01:09:43 2015 (54F15BA7) atikmdag.sys Sat Feb 28 02:19:23 2015 (54F16BFB) SynTP.sys Fri Mar 6 17:30:56 2015 (54FA2AA0) intelppm.sys Fri Mar 13 23:55:48 2015 (5503B144) filecrypt.sys Sat Mar 14 00:01:38 2015 (5503B2A2) synth3dvsp.sys Sat Mar 14 00:09:09 2015 (5503B465) mirahid.sys Sat Mar 14 00:42:29 2015 (5503BC35) storqosflt.sys Sat Mar 14 00:47:51 2015 (5503BD77) [/quote] http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=snp2uvc.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=amdkmpfd.sys
http://www.carrona.org/drivers/driver.php?id=athwnx.sys
rt640x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
filecrypt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
synth3dvsp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
mirahid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
storqosflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

Well, that's good news. Now to check Johns answer and see what else I should have considered *Smile

 

@John, I am sorry. I know how it feels when you compose a long response only to find out that the thread was resolved or closed when you finally post it *Smile.

Thanks anyway.

 

Thanks Adam!
Not a problem Kari, I'm just happy that you've solved the problem. :0)
FWIW - I have an AMD video card on my laptop and am dreading the day when I update it to Win10.

 

Hehe. Let's see how it goes this time when you try upgrading to Windows 10 *Tongue

 

FYI - it looks like 28 new BSOD codes for Win10. Mostly live debugging and 2 for XBox

 

So, now they are introducing the BSOD with Xbox as well? I wonder what would happen to the Red Ring of Death for the XBOX?
Any chance we would be soon seeing Xbox Dumps on forums? *chuckle
Too much work to do John once Windows 10 goes live :0)


-Pranav