I didn't attach the BSOD dump files after the the new keyboard/mouse. Will do so if you want.
My Computer
System One
-
- OS
- Windows 8
Your memory is underclocked, and perhaps set incorrectly in other ways.
Go into the bios settings, and see if you can set the RAM to run at 800 MHz instead of 776.
Set the timings to be 9-9-9-23 with 2T command rate - as opposed to not how it is at 11-11-11-28 with 2T.
--Alternatively--
Set Optimized Defaults in the bios and save - see if that sets the memory as I said or at least something different you can tell me about.
You might even update the bios to latest, for good measure, before doing either of the above.
Im about to rip my hair out. This is the most frustrating thing.
Im about to rip my hair out. This is the most frustrating thing.
heh heh I just had a power out in my neighborhood, and my message didn't get through because of it (complete with fire engine noises and all lol). So, I try again.
We've all been there and done that with things like this, and I assure you that participating in this thread is a great choice on your behalf.
2 things.
Razer device drivers are quite notorious, regardless of date or version.
I would physically detach the Razer, attach some generic device to replace it (for now only, just to test!) and reboot.
The other thing is, how did you get on with bios changes? Anything to report?
I did detach the razer devices and connected a wireless Microsoft mouse and a AZZA keyboard I got from an order awhile back. I didnt Reboot after that though so that could of been a problem. Should I reboot again even though the BSOD rebooted for me? I didnt physically remove the Razer drivers if that was necessary.Cool. Good info, thank you.
Like I was saying, test (in the method I described above!) - without Razer.
Then move on from there - if necessary.
"I would physically detach the Razer, attach some generic device to replace it (for now only, just to test!) and reboot."
Well I stepped away from pc for a little bit and I came back and I was at my Log in screen. I assumed I got a BSOD but there was no new mini dump file. Not sure what happened?
Well I stepped away from pc for a little bit and I came back and I was at my Log in screen. I assumed I got a BSOD but there was no new mini dump file. Not sure what happened?
Maybe the machine did not crash, but instead, it asked for a password because it was sleeping correctly and you're not acclimated to that.
lvrs64 lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64 lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8)