holdum333
Banned
- Joined
- Mar 27, 2016
- Messages
- 1,243
Trouble is Gary many motherboards now use solid caps but inspection of the motherboard is always worthwhile..
I upped the ram speed to 1.6 and it kept crashing consistently.Trouble is Gar/y many motherboards now use solid caps but inspection of the motherboard is always worthwhile..
Bawb if manually setting the RAM speed doesn't help you could try upping the voltage slightly. If your Vengence RAM runs at 2400MHz then it's voltage will be about 1.65v. Try upping it slightly but don't go over 1.7v. Failing that, do you have access to any other memory or would it be possible to perhaps borrow some off a friend?
Try something for me please, when you next reboot, expecting a bsod, boot straight into safe mode and see if the blue screen still occurs. If it does don't forget to send me the dump.
I also notice you use a Logitech Keyboard and possibly a XTD kone mouse? (I own an XTD Kone and they are an awesome mouse, anyway I digress) Bawb have you tried removing either the mouse or the keyboard and seeing if the bsod still occurs? It's a long shot I know but if you have a spare k'board and mouse see if swapping them over makes any difference.
Hmm...Really? That's not good. I assume that when you say '1.6' your referring to the RAM speed of 1600MHz and not the voltage of 1.6?I upped the ram speed to 1.6 and it kept crashing consistently.
I was talking about the voltage. They default to 1333? really? I always thought they were 1600 im so sure I looked it up multiple times as well. Well the only value that i have added manually is the voltage which 1.55 right now. And xmp is enabled but disabling xmp has not worked before.Hmm...Really? That's not good. I assume that when you say '1.6' your referring to the RAM speed of 1600MHz and not the voltage of 1.6?
Link Removed
I checked which RAM you have by looking at an old dump file. You'll notice in the link above that your sticks will default to 1333mhz @ 1.5v. They have also been tested to run at the rate of 1600MHz @ 1.5v and in order to achieve this speed you either use the X.M.P. profiles or manually overclock.
This is normal practice. Your motherboard manual will tell you how to correctly configure XMP.
Now if you tried to manually overclock the sticks to 1.6mhz or 1600mhz and they crashed constantly then that is not good at all and the sticks could well be faulty.
What about if you returned the sticks beck to the default speed of 1333mhz and then tried enabling the XMP profile. As I wrote above your manual will tell you how and if you haven't got one download another from the motherboard link in earlier posts.
Its most definitely not the power supply. As I mentioned before this has been happening for a long time and Ive swapped out parts of my PC over the course of this happening the only things that are the same since this started are the CPU, and motherboard.
I've dealt with cases far longer than this one and eventually found the solution so let's not panic just yet..Hi I probably will get hollered at, but this is post number 65. IMHO it's time for a new mother board or a new computer.
Yup. As I said earlier ALL RAM defaults to 1333mhz (unless it's slower than 1333mhz of course) and to achieve the speed the RAM has been tested to one has to enable the xmp or you can set the speed manually. Check the link I posted:They default to 1333? really? I always thought they were 1600 im so sure I looked it up multiple times as well.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffd000f2991320, 0, fffff801b10f2d67, 2}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruptionWhen you re-installed Windows were these clean installs or back up images or upgrade installs?
When you re-installed Windows were these clean installs or back up images or upgrade installs?
yea sorry for late response i guess? But yea they were clean installs. off of the disk, no files saved. alright ill clear the bios and then get back to you if it blue screens.Yup thanks Gary.
Bawb if you could post whether they were clean installs or not that would be great. There is a specific reason I'm asking this question so please let me know.
The op looked and couldn't find the files I mentioned. This can sometimes happen and probably means something is still in the registry which relates to the apps mentioned.Hi Guys! I just can't get this off my mind. MSE should not be showing up on your PC. Here's a old reply that is really bothering me and I'm wondering if this still exists! Here's a suggestion by @kemical that never really got answered! The last thing I read was that these could not be found. That doesn't sound right to me!
AsIO.sys Tue Aug 24 02:53:02 2010: Asus PCProbe Utility. This is too old for Windows 10 really and needs either removing or updating.
MpKsl89da5820.sys Wed May 20 02:50:37 2015: Microsoft Security essentials? If so please remove and just use the onboard Defender.
zamguard64.sys Mon Dec 14 10:13:23 2015: Anti Malware uninstall to test
Resting the BIOS did not fix the blue screen. Added the dump filesYup, thanks Gary.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffd000aa4a0d49, 0, fffff801e7eb6dca, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption