2 Dell Latitude 3440's with Windows 10 Clean Install, both BSOD 0x154

link470 · 16 May 2016

Hi everyone,

I'm struggling with 2 Dell Latitude 3440 notebook PC's that I'm trying to install Windows 10 Pro on. One of which has been running Windows 7 flawlessly for 2 years, the other one is brand new out of the box, never been opened. As always when doing a reinstall of an OS or even a fresh install on a newly delivered computer, I test the RAM and HD. RAM is tested with Memtest 86+ (what else?) and for the HD's, I have a few different sector checking utilities I use on them. All tests passed on both machines, as I expected.

So, I start the install. I'm using a fresh copy of Windows 10 64-Bit. After zeroing the hard drive in each machine, I start the install. Installation goes smoothly. I then download the drivers (all from Dell's website, for the Latitude 3440, for Windows 10 64-Bit) and install (not necessarily in this order):
•Intel Chipset Driver
•Intel Management Engine Interface Driver
•Trackpad Driver
•Audio Driver (via Device Manager)
•Ethernet and WiFi Drivers (via Device Manager)
•SD Card Reader Driver
•Intel Rapid Storage Technology Driver
•Video Driver

On one machine, the person needed it back (this was the one I had wiped Windows 7 on and done a fresh install to Windows 10 Pro), so I installed my usual set of applications and then gave it to her.

On the second machine, I was done with it for the night and didn't start the software load because it was getting late, so I shut it down and started it up again, and somewhere in here, I can't remember where, it threw a UNEXPECTED STORE EXCEPTION 0x154 bluescreen. I fired it back up and collected some logs (attached), and tried for the next half hour or so to watch videos on YouTube in 1080p full screen, launch Windows applications, shut down and boot up the computer, restart the computer (which we know is different than shutting down by default thanks to Fast Boot), and anything else I could possibly think of to try to make it bluescreen again, and I couldn't.

I also just received a message with a photo attached from the person using the first computer, and it's a photo of the exact same bluescreen that she just received while resuming her session on her laptop (I think she opened the lid after it was asleep, but I can't 100% confirm the exact action taken). When I had that machine last week, everything went fine during the installation and software load and I thought it was good to go.

On the laptop I do have, with no software installed at all besides the drivers, I tried installing the Intel Driver Update Utility, just to see if by chance it detected new IRST, Chipset, or IME/AMT drivers, and it didn't. The only driver it detected was a video driver that could be updated, but detected that the current version was a manufacturer specific driver.

Everything I can find in the bluescreen logs seems to relate to a disk error or storage driver, and that's what I've found online relating to this error too. But I have a really hard time believing both drives are bad, especially with one machine that worked flawlessly with Windows 7 Professional for 2 years, and another brand new out of the box having the exact same issue, and both tested by me using my usual tests before proceeding with an install.

Thanks again very much in advance for any help! This is thoroughly annoying. The attached file below is from the Latitude 3440 that I currently have with me, the one with no extra software installed besides drivers from Dell's website, and that's it. This bluescreen seems extremely difficult to reproduce reliably.

fireberd · 17 May 2016

A comment on your install sequence. Unlike older OS', you only have to install the drivers for the devices Windows 10 does not install. Win 10 installs most (correct) drivers. Maybe that is the cause?

axe0 · 17 May 2016

What tests have been used on the HDD?

Please run below test on all systems experiencing this problem.

Diagnostics Test

System File Check

Please try following:

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

link470 · 17 May 2016

axe0 said:

What tests have been used on the HDD?

I use ViVARD on an Ultimate Boot CD. This BIOS for the Latitude 3440 only accepts ACHI though, so SeaTools doesn't even see the drive on that controller.

EDIT: Just took the drive out of the laptop and put it into another machine with a controller running in IDE mode. Verified the SMART stats which all looked good and confirmed the drive has very low power on hours (brand new), and re-ran ViVARD. Test passed with 0 bad sectors. Currently running SeaTools on the drive as well.

EDIT2: SeaTools just completed its Long Test. Passed, no errors as expected.

axe0 said:

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\

