ASUS X99-A

[Feverfew]

I have a new build (built in April) that has been having a constant problem since its inception and I really cant figure out a way to solve it. 

My build is the following:

 

I would like to note that none of my parts are overclocked!!

 

CPU: Intel i7-5820K 3.3 ghz 

RAM: 8GB Crucial

GPU: Palit Jetstream 780 (Nvidia)

Motherboard: ASUS X99-A

Hard Drive #1: (I think) Kingston 120gb

Hard Drive #2: Western Digital 2TB

PSU: Aerocool X-Strike 1100w

OS: Windows 8.1

 

Temps for my components are between 25-35 so overheating is not the problem. 

 

The freezing happens randomly. However as time has gone on I have noticed they happen around mostly during bootup of windows (this is after it has passed the POST.).

 

For example, I may find it freeze after post and the screen goes black. Thus I reset the computer . In some cases it may freeze repeatedly during the loading of windows causing several resets in a couple of minutes. There is no BSOD and I have to reset, the freezing does not stop, as I've left it an hour while freezing and it wouldn't come back.

 

Interesting notes:

1) The event viewer logs every time I reset/restart the computer due to a freeze (it does not record the moment the computer freezes, only once I act upon it). this leads to the following error in Event Viewer:

 

Critical 26/08/2015 17:54:47 Kernel-Power 41 (63)

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Warning 26/08/2015 17:54:48 Kernel-PnP 219 (212)

The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.

 

Error 26/08/2015 17:55:01 Service Control Manager 7034 None

The Service KMSELDI service terminated unexpectedly.  It has done this 1 time(s).#

 

2) Sometimes I may get a message that states that overclocking has failed (although I haven't overclocked). I then have to go in the BIOS and reset to defaults (even though nothing has changed.

 

3) I once got an error (and only once) that anti-surge protection detected a surge and so stopped going past boot (this was after I had reset my pc after a freeze).

 

4) The computer thinks that I have 2 keyboards ( this is seen when I get the overclocking error).

 

5) I once tried to force a crash to see what was causing it and the computer placed the blame on a file called IOMap64.sys.

 

 

I've done several things to try and solve this, and none of them have worked. I will list them (not in the order that I did them):

 

Re-install windows 8.1 several times.

 

Update BIOS to 1801. (the newest one).

 

Turn off Anti-Surge Support: 

 

Turn off Fast Boot.

 

Remove Ai Suite 3 (apparently it contains IOMap64.sys).

 

 

Turnj

[Sauron]

I think it might be the ram. Try running a memtest or 5. Or it could be a defective motherboard.

[PineappleHolidays]

Try the memory

 

also, 8gb ram on X99 ?!? blasphemy

 

if there are any cpu power savings options in the bios, I would try those too

[0x1e]

 

 

I would like to note that none of my parts are overclocked!!

 

CPU: Intel i7-5820K 3.3 ghz 

RAM: 8GB Crucial

GPU: Palit Jetstream 780 (Nvidia)

Motherboard: ASUS X99-A

Hard Drive #1: (I think) Kingston 120gb

Hard Drive #2: Western Digital 2TB

PSU: Aerocool X-Strike 1100w

OS: Windows 8.1

 

Temps for my components are between 25-35 so overheating is not the problem. 

 

Warning 26/08/2015 17:54:48 Kernel-PnP 219 (212)

The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.

 

Error 26/08/2015 17:55:01 Service Control Manager 7034 None

The Service KMSELDI service terminated unexpectedly.  It has done this 1 time(s).#

 

2) Sometimes I may get a message that states that overclocking has failed (although I haven't overclocked). I then have to go in the BIOS and reset to defaults (even though nothing has changed.

 

5) I once tried to force a crash to see what was causing it and the computer placed the blame on a file called IOMap64.sys.

 

 

I've done several things to try and solve this, and none of them have worked. I will list them (not in the order that I did them):

 

Re-install windows 8.1 several times.

 

Update BIOS to 1801. (the newest one).

 

Turn off Anti-Surge Support: 

 

Turn off Fast Boot.

 

Remove Ai Suite 3 (apparently it contains IOMap64.sys).

 

 

Turnj

 

I would think it's the ram. Programs that crash and have no connection to each other could be because of faulty ram, or over clocking.

You said you're not over clocking. What speed do you have the ram at, and at what timings? Have the timings too low can be classed as over clocking. Also having the ram too high again is over clocking. For instance my CPU only officially supports 1600Mhz but I have 1866 as that's the speed of the ram, but that's still over clocking as I'm forcing the IMC to ran faster than it's stated.

[Feverfew]

I would think it's the ram. Programs that crash and have no connection to each other could be because of faulty ram, or over clocking.

