Okay so i made a topic a while ago about this BSOD i keep getting. It goes along the lines of:
A clock interrupt was not received by a secondary processor within the allocated time interval blah blah blah
Someone on these forums suggested i do a power drain by doing the following:
Remove A/C adapter, battery pack, and coin-cell battery under compartment, and holding down power button for 30 seconds.
I did all that. Turned my computer on, clock was all messed up and set to a strange date. I changed the time and date to normal, then i got the BSOD AGAIN, and now my clock and date keep changing to random times/dates all the time, no matter how many times i correct it.
Right now it says its June 19, 2017 at 1:41 am.
Help?
-
Change your time in the BIOS and then boot windows. Also make sure the RTC battery if firmly seated.
-
download "Bluescreenview" then tell us which driver exactly caused the error.
-
I am also experiencing this from yesterday when i did CMOS reset by battery removal (trying to fix freeze issue with Vertex 3). Have you managed to fixed this?
-
@ Freeze with Vertex 3: Did you apply the LPM fix?
-
just testing that cmos reset, maybe this will finally help.
regarding clock problem it looks like the cmos battery didnt fit properly (although it looked fine). realligned and seems to be working, will see after couple of restarts. will update if still experience the problem.
M17x R3, First BSOD, now Clock problems.
Discussion in 'Alienware 17 and M17x' started by Nordini, Aug 3, 2011.