Interestingly enough, it did (on an install only a few days old and with no applications installed besides drivers). I got that result the first time, and then I restarted, and Windows showed that it was Configuring Windows/Getting Windows Ready for a good hour or so. Once the system rebooted, I ran sfc /scannow again and the same message showed up. CBS log is attached [Edit: Removed].

axe0 said:

Make a photo of the result and post it.

Wasn't sure what you wanted a photo of.

fireberd said:

A comment on your install sequence. Unlike older OS', you only have to install the drivers for the devices Windows 10 does not install. Win 10 installs most (correct) drivers. Maybe that is the cause?

Interesting, that crossed my mind as well. My process in the past has always been to install all drivers before even connecting to the internet, because I've had way too many experiences where Windows Update tries to say "lol np I got this!" and then downloads something completely incorrect or something that ends up causing issues, or something generic when I need a manufacturer specific driver.

I do, however, let Windows Update run afterwards and check any drivers it recommends. Usually Windows Update recommends no driver updates, but if there are any, I usually end up installing them if they look ok or if it actually recommends something I missed or a newer version of a driver that wasn't available on the manufacturers website.

axe0 · 18 May 2016

A photo of the SFC scan result.

The corruption is opencl.dll, if you're not familiair with it: opencl.dll is being replaced with driver updates from Nvidia but it doesn't cause any problems so it can safely be ignored.

link470 · 18 May 2016

axe0 said:

A photo of the SFC scan result.

Ah, ok. I didn't take a screenshot, but the results in the command window looked like just the general message you'd get if problems were found. I attached the CBS log in my last post. If you do need a screenshot, let me know and I'll get one for you after a third scan first thing tomorrow morning.

axe0 said:

The corruption is opencl.dll, if you're not familiair with it: opencl.dll is being replaced with driver updates from Nvidia but it doesn't cause any problems so it can safely be ignored.

Interesting, ok. The odd thing is it's an Intel chipset with Intel integrated graphics, would that still cause an Nvidia driver issue? Is that a driver included in the OS anyways and will always cause problems with sfc scans even on fresh Windows 10 installs and even if the driver doesn't need to be active (because of no Nvidia components)?

Thanks for your time so far, really appreciate it as this is a very annoying issue to diagnose on fresh installations and hardware. Any other steps I should take next before concluding it must be a compatibility issue between Windows 10 and the Latitude 3440 or drivers provided by Dell?

EDIT: One other note. The person who has the first Latitude 3440 got back to me again today and said it's been great and she can use it all day with absolutely no problems, until she closes the lid and opens it again a couple minutes later (sleeping and resuming the session). At that point, she says that every 2nd time she does that, it shows a black screen on resume and she has no choice but to hold power and cold reboot. Not sure if it's related but it's definitely interesting. That machine was also confirmed to get the same blue screen (the one she sent me a photo of).

axe0 · 18 May 2016

The story I described is the most occuring, opencl.dll is a Windows dll but it looks like in your case it is corrupted.
Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

I'd like some more logs for analysis to see if I can get more information or find a pattern or something before posting suggestions :)

lifetec · 18 May 2016

In the stack of the dumpfile partmgr and volmgr are named.

Code:

  STACK_TEXT:  
