Jump to content

Question about memory voltage

Guest
By Guest
in CPUs, Motherboards, and Memory
 Share
Posted

So I reset my bios settings to default due to me having IRQL_Driver_Less_Or_Equal crashes or whatever only in fallout 4. One of the reasons that BSOD happens is because of memory. After seeing he memory was fine I did a bios default and it worked fine. So I've just reappliled my overclock and I added 00.25 voltage to my cpu. I also reenabled xmp which is 2666mhz ddr4. The weird part is teh default voltage on the motherboard  is like 1.35 or around that which I found weird considering the default ddr4 voltage is actally 1.2. So the xmp made the voltage 1.2. 

 

Edit: So do you think it's teh memory that's teh problem? I guess I'l find out. 

Link to comment
https://linustechtips.com/topic/508953-question-about-memory-voltage/
Share on other sites
Link to post
Share on other sites
Posted

Stop saying teh, it's the.

 

Please.

lol, I read this and that was the first thing I thought.

Sergeant, United States Marine Corps

Network Administrator, Comptia A+, Security+, Cisco Certified Networking Associate

From a G3258 to dual Xeon E5-2670's

Link to post
Share on other sites
Posted

So I reset my bios settings to default due to me having IRQL_Driver_Less_Or_Equal crashes or whatever only in fallout 4. One of the reasons that BSOD happens is because of memory. After seeing he memory was fine I did a bios default and it worked fine. So I've just reappliled my overclock and I added 00.25 voltage to my cpu. I also reenabled xmp which is 2666mhz ddr4. The weird part is teh default voltage on the motherboard  is like 1.35 or around that which I found weird considering the default ddr4 voltage is actally 1.2. So the xmp made the voltage 1.2. 

 

Edit: So do you think it's teh memory that's teh problem? I guess I'l find out. 

 

Download BlueScreenView and see what executable file caused the BSOD. If it is Fallout's executable file or the physics engine associated with running Fallout, then it's probably a driver issue. If you had memory problems I think windows just impromptu freezes, no BSOD.

 

According to Microsoft, the IRQL_Driver_Less_Or_Equal error means that a program tried to access memory that doesn't belong to it (In english, basically Tim decided to view Bob's Whatsapp, but Bob realised and knocked Tim out).

 

 

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access.

...

This error usually occurs after the installation of a buggy device driver, system service, or BIOS.

 

https://msdn.microsoft.com/en-us/library/ms854226.aspx

 

 

I'd also recommend running Memtest after overclocking your RAM or changing voltages, to test system memory stability.

Speedtests

WiFi - 7ms, 22Mb down, 10Mb up

Ethernet - 6ms, 47.5Mb down, 9.7Mb up

 

Rigs

Spoiler

 Type            Desktop

 OS              Windows 10 Pro

 CPU             i5-4430S

 RAM             8GB CORSAIR XMS3 (2x4gb)

 Cooler          LC Power LC-CC-97 65W

 Motherboard     ASUS H81M-PLUS

 GPU             GeForce GTX 1060

 Storage         120GB Sandisk SSD (boot), 750GB Seagate 2.5" (storage), 500GB Seagate 2.5" SSHD (cache)

 

Spoiler

Type            Server

OS              Ubuntu 14.04 LTS

CPU             Core 2 Duo E6320

RAM             2GB Non-ECC

Motherboard     ASUS P5VD2-MX SE

Storage         RAID 1: 250GB WD Blue and Seagate Barracuda

Uses            Webserver, NAS, Mediaserver, Database Server

 

Quotes of Fame

On 8/27/2015 at 10:09 AM, Drixen said:

Linus is light years ahead a lot of other YouTubers, he isn't just an average YouTuber.. he's legitimately, legit.

On 10/11/2015 at 11:36 AM, Geralt said:

When something is worth doing, it's worth overdoing.

On 6/22/2016 at 10:05 AM, trag1c said:

It's completely blown out of proportion. Also if you're the least bit worried about data gathering then you should go live in a cave a 1000Km from the nearest establishment simply because every device and every entity gathers information these days. In the current era privacy is just fallacy and nothing more.

 

Link to post
Share on other sites
Posted

lol, I read this and that was the first thing I thought.

 

 

Stop saying teh, it's the.

 

Please.

 

And for the memory, I think you should look into other reasons, because if it was a driver crash then it's not the memory.

Heh, it's not really intentional, but yeah. Also it's not a driver as it was fine once the overclock was reset 

Link to post
Share on other sites
Posted

Heh, it's not really intentional, but yeah. Also it's not a driver as it was fine once the overclock was reset 

I think it's the board trying to overvolt the memory then, may be a feature for overclocking. I would just leave it at what you have to make it stable then.

Link to post
Share on other sites
Posted

I don't think teh memory is teh problem B)

                                                                                                                                                                            Professional Girl

Link to post
Share on other sites
Posted

Download BlueScreenView and see what executable file caused the BSOD. If it is Fallout's executable file or the physics engine associated with running Fallout, then it's probably a driver issue. If you had memory problems I think windows just impromptu freezes, no BSOD.

 

According to Microsoft, the IRQL_Driver_Less_Or_Equal error means that a program tried to access memory that doesn't belong to it (In english, basically Bob decided to view Tim's Whatsapp, but Bob realised and knocked Tim out).

 

 

https://msdn.microsoft.com/en-us/library/ms854226.aspx

 

Download BlueScreenView and see what executable file caused the BSOD. If it is Fallout's executable file or the physics engine associated with running Fallout, then it's probably a driver issue. If you had memory problems I think windows just impromptu freezes, no BSOD.

 

According to Microsoft, the IRQL_Driver_Less_Or_Equal error means that a program tried to access memory that doesn't belong to it (In english, basically Bob decided to view Tim's Whatsapp, but Bob realised and knocked Tim out).

 

 

https://msdn.microsoft.com/en-us/library/ms854226.aspx

I have and yes it was due to a driver which i forget it's name. It's weird though because once I reset the overclock it was gone. It never happened until after I did the overclock and updated windwos 10 pro. 

Link to post
Share on other sites
Posted

I think it's the board trying to overvolt the memory then, may be a feature for overclocking. I would just leave it at what you have to make it stable then.

No, it was at that for the default setting until I got xmp which make it lower. I think the crashing is due to the memory not getting enough voltage. 

Link to post
Share on other sites
Posted

No, it was at that for the default setting until I got xmp which make it lower. I think the crashing is due to the memory not getting enough voltage. 

Oh then that means your memory just can't take the speeds. Just leave XMP on, it's better to have it on anyways.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing CPUs, Motherboards, and Memory

×