C
chinibopini
Guest
Hello everyone,
For the past couple of months, I've been having freezing issues with my machine and the problems are happening more often as time goes on.
I will be usually multi tasking with a video game and Firefox open, then I will try to execute another task and the system will lock up, the mouse will disappear and 10 seconds later the system will reboot. I assume a BSOD is happening but I don't ever see it.
The most recent one happened yesterday, where I had a video stream going on Firefox and plugged in my USB Arcade controller. The system rebooted, prompted a disk check and repair after bios screen, then repaired for about 2 minutes and went into windows normally. I'd like to note that neither the freeze upon plugging in a USB device nor the disk repair had ever appeared before.
I usually check Event Viewer afterwards and it says the system has recovered from a bugcheck. This is the last one:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffac8ed5c9fd48, 0x0000000000000002, 0xfffff8056a85efe9, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d0868bda-dd02-4aac-b7e0-bc1dc65ff3a7.
And these are from other random times over the last 2 months:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000008, 0x0000000000000000, 0xfffff80434eb6c09). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 91eee0e7-ea22-432a-bde3-f972085f393c.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff8005693a590, 0xffffde0f8e80e0d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: de86f0cc-2c49-46de-88a3-b040d6c7f436.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xfffff806c4a59e8f, 0x0000000000000008, 0x0000000000000001, 0xfffff80739589ee8). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5e71fa75-65e3-4be2-80f0-98d48d586e76.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000000000085a, 0x00000000000000ff, 0x0000000000000000, 0xfffff80450901203). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a9ef8cfe-61d7-4548-a971-2ddca277b127.
The memory.dmp file is almost a gig large. There are also a handful of minidumps in systemroot.
Some assorted information:
When googling the bug check error two days ago, I was referred to a forum where it was speculated that it could be a driver issue and a suggestion to run the driver verifier process. I ran driver verifier, selected all drivers and rebooted which began an infinite crash loop shortly after reboot (around the time startup programs initialized). I eventually got into safe mode, deleted the driver verifier settings and disabled all startup programs for good measure. I'm able to boot and use system again normally.
After one of these freezes about a month or two ago, I ran mdscheduler and it said there is a problem with your computer's memory. I then ran memtest86, twice, and it found no errors -- then booted into system, ran mdscheduler again and it found no issues.
Continue reading...
For the past couple of months, I've been having freezing issues with my machine and the problems are happening more often as time goes on.
I will be usually multi tasking with a video game and Firefox open, then I will try to execute another task and the system will lock up, the mouse will disappear and 10 seconds later the system will reboot. I assume a BSOD is happening but I don't ever see it.
The most recent one happened yesterday, where I had a video stream going on Firefox and plugged in my USB Arcade controller. The system rebooted, prompted a disk check and repair after bios screen, then repaired for about 2 minutes and went into windows normally. I'd like to note that neither the freeze upon plugging in a USB device nor the disk repair had ever appeared before.
I usually check Event Viewer afterwards and it says the system has recovered from a bugcheck. This is the last one:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffac8ed5c9fd48, 0x0000000000000002, 0xfffff8056a85efe9, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d0868bda-dd02-4aac-b7e0-bc1dc65ff3a7.
And these are from other random times over the last 2 months:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000008, 0x0000000000000000, 0xfffff80434eb6c09). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 91eee0e7-ea22-432a-bde3-f972085f393c.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff8005693a590, 0xffffde0f8e80e0d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: de86f0cc-2c49-46de-88a3-b040d6c7f436.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xfffff806c4a59e8f, 0x0000000000000008, 0x0000000000000001, 0xfffff80739589ee8). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5e71fa75-65e3-4be2-80f0-98d48d586e76.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000000000085a, 0x00000000000000ff, 0x0000000000000000, 0xfffff80450901203). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a9ef8cfe-61d7-4548-a971-2ddca277b127.
The memory.dmp file is almost a gig large. There are also a handful of minidumps in systemroot.
Some assorted information:
When googling the bug check error two days ago, I was referred to a forum where it was speculated that it could be a driver issue and a suggestion to run the driver verifier process. I ran driver verifier, selected all drivers and rebooted which began an infinite crash loop shortly after reboot (around the time startup programs initialized). I eventually got into safe mode, deleted the driver verifier settings and disabled all startup programs for good measure. I'm able to boot and use system again normally.
After one of these freezes about a month or two ago, I ran mdscheduler and it said there is a problem with your computer's memory. I then ran memtest86, twice, and it found no errors -- then booted into system, ran mdscheduler again and it found no issues.
Continue reading...