ffffd000`42c67a78 fffff803`2cc87d96 : 00000000`00000154 ffffe001`f5156000 ffffd000`42c67b20 00000000`00000000 : nt!KeBugCheckEx
ffffd000`42c67a80 fffff803`2cbddf00 : ffffe001`f593e040 ffffc000`b626a390 00000000`00000000 ffffc000`b2a3c000 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x22
ffffd000`42c67ac0 fffff803`2cbbc07f : 00000000`00000000 00000000`00000000 c0000022`00000000 ffffe001`f2df6cf0 : nt! ?? ::FNODOBFM::`string'+0x2e00
ffffd000`42c67af0 fffff803`2cbd282d : 00000000`00000000 ffffd000`42c67c90 00000000`00000052 ffffc000`b75a0c5c : nt!_C_specific_handler+0x9f
ffffd000`42c67b60 fffff803`2cb24c19 : 00000000`00000000 00000000`000000c1 ffffd000`42c68160 fffff803`2cb03b92 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`42c67b90 fffff803`2cb23028 : ffffd000`42c68aa8 ffffd000`42c687c0 ffffd000`42c68aa8 ffffe001`00000001 : nt!RtlDispatchException+0x429
ffffd000`42c68290 fffff803`2cbd73c2 : ffffe001`f4078260 00010000`0000116c 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x144
ffffd000`42c68970 fffff803`2cbd5aa1 : 00000000`00000000 ffffe001`f57c5280 00010502`00000002 fffff801`4d2b5e10 : nt!KiExceptionDispatch+0xc2
ffffd000`42c68b50 fffff803`2cb98670 : ffffd000`42c47000 ffffd000`42c47000 00000000`00001000 fffff803`2cb7a918 : nt!KiPageFault+0x221
ffffd000`42c68ce0 fffff803`2cb7a918 : ffffe001`f5156050 fffff803`2ccc76a8 ffffd000`42c47000 00000000`00000400 : nt!RtlDecompressBufferXpressLz+0x50
ffffd000`42c68d00 fffff803`2cb89f0c : 00000000`00000002 00000284`b93209e0 ffffe001`f5156050 00000000`00000000 : nt!RtlDecompressBufferEx+0x64
ffffd000`42c68d50 fffff803`2cb89d76 : ffffe001`f471eb90 ffffda75`930d4d59 ffffe001`f553f040 fffff803`2cb8899c : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x15c
ffffd000`42c68e20 fffff803`2cb8a1f1 : 00000000`00000002 ffffe001`f46ae020 ffffe001`f5156050 00000000`00000014 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6
ffffd000`42c68e80 fffff803`2cb8a3f5 : ffffe001`ffffffff fffff801`0000009e ffffe001`00000000 ffffe001`f471eb90 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1
ffffd000`42c68f20 fffff803`2cb8ae9e : fffff803`2cd866b0 ffffe001`f471eb90 ffffd000`00000000 ffffe001`f471eb90 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
ffffd000`42c68fe0 fffff803`2cb8af49 : ffffe001`f5156000 ffffd000`42c690f0 fffff803`2cb8af28 fffff803`2cb8af28 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52
ffffd000`42c69030 fffff803`2cb30e95 : ffffe001`f593e040 ffffd000`42c690f0 ffffe001`f5e54530 fffff803`2cb77e40 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffd000`42c69060 fffff803`2cb849d0 : 00000000`00000003 ffffe001`f471eb90 ffffe001`f553f000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`42c690b0 fffff803`2cb86964 : ffffd000`42c691b0 fffff803`2cb8abd0 ffffe001`f5156000 ffffd000`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xac
ffffd000`42c69180 fffff803`2cb86677 : ffffe001`f5156000 ffffe001`f471eb90 fffff803`2cd896c0 fffff803`2cd896c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x180
ffffd000`42c691d0 fffff803`2cb84861 : 00000000`0000000c ffffe001`f5e545e0 ffffe001`f471eb90 00000000`00000010 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbb
ffffd000`42c69250 fffff803`2cb846f5 : ffffe001`f5e545e0 ffffd000`42c69300 ffffd000`00000010 fffff6fc`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165
ffffd000`42c692d0 fffff803`2cb16311 : ffffe001`00000000 00000000`00000000 00000000`00000000 fffff801`496813cc : nt!SmPageRead+0x51
ffffd000`42c69320 fffff803`2cb15792 : 00000000`00000002 00000000`00000000 ffffe001`f5e544e0 00000000`00000000 : nt!MiIssueHardFaultIo+0x129
ffffd000`42c693a0 fffff803`2caf5823 : 00000000`c0033333 fffff801`4a070000 ffffd000`42c695a0 00000000`00000000 : nt!MiIssueHardFault+0x162
ffffd000`42c69440 fffff803`2cbd59bc : 00000000`00000000 00000000`00000000 00000000`c00000c0 fffff803`2cb23de4 : nt!MmAccessFault+0x7f3
ffffd000`42c695a0 fffff803`2cb14295 : fffff803`2cb14256 fffff801`4a094c50 ffffe001`f283db60 ffffe001`f5935700 : nt!KiPageFault+0x13c
ffffd000`42c69738 fffff803`2cb14256 : fffff801`4a094c50 ffffe001`f283db60 ffffe001`f5935700 00000000`00000003 : nt!RtlImageNtHeaderEx+0x35
ffffd000`42c69740 fffff803`2cef856e : ffffd000`42c698c8 00000000`00000000 00000000`00000000 fffff803`2cb0f630 : nt!RtlImageNtHeader+0x1e
ffffd000`42c69770 fffff801`4a061a12 : ffffd000`42c698c8 00000000`00000000 ffffe001`f283db60 fffff803`2ca19770 : nt!MmResetDriverPaging+0x3a
ffffd000`42c697b0 fffff801`4a06187b : 00000000`00000000 fffff803`2cbd1216 00000000`00000217 fffff803`2cb0ec7c : volmgr!VmpPartitionRemovedImmediate+0x46
ffffd000`42c69880 fffff801`4a053f95 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000000 : volmgr!VmpPartitionRemoved+0x4f
ffffd000`42c698c0 fffff803`2cb6c53e : ffffe001`efdbf690 00000000`00000000 00000000`00000000 00000000`00000000 : volmgr!VmpSetAttributesCallback+0xfc5
ffffd000`42c698f0 fffff803`2cf3b469 : 00000000`00000010 fffff801`488f1b00 00000000`00000000 00000000`00000200 : nt!IoSynchronousCallDriver+0x52
ffffd000`42c69950 fffff801`488f9c03 : 00000000`00000000 ffffe001`f27a4c60 ffffd000`42c699f9 00000000`00000001 : nt!IoForwardIrpSynchronously+0x41
ffffd000`42c69980 fffff801`488f6ad7 : ffffe001`f27a4c60 00000000`00000000 ffffe001`f283dcb0 fffff801`488f1b00 : partmgr!PmTakePartition+0x173
ffffd000`42c69a60 fffff803`2cab3a00 : ffffe001`f280fd50 ffffe001`f27a4b10 00000000`00000000 00000000`00000000 : partmgr! ?? ::FNODOBFM::`string'+0x7f7
ffffd000`42c69b10 fffff803`2caccc59 : fffff803`2ce1d200 ffffe001`f593e040 fffff803`2cab3910 ffffe001`f284b010 : nt!IopProcessWorkItem+0xf0
ffffd000`42c69b80 fffff803`2cb77b65 : 00000005`bd9bbfff 00000000`00000080 ffffe001`ee683040 ffffe001`f593e040 : nt!ExpWorkerThread+0xe9
ffffd000`42c69c10 fffff803`2cbd1926 : ffffd000`3f300180 ffffe001`f593e040 fffff803`2cb77b24 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffd000`42c69c60 00000000`00000000 : ffffd000`42c6a000 ffffd000`42c64000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