You said you're not over clocking. What speed do you have the ram at, and at what timings? Have the timings too low can be classed as over clocking. Also having the ram too high again is over clocking. For instance my CPU only officially supports 1600Mhz but I have 1866 as that's the speed of the ram, but that's still over clocking as I'm forcing the IMC to ran faster than it's stated.

Well I've just stumbled open something very weird. I remember that my DRAM frequency should be 2400MHZ ( or something in the 2000's) but for some reason its 1199 (According to speccy). The standard is 1333 so I dont know how it managed to get set to 1199. Am I even talking about the same thing as you are or am I confusing it with something else.

 

Ai suite tells me that the maximum bandwidth is 2400. So tomorrow morning I'll go check see wtf is going on and try to reset it to default via BIOS (I haven't manually changed any RAM settings myself), I will also try memtest tomorrow as another user suggested.

 

I remember when I built the PC I had a memory intitalization error when I tried to put the RAM in the recommended DIMM slot (there are 8). I just chose to move the RAM to the first (counting from the left) dimm slot and that solved it. Should I try to move it back to what the motherboard manual recommends?

[0x1e]

Well I've just stumbled open something very weird. I remember that my DRAM frequency should be 2400MHZ ( or something in the 2000's) but for some reason its 1199 (According to speccy). The standard is 1333 so I dont know how it managed to get set to 1199. Am I even talking about the same thing as you are or am I confusing it with something else.

 

Ai suite tells me that the maximum bandwidth is 2400. So tomorrow morning I'll go check see wtf is going on and try to reset it to default via BIOS (I haven't manually changed any RAM settings myself), I will also try memtest tomorrow as another user suggested.

 

I remember when I built the PC I had a memory intitalization error when I tried to put the RAM in the recommended DIMM slot (there are 8). I just chose to move the RAM to the first (counting from the left) dimm slot and that solved it. Should I try to move it back to what the motherboard manual recommends?

I'm guessing you're looking at CPU-Z or some program like that. They don't take into account the Double part in DDR. So 1199(1200) will be 2400.

Find you max rated memory speed supported by your CPU. It's DDR4 I believe so it would be 2133Mhz. Run it at that speed just to see what happens. Manually set it and then manually set the ram timings. You could simply have a dud IMC.

[Feverfew]

I'm guessing you're looking at CPU-Z or some program like that. They don't take into account the Double part in DDR. So 1199(1200) will be 2400.

Find you max rated memory speed supported by your CPU. It's DDR4 I believe so it would be 2133Mhz. Run it at that speed just to see what happens. Manually set it and then manually set the ram timings. You could simply have a dud IMC.

Wow. Well I found out that my CPU only supports DDR4 to 2133 MHz. So I went into the BIOS and changed it from 2400MHz to 2133MHz and so far have not had any freezes!! Hopefully it stays that way and if it doesn't then I will probably have to Memtest the RAM. How come the RAM timing caused such a problem?

 

I'd like to thank everyone in this thread who posted for helping me solve this long lasting problem.

[0x1e]

Wow. Well I found out that my CPU only supports DDR4 to 2133 MHz. So I went into the BIOS and changed it from 2400MHz to 2133MHz and so far have not had any freezes!! Hopefully it stays that way and if it doesn't then I will probably have to Memtest the RAM. How come the RAM timing caused such a problem?

 

I'd like to thank everyone in this thread who posted for helping me solve this long lasting problem.

Many years ago (not too many though) the integrated memory controller was apart of the North Bridge. This meant motherboard manufacturers had control over their quality and what type it was. This would normally mean, the higher end motherboards that you spent a lot of money on would normally have better quality chips, including a better north bridge = better and faster memory support. This led to far better memory over clocking (if the memory itself could handle it).

Now though the north bridge is all inside the CPU and has no type of quality binning. It either works or it doesn't. It only gets tested for one speed (in your case it's 2133Mhz).

However there are many that can do far more, like 3333Mhz, but not all. So yes you can buy memory that fast, but it will only go as fast as what the IMC will allow.

You can always add more voltage to the IMC and see if it works, but from my experience it's very hit and miss. Most of the time if it doesn't work then it simply doesn't work.

 

Unlike ECC ram, if the timings and speed is incorrect then it can cause so many problems that it's not even funny. One problem can cause another and eventually Windows will just goes "fuck this shit" and throws everything out of the window by showing a BSOD or hard crash altogether.

It can also be difficult to diagnose, especially if you truly believe that you've set your bios up correctly. On top of that because it's a shared resource (everything uses RAM) anything can go wrong, so Windows could be showing errors with so many programs but in actual fact there's only one problem, your ram.