New
#31
OK everything should be up to date now. I guess now I wait to see if I get more BSODs?
OK everything should be up to date now. I guess now I wait to see if I get more BSODs?
Yep.
I can't analyse anything until the 29th, that is the day I come home, but I don't know when I am home so you may expect an analyse the 30th.
So I've still been getting some BSODs and I've been keeping track of when they are happening and it seems like they always occur when I try to load a new window/tab in google chrome. I don't know if that points to something but I do know each chrome tab is a new process. They seem to be memory related too. I find that strange since I'm able to play very taxing video games that use up a lot of RAM with no problems. If it doesn't say in the logs my version of Chrome is 47.0.2526.106 m which it says is the latest.
Here is the DM Log from my computer: Attachment 58109
Thanks!
Please try disabling hardware acceleration if it is turned on
In the right upper corner click on Attachment 58148
In the menu choose 'settings'
In the settings scroll down and click 'Show advanced settings'
Scroll all the way down to the bottom.
Under the part 'System' you can find 'Use hardware acceleration when available'
If it is checked, uncheck it
Hardware acceleration uses the hardware to execute functionality faster then with software.
I suspect this may be a problem if it is enabled.
I went ahead and disabled hardware acceleration and have still been getting BSODs. I just experienced a new one (Critical Structure Corruption). I've also noticed that the windows interface, like the Start Menu and things like Task Manager have been freezing up. When this happens I can interact with the program I'm currently using but can't alt-tab or use the start menu. The problem goes away after a minute at most.
Here is the newest DM Log Collector: Attachment 60169
Any ideas? Is this sounding like a hardware issue?
Thanks
I did temporarily change my date to 10/31 so I could play a Halloween event in a game so that may have something to do with it. Now that I think of it, when I was getting set up for that my PC did BSOD, but then again it's still not listing the correct date/time for the minidump from last night. It looks like the other files in the zip have the correct times.
The date and time has been correct according to windows (on the bottom right of the screen). Is there a chance I just need to update it elsewhere as well?
Changing the system time to the future or the past isn't good for several reasons including security reasons.
I don't think so.
Could the CMOS battery have been causing these problems all along or do you think there may be another issue too?
No, the CMOS battery was just a thought because of the time from the dumps but I didn't knew you had changed it.