Daily BSOD with various stop codes 0x1e, 0x3b, 0x7e

Good information.
It will be interesting to see what Asus has to say about your RAM.
You now have a new set of RAM, same P/N as before, is this correct?

Any more crashes or not, it's a good idea to increase the VCCIO to 1.150v.
This will be the Intel recommended 0.50v max difference between RAM voltage and VCCIO (CPU Integrated Memory Controller) voltage.

If the new RAM continues to run stable, then you are good.
If you have more crashes then we can adjust settings a bit more and see if it will become stable.
Either way you should run memtest86+ to be sure.
Run memtest86+ for a minimum of 7 full passes with both RAM cards installed, best to run overnight.
Stop the test if you get any errors.
RAM - Test with Memtest86+


Your Ram was reported as KHX1600C9D3/4GX, CPUZ has it as KHX1600C9D3/4GX, the same. You posted the number on the cards is/was KHX1600c9d3k2/8gx, the K2/8GX means Kit of 2 for total of 8GB. It's the same P/N a single RAM card vs a kit of 2 cards, as you mentioned previously.

If you want to have BSODs and crashes, be sure to overclock.

Well it was too soon to assume everything was good.
Another bsod occurred when I was surfing web. Dumps attached.

EDIT: btw I'm not sure if this is worth mentioning but sometimes after bsod my mouse stays off (no response) and gets back on as soon as I press any of buttons. It doesn't matter what usb port I use and keyboard never had same issue.

jCni said:

Yes the new Ram is exactly the same model as before.
I did increase vccio to 1,15 and everything else is on default. Just curious will that change make any difference if I want to OC my cpu again after I get this system stable?

I will run memtest again at night and post results. System seems fine so far.

Yes, it will make a difference, it will make your system more stable at stock settings and when OC'ing.

As for OC'ing, many do it with completely stable results.
The only crash I've had, after getting the OC stable, was due to a PSU failure, new PSU and it's very stable again.

Let us know the memtest86+ results.

jCni said:

Well it was too soon to assume everything was good.
Another bsod occurred when I was surfing web. Dumps attached.

EDIT: btw I'm not sure if this is worth mentioning but sometimes after bsod my mouse stays off (no response) and gets back on as soon as I press any of buttons. It doesn't matter what usb port I use and keyboard never had same issue.

I've seen mouse/keyboard cause crashes, get another mouse to test with.
You can also check for an updated mouse driver.

When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Blue Screen of Death (BSOD) Posting Instructions


Last crash info:

Code:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpWaitForResource+cc

Waiting for the rest of the crash information, this will let us get a better idea of the cause.

As mentioned, do the memtest86+ testing.
What version of Chrome are you using?
Update is possible.
What graphics driver are you using?
Update if possible: AMD Catalyst™ Display Driver for Windows Vista/Windows 7 64-bit

As far as the mouse, it's a good thing to check.

You'll find it a standard thing for the motherboard company to blame the CPU or RAM, the RAM company will blame the CPU and motherboard, the CPU company will blame the RAM and motherboard.
Though it is possible, it's rare to get CPU failures.

Beta graphic drivers are not a good idea, remove the beta and sweep for remnants, install 12.6.

When you removed your previous OC, did you re-set the BIOS settings to default?

Some of the previous crashes (with the old RAM):

Code:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!PoIdle+423
------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION - again - same as before
Usual causes:  System service, Device driver, graphics driver, ?memory
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED - this one may be corrupt as it is showing a lot of errors in the debugger
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
ExceptionAddress: fffff88001542ca5 (ataport!IdeStartIoCallBack+0x00000000000000e5)
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
------------------------------------------------------------------------------------------------------------------------------
Next one is same as above - may be corrupt 
------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlRemoveEntryHashTable+1d

The last crash after the new RAM was installed is the same as you were having before, lets run a CPU test that will also test some of the RAM.

Be sure to watch the CPU Core temps while testing.
Use Real Temp

To stress the system you can run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes.
Set the time before you start, on the CPU:OCCT page.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Max CPU Core temp is 77.6°C.
Intel® Core™ i5-2500K Processor

The Sys/App event logs aren't in English so I can't read them.
They are a very good source of information on what your system is doing, this will impede the analyses.

Code:

24.7.2012 20:44	Application Error	Viallisen sovelluksen nimi: setup.exe_ASUS AI Suite II, versio: 1.1.2.1, aikaleima: 0x4eca370e
Viallisen moduulin nimi: KERNELBASE.dll, versio: 6.1.7601.17651, aikaleima: 0x4e211319
Poikkeuskoodi: 0x0eedfade
Virhepoikkeama: 0x0000b9bc
Viallisen prosessin tunnus: 0x68c
Viallisen sovelluksen käynnistysaika: 0x01cd69dd089c6c83
Viallisen sovelluksen polku: C:\Users\Jani\Desktop\AI_Suite_II_V10220_P8Z68-V_LX_XPVistaWin7\setup.exe
Viallisen moduulin polku: C:\Windows\syswow64\KERNELBASE.dll
Raportin tunnus: 4f93628a-d5d0-11e1-b948-c860006ac1dd

Un-install all Asus utilities, they are known to cause system crashes.

Code:

22.6.2012 13:10	Application Error	Viallisen sovelluksen nimi: FlashPlayerPlugin_11_3_300_257.exe, versio: 11.3.300.257, aikaleima: 0x4fc82063
Viallisen moduulin nimi: NPSWF32_11_3_300_257.dll, versio: 11.3.300.257, aikaleima: 0x4fc821fc
Poikkeuskoodi: 0xc0000005
Virhepoikkeama: 0x0016b4bd
Viallisen prosessin tunnus: 0x450
Viallisen sovelluksen käynnistysaika: 0x01cd50774957265c
Viallisen sovelluksen polku: C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerPlugin_11_3_300_257.exe
Viallisen moduulin polku: C:\Windows\SysWOW64\Macromed\Flash\NPSWF32_11_3_300_257.dll
Raportin tunnus: 94c529db-bc6b-11e1-bbd3-c860006ac1dd

Update your Flash Player Plugin.

Code:

4.7.2012 8:34	Application Hang	Ohjelman avp.exe versio 12.0.0.374, lakkasi olemasta yhteydessä Windowsiin, joten se suljettiin. Voit tarkistaa, onko ongelmasta saatavilla lisätietoja, ohjauspaneelin Toimintokeskus-kohdasta.
 Prosessin tunnus: b6c
 Alkamisaika: 01cd59bf862c8b12
 Päättymisaika: 2
 Sovelluksen polku: C:\Program Files (x86)\Kaspersky Lab\Kaspersky Internet Security 2012\avp.exe
 Raportin tunnus: cc8567b8-c5b2-11e1-af31-c860006ac1dd

Can you tell me what this is?

Driver issues, outdated:

Code:

GEARAspiWDM.sys Mon May 18 20:17:04 2009

Un-install iTunes for testing purposes, this is known to cause crashes. The driver is out of date.

Are you using Intel RST or the stock msachi drivers?
The MS driver is showing loaded but, the runinfoLocal info says Intel RST.