New
#161
Hey all, so my computer has been running slow as crap and like general shit so far. I guess I'm just used to SSD performance, or maybe edge browser is bad. Either way pages stopped responding and then I crashed, here's the DM log. If it's something new I have to buy I'm alright with that, hell black Friday is coming up so whoopee, but this is getting irritating.
The exact same dumps are in the zip and according to the logs no new crashes have appeared.
If you have had a new crash, what error code was displayed?
Not sure, this time it crashed but the screen flashed and went to black before I could see the error code, it was oddly fast so maybe no dump file was made? Not sure, here's another DM log I just ran, I might've put the wrong one in. But aside from that, anything I can do next?
This is very strange, no logs after 22th.
I would like to know if on your system there are event logs after 22th.
Please enter Windows logo + r, type/copy paste "eventvwr.msc" (without quotes) and press enter.
In the Windows Logs, check every part (Application, Security, Setup, System) for the log dates.
Please let me know if the dates are later then 22th this month.
Please search in the event logs for the event id: 1001.
I don't know where exactly honestly.
This event id is the event that is the record of the bluescreen, but only the error code and a few parameters. Not much but it would be helpful.
in the application section there are a lot of events with the ID 1001.
Well I crashed again, weird thing is, after checking in my Minidump folder, all the old logs are gone and only this one latest dump file stayed. I updated windows a few hours ago, could that have something to do with it? Anyways, hopefully this dump file sheds light on something.
How is the hard drive connected?
Is the cable the same you also have used for the other hard drive?
Code:Probably caused by : hardware ( REGION_PAGED_OUT ) Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000061, physical page number Arg3: 0000024f2a003180, zero Arg4: ffffd00022d42000, zero