(on x86, this will be the ebp that goes with the procedure KiTrap)Īrg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT trap on the appropriate frame will show where the trap was taken tss on the part before the colon, then kv. The first number in theīugCheck params is the number of the trap (8 = double fault, etc)Ĭonsult an Intel x86 family manual to learn more about what these That the kernel isn't allowed to have/catch (bound trap) or that This means a trap occurred in kernel mode, and it's a trap of a kind Here's the actual minidump file and bugcheck analysis, if anyone is able to tell me what's going on with my PC, I would be extremely grateful as this has been going on for a while now. I can confirm that both of my RAM sticks aren't the problem as I ran memtest86 over night and received 0 errors through 4 passes. I found, using Bluescreenview, that there was three files (hal.dll ntoskrnl.exe PSHED.dll) that supposedly caused the BSOD to occur.įrom the bugcheck analysis I found that the PROCESS_NAME was "System" and the IMAGE_NAME and MODULE_NAME were both "hardware", using this information I kind of gathered that the problem is a piece of hardware within the actual PC although, I'm not 100% sure that's what it's actually telling me. This was found through a bugcheck analysis, which I will show the results to further on. I encountered a BSOD today which was initially unnamed but was found to be an UNEXPECTED_KERNEL_MODE_TRAP error. Firstly, I'll start with a list of my specs, I'm sure I know all of the needed specs other than the exact model of my RAM.
0 Comments
Leave a Reply. |