So it looks that this bsod is related to windows Partition Management Driver and Volume Manager Driver.

So it might be that the freezing/crashing after opening the lid etc. has a other cause.
Do you know if the airplane mode is enabled on both of the laptops, because the Dellrbtn.sys is from 2012.And there is a newer driver on the supportpage with Release Date: 18 Oct 2013.
DellRbtn Fri Aug 03 23:32:54 2012
Driver Description: OSR Open Systems Resources Airplane Mode Switch Driver (as the driver name states
Driver Update Site: this may be available from Dell)

In the eventviewer i found this

Event[589]:
Log Name: System
Source: rt640x64
Date: 2016-05-11T21:48:01.726
Event ID: 1
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-H6T8J89
Description:
Realtek PCIe GBE Family Controller is disconnected from network.

This driver is from may 2015 (predates windows 10).
rt640x64 Tue May 05 18:21:03 2015
Driver Description: Realtek NICDRV 8169 PCIe GBE Family Controller driver
Look if a newer driver is avaliable on the supportpage

axe0 · 18 May 2016

Lets have a 2nd look at the stack though I'm not sure what exactly happens.
We see a few I/O actions, as usual happens the problem when a pagefault occurs which is last occuring after RtlDecompressBufferXpressLz is being called where the exception occured on.
The volume manager driver & partition manager driver are both system file drivers, the volume manager driver is being flagged when dumping the raw stack & the probable cause is hardware_disk.
Even though the same problem has occured on 2 systems this can only be said on 1 for sure because there is only logs from 1 system.
I suspect that either the chipset controller driver is the cause or the hard drive itself.

