Bsod 0xed hyper v6/17/2023 Some register values may be zeroed or incorrect. NOTE: The trap frame does not contain all registers. Typically the address is just plain bad or itĪrg1: fffffa8303aa41ea, memory referenced.Īrg2: 0000000000000000, value 0 = read operation, 1 = write operation.Īrg3: fffff8800556e328, If non-zero, the instruction address which referenced the bad memory ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-3770S CPU 3.10GHz Identifier = REG_SZ Intel64 Family 6 Model 58 Stepping 9 Product: Server, suite: TerminalServer DataCenter SingleUserTSīuilt by: 8_gdr.130410-1505 Windows 8 Kernel Version 9200 MP (4 procs) Free 圆4 ETW logging enabled on CoveFS / CoveFSDisk, giving us everything that CoveFS did right before the crash.Verifier enabled on all drivers at the time of the crash (giving us additional data about the crash).I'm going to post a technical description of the crash for anyone who can read this sort of thing. Paris has submitted the best dump to date on this issue and I've analyzed it in detail. The crashes only occur on Windows 8 / Windows Server 2012 (including Essentials). ![]() Srv2.sys is Microsoft's file sharing driver that translates network file I/O requests into local file I/O requests on the server, but the implication is of course that StableBit DrivePool may somehow be the cause of these crashes. Just to recap, I've received a number of memory dumps over the past month or so showing a system crash in srv2.sys. Continuing the thread from the old forum:
0 Comments
Leave a Reply. |