Multiple BSOD erros. Random times.
- Thread starter JohnAbyss
- Start date
MasterChief
Banned
- Messages
- 1,883
MasterChief
Banned
- Messages
- 1,883
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.
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.
I tried changing it but it just stayed the same. For example it would be 11-11-11-28 but beside it would be 9-9-9-23(as I entered). Also setting it to defaults did not change anything.
MasterChief
Banned
- Messages
- 1,883
I would check on the motherboard manual, since it would be the best resource on how to make bios adjustments well.
You might have to set the bios to manual, somewhere above where you enter the numbers, or something like that.
Also, if the bios asked for a password and you did not enter one, or it was wrong, you might not have access to change anything.
You might have to set the bios to manual, somewhere above where you enter the numbers, or something like that.
Also, if the bios asked for a password and you did not enter one, or it was wrong, you might not have access to change anything.
MasterChief
Banned
- Messages
- 1,883
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 detached all razer devices. Nothing to report on the BIOS yet. Will be working on that extensively soon. Just got another BSOD. This one was kinda weird. My computer was sitting idle for about 45-50 minutes. Then as soon as I touched the mouse to move it BSOD. Im not sure if that is relevant but thought Id tell you. Heres the dump.
EDIT: I edited the first sentence. Forgot to mention I detached all Razer devices. The BSOD was after they were disconnected.
MasterChief
Banned
- Messages
- 1,883
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."
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."
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.
MasterChief
Banned
- Messages
- 1,883
Good, good. Look in the normal Programs uninstall list. If it shows anything Razer, remove it.
Keep us updated on any related events after.
Reboot for good measure, after removal.
Keep us updated on any related events after.
Reboot for good measure, after removal.
MasterChief
Banned
- Messages
- 1,883
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.
You can do two things.
1) Set your power plan to not ask for passwords when coming out of sleep or hibernation.
2) Use netplwiz to tell Windows not to ask for passwords.
I was only gone maybe 10 minutes. Also none of my windows that were open previously were open? Its probably nothing. Like I said I changed the memory settings in my BIOS. Will report back on further updates.
MasterChief
Banned
- Messages
- 1,883
Going by gut feeling, it still has to do with your RAM settings.
In the name of good practice, try to update Logitech camera drivers:
Product Support & Software Downloads: Webcams - Logitech
In the name of good practice, try to update Logitech camera drivers:
Code:
lvrs64 lvrs64.sys Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64 lvuvc64.sys Mon Oct 22 22:12:08 2012 (5085FCF8)Product Support & Software Downloads: Webcams - Logitech