Code:

Probably caused by : hardware_disk

link470 · 20 May 2016

Hi everyone,

Thought I'd give you an update. I still have the second Latitude 3440, but I haven't had a chance to work with it much in the last couple days or do any further testing. I also haven't heard much from the first user who has theirs, and haven't been able to obtain any logs from that one cause she's been very busy.

axe0 said:

Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

Ran this on the machine that I have (that I still can't make do anything wrong since that initial bluescreen...of course), and it needed the install.wim. I didn't have a flash drive handy when I ran it with the Windows 10 installer on it so I'll need to get back to that later. But at this point, I'm much more tempted to wipe that machine again and reinstall Windows 10 64-Bit and reinstall drivers.

Would you recommend what firebird recommended above, which is to let Windows Update install everything and completely ignore things like chipset drivers etc. from Dell and only install what's missing in Device Manager? To me this sometimes works, but has led to interesting problems in the past if I don't have those manufacturer specific drivers installed, even if Device Manager looks good.

lifetec said:

In the stack of the dumpfile partmgr and volmgr are named.

So it looks that this bsod is related to windows Partition Management Driver and Volume Manager Driver.

axe0 said:

I suspect that either the chipset controller driver is the cause or the hard drive itself.

Code:

Probably caused by : hardware_disk

That's what I was able to find by tracing the bluescreen log as well, and was suspicious maybe it was a IRST or AHCI controller driver of some sort causing issues. This machine also has one of those hybrid 500GB SSD/HDD's in it too from Seagate (came standard with this machine) and I don't believe the first one has it. Yet they're both experiencing similar problems and both drives and hardware tested fine, so I'm ruling that out.

lifetec said:

Do you know if the airplane mode is enabled on both of the laptops, because the Dellrbtn.sys is from 2012.And there is a newer driver on the supportpage with Release Date: 18 Oct 2013.

It's not enabled (or shouldn't be). The first user who has hers uses it over WiFi, and I doubt she even knows Airplane Mode is there (she was running Windows 7 on that machine previously for 2 years with no issues). The driver installed for Airplane mode though on the laptop that I have is the most current one from Dell's website, but I've noticed that some odd numbers come up sometimes with dates. For example, Dell's website may say the driver was released in July 2015, but the driver date in Device Manager shows 2014 or even earlier. That may be what's happening here where the date is mis-labeled as a "published date" from Dell, and not neccesarily the date of the driver itself.

As far as I know, all drivers are the most up to date released ones from the Dell website for Windows 10 64-Bit. Part of me was wondering if I may have installed drivers for the wrong OS by accident, but I highly doubt this seeing as I don't usually make that mistake, the driver downloads I have still on the install flash drive match what's on the website for Windows 10, and this is happening on 2 identical machines. I just did another install using the same install ISO from Microsoft Techbench via flash drive on a Dell Optiplex 3010, and that's working no problem.

I actually contacted Dell Enterprise hardware support yesterday about this issue, and the representative said he escalated the issue up to engineering to see if they had new drivers coming down the pipe (I asked because part of me is still fairly suspicious it's a driver issue of some sort for Windows 10).

axe0 said:

I'd like some more logs for analysis to see if I can get more information or find a pattern or something before posting suggestions

Ugh, you and me both.

I'm really hoping to get some data from this first machine soon, since that's the one I sent off to the user thinking everything was ok, but has reported problems since.

Thanks again for your time in troubleshooting, really appreciate it and would just love to get these otherwise working laptops finished and into service.