*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,So on Friday (July 7th) I received a brand new gaming computer courtesy of iBuyPower.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff300c3b253c0, f5200003dbc72847, fffff300c3b243c0}
Probably caused by : memory_corruption
Followup: memory_corruption
0x403+
The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
Hmm... Well if the machine didn't blue screen until you updated drivers then you could try removing or reversing whatever it is you installed or updated.Unfortunately I don't have a CD or a USB, I will most likely be bringing it back. Is there any other way its something that can be fixed easily
Well, I looked for earliest restore points. It doesn't go back to when I installed the drivers. I could try a full factory reset if you recommend that. Although I don't know if the drivers that I installed caused the crashing to begin but I installed some GPU game ready drivers and messed with some registry stuff including removing xbox app's game DVR; the crashing happened before that though.Hmm... Well if the machine didn't blue screen until you updated drivers then you could try removing or reversing whatever it is you installed or updated.
It is possible for software to cause this bugcheck so try checking for restore point which would take you back before you installed anything.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
Also, about the restore; my last restore point doesnt go far enough. Like I said before I could attempt a factory reset if you feel like that is an option that could stop crashing.
As we are not sure which driver or drivers you updated you could either go for a reset or run the driver verifier and see if it turns up anything.
Please.Which dump file do you want? a new one?