0

I've got a bsod (on windows 10.0.14393.0) and trying to figure out what happened. Event log says

bugcheckcode 122
bugcheckparameter1 0x4
bugcheckparameter2 0x0
bugcheckparameter3 0xffff8406530bf010
bugcheckparameter4 0xa782390

but I'm already stuck at parameter1 since when I looked at the corresponding bug check code reference page, there they only have listed parameter1 values 0x1, 0x2, 0x5, 0x6, 0x7, 0x8, 0x9, 0xA and 0xB.

Does anybody know where to find information about parameter1 value 0x4?

Later

Following suggestion in a comment by Jamie Hanrahan I am adding a link to the memory dump file dump.zip.

13
  • This type of crash can be caused by many things. What problem are you trying to solve?
    – Ramhound
    Commented Sep 1, 2016 at 18:27
  • 1
    There should be a crash dump file generated, you need to debug the dump file... tenforums.com/tutorials/…
    – Moab
    Commented Sep 1, 2016 at 18:58
  • 1
    This value is not documented even in the latest version of windbg. Commented Sep 1, 2016 at 19:23
  • 1
    Bugcheck code 0x122 in general, regardless of parameter1, means "This bug check indicates that an internal error in the Windows Hardware Error Architecture (WHEA) has occurred. Errors can result from a bug in the implementation of a platform-specific hardware error driver (PSHED) plug-in supplied by a vendor, the firmware implementation of error records, or the firmware implementation of error injection." The thing that stands out here is "hardware error". These usually come from problems with the CPU, the chipset, etc. There is a good possibility that a "machine check exception" occurred. Commented Sep 1, 2016 at 20:13
  • 1
    122 is decimal and turns in 0x7A (KERNEL_DATA_INPAGE_ERROR). Commented Sep 2, 2016 at 4:27

1 Answer 1

1

You made a mistake. The 122 is decimal. The hex value is 0x7A. The 0x7A stands for Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR

The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

1
  • 1
    Ah, oops! However the description quoted is incorrect. You can get "inpage errors" from any mapped file, not just the pagefile. These are usually IME caused by disk read errors, but further looking at the dump suggests a deeper problem: corruption of Mm data structures. I'd be running a memory test. Commented Sep 10, 2016 at 1:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .