Hi Stefan. . .
Is it your system that BSODs or the one you're connected to via RD?
Is bsw.exe running on your system or the RD system -- BSODs?
I am not familiar with bsw.exe, but I do beta test other apps. I would think if all conditions are the same and the the system only BSODs under the beta version bsw, it is very likey involved or there is a conflict with another driver.
... bsw.exe somehow causes csrss.exe to fail with a "ReadMemory error: Cannot get nt!KeMaximumIncrement value. fffff78000000000: Unable to get shared data"
Bugcheck
0xf4 (0x3,,,) simply tells us that a process critical to Windows suddenly terminated.
csrss.exe is often seen with 0xf4, but the W7 SP1 system listed nothing as the probable cause, not even the usual
NT default.
Code:
BugCheck F4, {3, fffffa8004c92060, fffffa8004c92340, fffff80002be68b0}
Probably caused by : _
The dump listed bsw.exe as the process running, but didn't actually name bsw drivers as the probable cause. Have others reported BSODs while running the beta bsw version?
Yes, both minidumps are from VMs (VMWare), but i was able to reproduce this on a real machine too when logged in remotely. I can send you that crash dump too if needed.
I can run it fine both locally and on the remote system too, when i don't use Remote Desktop. It runs fine interactively.
I mentioned the Intel Ethernet driver because the May 2008 timestamp = Vista SP1 era. Since the BSODs are only occurring while RD'ing, the outdated Intel driver may be a contibuting factor. It should be updated -
https://www.sysnative.com/drivers/driver.php?id=E1G6032E.sys
The bsw developers are best suited to deal with crashes involving their app as they have symbol files not available to us.
However, I'll be glad to take a look at the non-VM dump to see if it yields any clues.
Regards. . .
jcgriff2
