All of them indicate memory corruption:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff8800a934688, fffff8800a933ee0, fffff80003244f0b}
Probably caused by : memory_corruption ( nt!MmPurgeSection+4eb )
Followup: MachineOwner
---------
Have you followed part 3 of the tutorial?
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa800313c8c0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
Followup: MachineOwner
---------
If yes, I would check how a different set of ram sticks work on the computer. (compatible with your mobo)
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {28, 2, 0, fffff8000330bd80}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner
---------