BSOD SYSTEM_SERVICE_EXCEPTION 0x0000003B

[JustRelaxASC]

First of all, hello everyone
So in the past 2 months I've been having some serious(?) issues with my PC, I've been posting to whole bunch of different forums and yet, no one could help me.
This was like a month ago, everyone was saying it was bad RAM and stuff so I changed out my RAM, Graphics Card, and my PSU, hoping it will fix stuff.. but no.
Here I am still having issues,
My PC was taken to service and they couldn't fix it either... (I mean they were telling me it's fixed, but obviously it isn't)
So now my PC often (every day, once or few times) gets BSODs and sometimes just randomly restarts without any warning (BSOD, or any kind of message), it sometimes just freezes and there is nothing I can do but restart it on button, it happens when im playing games and then there is some noise (I suppose it's a continuous loop of the last sound that was playing before it freezed) and sometimes it just freezes while it's in idle and no one is using it, so when I come back I just see I can't move my mouse and then I restart it. It also happens when I am sometimes listening music on YouTube.. (so the anoying noise is there aswell)
The new RAM is tested with memtest86 and some other memory testing tool for 24h and it came up with no errors. The clean install of Windows has been done a few times and problems persisted.
Some times it BSODs and fails to dump it so I can not see it in Minidump folder.
The BSOD that happens most often is SYSTEM_SERVICE_EXCEPTION 0x0000003B, and then there is 0x0000007E with nothing above (the place where it should say something like SYSTEM_SERVICE_EXCEPTION), I got that BSOD captured with my phone but it didn't dump the crash so.. yeah, and then there is 0x0000001E also not dumped and with nothing above.

==================================================
Dump File : 082314-20295-01.dmp
Crash Time : 23.8.2014 20:59:40
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02caecd1
Parameter 3 : fffff880`0b472170
Parameter 4 : 00000000`00000000
Caused By Driver : Unknown_Module_00000000`00000000
Caused By Address : Unknown_Module_00000000`00000000+2fe692
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082314-20295-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262.144
Dump File Time : 23.8.2014 21:00:50
==================================================

==================================================
Dump File : 082314-16738-01.dmp
Crash Time : 23.8.2014 20:47:28
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02c71445
Parameter 3 : fffff880`08bcb060
Parameter 4 : 00000000`00000000
Caused By Driver : Unknown_Module_00000000`0000008e
Caused By Address : Unknown_Module_00000000`0000008e+1f8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+74540
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082314-16738-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262.144
Dump File Time : 23.8.2014 20:48:55
==================================================

==================================================
Dump File : 082214-15334-01.dmp
Crash Time : 22.8.2014 18:32:10
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d346aa
Parameter 3 : fffff880`09a9f980
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74540
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.22616 (win7sp1_ldr.140303-2307)
Processor : x64
Crash Address : ntoskrnl.exe+74540
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082214-15334-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276.064
Dump File Time : 22.8.2014 18:32:56
==================================================

==================================================
Dump File : 082114-15132-01.dmp
Crash Time : 21.8.2014 14:15:57
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02c78865
Parameter 3 : fffff880`083b3f20
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74540
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.22616 (win7sp1_ldr.140303-2307)
Processor : x64
Crash Address : ntoskrnl.exe+74540
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082114-15132-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274.672
Dump File Time : 21.8.2014 14:16:56
==================================================

 

[johnbl]

0x0000007B = INACCESSIBLE_BOOT_DEVICE

Look for a problem in your disk subsystem.
ie update BIOS, change/reconnect your cables to your disk driver. If you have a solid state driver, boot to BIOS and let the system go idle to let the internal garbage collection and trim functions clean up the drive (they should start after 5 minutes of idle) maybe look for a firmware update if you have a SSD.

Make sure your drive is on a primary chip sata port, enable hotswap in the BIOS if you have that option. Update the CPU chipset drivers directly from the CPU manufactures website.

your other bugcheck 0x3b SYSTEM_SERVICE_EXCEPTION is harder to tell what the issue it. You really need to post a copy of one of your current memory .dmp files if you have one. If you don't you have a failure in your disk subsystem and it could not be written. (enable hotswap in BIOS to attempt to work around the failure or add a second drive and make the memory .dmp file be save on the second drive so you can post it on a cloud server.)
- the error is common with memory corruption caused by incorrect RAM settings and by having a device driver that is corrupting the memory structures of other device drivers. provide memory .dmp and I can point out common device drivers that could be suspect. If it is not clear as to what device driver causes the corruption you can use verifier.exe to test the third party drivers and have windows bugcheck when they attempt to corrupt shared memory. When this happens the bad driver will be named in the bugcheck.

 

[JustRelaxASC]

0x0000007B = INACCESSIBLE_BOOT_DEVICE

Look for a problem in your disk subsystem.
ie update BIOS, change/reconnect your cables to your disk driver. If you have a solid state driver, boot to BIOS and let the system go idle to let the internal garbage collection and trim functions clean up the drive (they should start after 5 minutes of idle) maybe look for a firmware update if you have a SSD.

Make sure your drive is on a primary chip sata port, enable hotswap in the BIOS if you have that option. Update the CPU chipset drivers directly from the CPU manufactures website.

your other bugcheck 0x3b SYSTEM_SERVICE_EXCEPTION is harder to tell what the issue it. You really need to post a copy of one of your current memory .dmp files if you have one. If you don't you have a failure in your disk subsystem and it could not be written. (enable hotswap in BIOS to attempt to work around the failure or add a second drive and make the memory .dmp file be save on the second drive so you can post it on a cloud server.)
- the error is common with memory corruption caused by incorrect RAM settings and by having a device driver that is corrupting the memory structures of other device drivers. provide memory .dmp and I can point out common device drivers that could be suspect. If it is not clear as to what device driver causes the corruption you can use verifier.exe to test the third party drivers and have windows bugcheck when they attempt to corrupt shared memory. When this happens the bad driver will be named in the bugcheck.

Here are the dumps.
If I understood you correctly you requested that ^
I do not have SSD
What is disk subsystem?
One thing I noticed (idk if that is causing problems but may be idk) is that my RAM is CL9 and in bios its showing 11-11-11-28, I don't know if thats normal or not, and one more thing is that my RAM sticks (HyperXBeasts, they are huge) can't fit in first 2 slots because of huge Cooler for my CPU so now they are in second 2 slots, also could be a reason idk, and the last thing I think may be are not correct voltages for RAM maybe? Because I was reading on some forums and there were some people having kind of same problem as I do and chaning Voltages helped them, but that's the last thing we are going to try I suppose, bcs its not something to mess with.
And I also noticed in the back of my PC, where the PSU Is located there is some sound like electricity popping, or something really small vibrating, I don't know if thats normal or not.
And here is my machine:

 

[Vic 40]

0x0000007B = INACCESSIBLE_BOOT_DEVICE

.

It's 0x0000003b which says "SYSTEM_SERVICE_EXCEPTION".

Maybe that this will work?
http://support.microsoft.com/kb/980932/en-us
it contains a hotfix.

You could give some system info if this doesn't work,

Download the next program,
http://www.hwinfo.com/download32.html
open it,click run,close the top window which is the system summary,click save report at the left top,in the next window at the bottom check=dot "short text report" after that next,you'll get to see what is in your pc,copy that by clicking "copy to clipboard" and right click and paste in you next post.

 

[johnbl]

082114-15132-01.dmp
BugCheck 3B, {c0000005, fffff80002c78865, fffff880083b3f20, 0}
SYSTEM_SERVICE_EXCEPTION (3b)

focus on running a malwarebytes scan
and remove 4.exe loaded as a driver (listed as a trojan)
run cmd.exe as a admin
sfc.exe /scannow (will attempt to fix corrupted windows files)

===============

looking at your memory dump file.
you have some issues with viruses/Trojans
here is a list of your loaded drivers that you might want to remove:
4 4.exe unavailable (00000000)
ffff880`079dd000 fffff880`079f7d00 Unknown_Module_fffff880_079dd000 Unknown_Module_fffff880`079dd000 Fri Jul 12 03:40:58 2013 (51DFDD3A)
fffff880`08992000 fffff880`089e5000 Unknown_Module_fffff880_08992000 Unknown_Module_fffff880`08992000 unavailable (00000000)
fffff880`089e5000 fffff880`089f8000 Unknown_Module_fffff880_089e5000 Unknown_Module_fffff880`089e5000 Thu Oct 18 11:52:27 2012 (50804FEB)
fffff960`00640000 fffff960`00667000 Unknown_Module_fffff960_00640000 Unknown_Module_fffff960`00640000 Thu Feb 03 03:25:25 2011 (4D4A90A5)


you might also want to look at your samsung printer driver
C:\Windows\system32\Drivers\SSPORT.sys Thu Aug 11 16:07:32 2005

and confirm you want this driver loaded: RemoveAAM.bin unavailable (00000000)

 

[johnbl]

remove drivers listed below and retest to see if you still get corruption/bugcheck
====
looked at the other 3 bugcheck memory dump files, two were corrupted and not of much use. the last one does not show the problems of the others. on this dump file I would just suggest removing potential causes of memory corruption caused by drivers:

082214-15334-01.dmp
System Uptime: 0 days 0:00:34.741

remove your 2005 samsung printer driver
\??\C:\Windows\system32\Drivers\SSPORT.sys Thu Aug 11 16:07:32 2005
remove your 2011 eamonm.sys driver and your entire
ESET Smart Security softweare.

 

[JustRelaxASC]

First of all, sorry for the late(?) answer, but for some reason I wasn't able to see any replies to this thread after my last post.

0x0000007B = INACCESSIBLE_BOOT_DEVICE

.

It's 0x0000003b which says "SYSTEM_SERVICE_EXCEPTION".

Maybe that this will work?
http://support.microsoft.com/kb/980932/en-us
it contains a hotfix.

You could give some system info if this doesn't work,

Download the next program,
http://www.hwinfo.com/download32.html
open it,click run,close the top window which is the system summary,click save report at the left top,in the next window at the bottom check=dot "short text report" after that next,you'll get to see what is in your pc,copy that by clicking "copy to clipboard" and right click and paste in you next post.

I already tried the Hotfix, It didn't work.
I can't find what you are requesting me to in the hw software, when I run it I get this: http://prntscr.com/4h3cnn what should I check?

082114-15132-01.dmp
BugCheck 3B, {c0000005, fffff80002c78865, fffff880083b3f20, 0}
SYSTEM_SERVICE_EXCEPTION (3b)

focus on running a malwarebytes scan
and remove 4.exe loaded as a driver (listed as a trojan)
run cmd.exe as a admin
sfc.exe /scannow (will attempt to fix corrupted windows files)

===============

looking at your memory dump file.
you have some issues with viruses/Trojans
here is a list of your loaded drivers that you might want to remove:
4 4.exe unavailable (00000000)
ffff880`079dd000 fffff880`079f7d00 Unknown_Module_fffff880_079dd000 Unknown_Module_fffff880`079dd000 Fri Jul 12 03:40:58 2013 (51DFDD3A)
fffff880`08992000 fffff880`089e5000 Unknown_Module_fffff880_08992000 Unknown_Module_fffff880`08992000 unavailable (00000000)
fffff880`089e5000 fffff880`089f8000 Unknown_Module_fffff880_089e5000 Unknown_Module_fffff880`089e5000 Thu Oct 18 11:52:27 2012 (50804FEB)
fffff960`00640000 fffff960`00667000 Unknown_Module_fffff960_00640000 Unknown_Module_fffff960`00640000 Thu Feb 03 03:25:25 2011 (4D4A90A5)


you might also want to look at your samsung printer driver
C:\Windows\system32\Drivers\SSPORT.sys Thu Aug 11 16:07:32 2005

and confirm you want this driver loaded: RemoveAAM.bin unavailable (00000000)

I already ran MBAM and it came up with no viruses
How can I remove 4.exe driver (trojan)? Where can I find it?
I already ran sfc /scannow and came up with everything right
How do I remove those drivers? I scanned my system with mbam hitmanpro and eset and they all showed no viruses.
I have no idea what RemoveAAM.bin is.

remove drivers listed below and retest to see if you still get corruption/bugcheck
====
looked at the other 3 bugcheck memory dump files, two were corrupted and not of much use. the last one does not show the problems of the others. on this dump file I would just suggest removing potential causes of memory corruption caused by drivers:

082214-15334-01.dmp
System Uptime: 0 days 0:00:34.741

remove your 2005 samsung printer driver
\??\C:\Windows\system32\Drivers\SSPORT.sys Thu Aug 11 16:07:32 2005
remove your 2011 eamonm.sys driver and your entire
ESET Smart Security softweare.

I will remove ESET tho I don't think it will fix anything
Maybe this thread will help since I do not want to write everything again from there so you can just read through if you want: http://goo.gl/2iatYc

 

[Vic 40]

I got what i wnted from your other thread regarding what's in your pc.That's what i was after,but still for further use,
In this,
http://prntscr.com/4h3cnn
click run,
two windows will open close the top window which is the system summary,
click "save report" at the left top
in the next window at the bottom you mark "short text report"
after that next,
a new window will open in which you'll get to see what is in your pc,
copy that by clicking "copy to clipboard" and right click and paste in you next post.



I,as someone there,think it's about the ram too,maybe just an incompatbility between old and new=motherboard/CPU and ram.You could try with taking the ram voltage to 1.55V to see if that gives stability .

 

[JustRelaxASC]

I got what i wnted from your other thread regarding what's in your pc.That's what i was after,but still for further use,
In this,
http://prntscr.com/4h3cnn
click run,
two windows will open close the top window which is the system summary,
click "save report" at the left top
in the next window at the bottom you mark "short text report"
after that next,
a new window will open in which you'll get to see what is in your pc,
copy that by clicking "copy to clipboard" and right click and paste in you next post.

I,as someone there,think it's about the ram too,maybe just an incompatbility between old and new=motherboard/CPU and ram.You could try with taking the ram voltage to 1.55V to see if that gives stability.

Computer: GIGABYTE GA-MA770T-UD3P
CPU: AMD Phenom II X4 955 Black Edition (Deneb, RB-C3 (Ridgeback))
3200 MHz (16.00x200.0) @ 803 MHz (4.00x200.9)
Motherboard: GIGABYTE GA-MA770T-UD3P
Chipset: AMD 770/870 (RX780) + SB750/SB710
Memory: 8192 MBytes @ 803 MHz, 11.0-11-11-28
- 4096 MB PC14900 DDR3 SDRAM - Kingston KHX1866C9D3/4GX
- 4096 MB PC14900 DDR3 SDRAM - Kingston KHX1866C9D3/4GX
Graphics: MSI R9 270X (MS-V303)
ATI/AMD Radeon R9 270X, 2048 MB GDDR5 SDRAM
Drive: ST3500418AS, 488.4 GB, Serial ATA 3Gb/s
Drive: Optiarc DVD RW AD-5240S, DVD+R DL
Sound: ATI/AMD SB600 - High Definition Audio Controller
Sound: ATI/AMD Verde/Heathrow/Chelsea - High Definition Audio Controller
Network: RealTek Semiconductor RTL8168C/8111C PCI-E Gigabit Ethernet Adapter
OS: Microsoft Windows 7 Ultimate (x64) Build 7601


I'll try that with voltages later after we make sure that nothing else could be causing problems since I've read that changing voltages is not something to mess with.
I also noticed in BIOS RAMs are set up to 11-11-11-28 and they are CL9 and on some site I read for them is 9-11-9-24 I think.

New BSOD (tho I think it's corrupted (failed to dump)):
==================================================
Dump File : 082814-33867-01.dmp
Crash Time : 28.8.2014 15:22:37
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`00ba0690
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082814-33867-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262.144
Dump File Time : 28.8.2014 15:25:50
==================================================

 

[johnbl]

the bugcheck parameter 1 indicates that a driver was using a memory address that it could not access.
it can be:
-memory corruption cause by bad RAM or ram settings (overclocking)
- device driver that has bugs (releases a address but then attempts to use it again)
- device driver but that overwrites another device drivers memory (pretty common problem)
- malware that attempts to get into the system (pretty common)

If you system passes memtest86, and you have done a malwarebytes scan, do not have overclocking, have updated your device drivers, uninstalled questionable drivers then you are left with running verifier.exe and turning on some global flags to do extra error checking on your device drivers. Google on how to set up verifier and run it.

if verifier finds a device driver that is making a mistake it will call a bugcheck and name the device driver. At least you will know the cause of the failure.

 

[JustRelaxASC]

the bugcheck parameter 1 indicates that a driver was using a memory address that it could not access.
it can be:
-memory corruption cause by bad RAM or ram settings (overclocking)
- device driver that has bugs (releases a address but then attempts to use it again)
- device driver but that overwrites another device drivers memory (pretty common problem)
- malware that attempts to get into the system (pretty common)

If you system passes memtest86, and you have done a malwarebytes scan, do not have overclocking, have updated your device drivers, uninstalled questionable drivers then you are left with running verifier.exe and turning on some global flags to do extra error checking on your device drivers. Google on how to set up verifier and run it.

if verifier finds a device driver that is making a mistake it will call a bugcheck and name the device driver. At least you will know the cause of the failure.

I already asked:
"How can I remove 4.exe driver (trojan)? Where can I find it?
How do I remove those drivers?
I have no idea what RemoveAAM.bin is."

 

[johnbl]

I don't know. It showed up on one of your memory dump files but not in the others.
I would scan my drive for 4.exe and see if I could find it

same with the .bin file. it was listed as a adobe file

you had a pretty weird memory dump and I think the others were corrupted.
I don't know why.

the bugcheck parameter 1 indicates that a driver was using a memory address that it could not access.
it can be:
-memory corruption cause by bad RAM or ram settings (overclocking)
- device driver that has bugs (releases a address but then attempts to use it again)
- device driver but that overwrites another device drivers memory (pretty common problem)
- malware that attempts to get into the system (pretty common)

If you system passes memtest86, and you have done a malwarebytes scan, do not have overclocking, have updated your device drivers, uninstalled questionable drivers then you are left with running verifier.exe and turning on some global flags to do extra error checking on your device drivers. Google on how to set up verifier and run it.

if verifier finds a device driver that is making a mistake it will call a bugcheck and name the device driver. At least you will know the cause of the failure.

I already asked:
"How can I remove 4.exe driver (trojan)? Where can I find it?
How do I remove those drivers?
I have no idea what RemoveAAM.bin is."

 

[Vic 40]

Your ram is running at ~1600mhz (=803x2) ,i would bring that down to 1333 2=667) to see if that will do any good.
For the right latency's,

• JEDEC: DDR3-1333 CL9-9-9 @1.5V (This for what i recommend now.)
• XMP Profile #2: D3-1600 CL9-9-9 @1.65V
• XMP Profile #1: D3-1866 CL9-11-9 @1.65V

These do depend on the speed the ram runs on.

 

[JustRelaxASC]

Your ram is running at ~1600mhz (=803x2) ,i would bring that down to 1333 2=667) to see if that will do any good.
For the right latency's,

• JEDEC: DDR3-1333 CL9-9-9 @1.5V (This for what i recommend now.)
• XMP Profile #2: D3-1600 CL9-9-9 @1.65V
• XMP Profile #1: D3-1866 CL9-11-9 @1.65V

These do depend on the speed the ram runs on.

Can I take a pic of my RAM settings in BIOS and u tell me what to change? Because when I try to change voltages to 1.5V I can not because the current voltage that rams are running on are min, so idk if I popped up wrong setting or what?

 

[Vic 40]

Can I take a pic of my RAM settings in BIOS and u tell me what to change?

You could and i can try,maybe that 1.5 is the standard.
Maybe use this to share pics,
http://imgur.com/

I will try to take a look at the manual for your mobo too.

Well it should be like this,

You have to go into the bios,
got to the "Motherboard Intelligent Twaeker" =MIT from now on,
somewhere you'll see "Dram Voltage Control" this is at auto,got to that and set it to 1.5,auto might just be fine too,
go to "Dram configuration",
a bigger menu will open,
only the first four are important right now (haven't set other ram options myself,if that becomes the case should we ask Tradesman1 for help,don't think it's necessary though to meddle with those)
set the first four at these settings: "9-9-9-27".
set "Command Timing" at 2T,you could try 1T but it may not boot up or give faults and you'll maybe have to do a clear cmos,it might just go to the old settings if it doesn't boot the first time,2T seems the one to go for imo,
You need to change settings from auto to manual to change them,
When changed save with F10+Y.

Do some test,like hyper-pi 32mil., prime95 in blend or just memtest86+ to see if this is stable.

 

[JustRelaxASC]

Can I take a pic of my RAM settings in BIOS and u tell me what to change?

You could and i can try,maybe that 1.5 is the standard.
Maybe use this to share pics,
http://imgur.com/

I will try to take a look at the manual for your mobo too.

Well it should be like this,

You have to go into the bios,
got to the "Motherboard Intelligent Twaeker" =MIT from now on,
somewhere you'll see "Dram Voltage Control" this is at auto,got to that and set it to 1.5,auto might just be fine too,
go to "Dram configuration",
a bigger menu will open,
only the first four are important right now (haven't set other ram options myself,if that becomes the case should we ask Tradesman1 for help,don't think it's necessary though to meddle with those)
set the first four at these settings: "9-9-9-27".
set "Command Timing" at 2T,you could try 1T but it may not boot up or give faults and you'll maybe have to do a clear cmos,it might just go to the old settings if it doesn't boot the first time,2T seems the one to go for imo,
You need to change settings from auto to manual to change them,
When changed save with F10+Y.

Do some test,like hyper-pi 32mil., prime95 in blend or just memtest86+ to see if this is stable.

This is what I was talking about, there is Normal and then 1.600V no 1.5V as an option.

You see: http://imgur.com/a/ibb8s normal appears to be 1.600V
I got 2 BSODs aswell in like 5 minutes one was 1E and the other is in imgur album. Tho both failed to dump and for some reason they deleted all other dumps that were in %systemroot%\Minidump folder

 

[Vic 40]

Setting dram voltage to manual doesn't give more options? Normal should be fine then.

You still have the ram at 1600mhz,try to lower the multiplier (memory clock in one of those pics) untill you get 1333.
Did you change timings too?

 

[JustRelaxASC]

Setting dram voltage to manual doesn't give more options? Normal should be fine then.

You still have the ram at 1600mhz,try to lower the multiplier (memory clock in one of those pics) untill you get 1333.
Did you change timings too?

I didn't change anything yet because I saw that there is no 1.5V

 

[Vic 40]

Even at 1.6V would you be fine although it's a bit high.Your ram is rated to run at 1866@1.65V so should be able to handle that voltage.

 

[JustRelaxASC]

Sorry for late answer, my PC was at another Repair Shop for 10 days and they say it didn't BSOD (Shutdown/Restart) a single time.
So now I have no idea what to do... Any ideas?