BSOD ntoskrnl.exe 64bit

Yes they are and may void your warranty. You might want to check your the max temps your motherboard and CPU can take from their manuals.

rapstyle said:

are not these tests a bit dangerous? what is the maximum temperature i can reach safely?

Intel Burn Test should run fine at the standard setting and stop it if temps go above 80C.

In your BIOS/UEFI make sure Virtu and on chip graphics are disabled. I wouldn't use the ASRock Super Speed USB software, I had it and it's very buggy.

Try these steps to install only the graphics driver.

1.Download the preferred driver and save it to the desktop.
2.Double click the installer and you will see a screen where it will be extracted to, change that to your desktop.
3.Open Device Manager through Control Panel.
4.Expand Display adapters and right click the name for yours and choose Update Driver\Browse my Computer. Select the driver folder you just saved on the desktop. Click Next.
5. Your system should say "Windows has successfully updated your driver software".

If you get a window saying you already have the most current driver, go back to step 4 and choose Uninstall Driver software instead. Then restart from step 3.
Attachment 228491 Attachment 228492

Code:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED 
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
BugCheck 1E, {ffffffffc000001d, fffff800030a98eb, 1, fffffa8009e2b000}
Probably caused by : memory_corruption
..........................................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8804fb72b5e, 0, fffff800033dd874, 5}
Could not read faulting driver name
Probably caused by : memory_corruption
........................................................................................
BugCheck 50, {fffff7fffb20db44, 0, fffff800033558c7, 2}
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

You might want to enable Driver Verifier again to see if we have luck with getting BSODs out of it. You'll need to do tasks that stress the computer etc. and see if that creates a blue screen.

Have you performed a clean install and seen how the computer performs? Like with nothing installed on it. No software/drivers etc?

Nope.

Code:

BugCheck A, {18, 2, 0, fffff80002f122af}
Probably caused by : memory_corruption ( nt!MiRemoveLockedPageCharge+b )

And you didn't enable verifier.