This is caused by two possible scenarios. First thing to do is review the device drivers for file system and networking. Are they all signed? Sometimes rolling back one or more versions provides a more stable (for that system) driver version.
1. The IRP stack size was exceeded, kb285089. Uncommon but I still see this even on Windows 8. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters IRPStackSize (REG_DWORD) (CASE SENSITIVE!) The default value of the IRPStackSize parameter is 15. The range is from 11 (0xb hexadecimal) through 50 (0x32 hexadecimal). On some computers, values from 33 through 38 can cause problems. I use 18 which generally fixes the issue: reg add "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" /v IRPStackSize /t REG_DWORD /d 18 /F Increase by 3’s. (Forget where I read that) 2. Too many file system filter drivers or a miss-behaving file system filter driver. (Rare in Win 7 forward with validated/signed drivers). This was an issue seen in Windows XP, especially in the first few years. AntiVirus applications were notorious for causing this issue as a miss-behaving file system filter driver. If updating or rolling back drivers does not resolve, try KB906866 for a different IRP registry key. Peter Boyles BIS Engineering Analyst PepsiCo Inc. | Global End User Services | GEUS Deployment Services From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Delaughter Sent: Thursday, November 5, 2015 11:18 AM To: [email protected] Subject: [MDT-OSD] Dell E5520 and WinPE 10 Problems Has anyone used WinPE 10 with the E5520s yet? I just upgraded the ADK from 8.1 to 10 on my SCCM site server, and now the SCCM task sequences fails with "Unable to read task sequence configuration disk" on E5520s. It works fine on our E6XXX models. During the error on the SCCM task sequence, if I check the disks in cmd prompt, it reports "no disks found". If I run the same check early in the loading of the boot media, I get the same thing. But if I wait for the boot media to get to the wizard that allows me to select the task sequence, I can see it in diskpart again. My suspicion is that after the reboot, the HD either isn't coming back up at all, or isn't visible quick enough and the task sequence fails because of it. I tried to boot to a vanilla WinPE from a usb drive, and I get a BSOD during the winpeinit script. The stop error is "NO_MORE_IRP_STACK_LOCATIONS" -- Joshua Delaughter
