Random BSOD mostly ntoskrnl.exe

Welcome to the forum.

There are no outdated drivers which means it might be a hardware problem.

Follow:

Arc said:

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

• Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• Virus Check:
  
  • Make scans with these tools below:
    
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  
  • Reduce the start-up items. This will help avoid software conflicts:
    
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

• System File Checker
  
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    
    • Link to full tutorial: SFC /SCANNOW Command - System File Checker
• Run Disk Check in Windows 7
  
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
    
    • Link to full tutorial: Disk Check

• Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
  
  • Then test your Hard Drives (s) running a Hard Drive Diag.

• Check for heating issues using Speccy or HWmonitor
  
  • HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
  • Speccy - System Information - Free Download
    
    • Please upload a summary tab using Speccy. Screenshots and Files - Upload and Post in Seven Forums

• Test and Diagnose RAM issues with MEMTEST86+
  
  • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
    
    • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 18:33:35.894 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:12.112
BugCheck 3B, {c0000005, fffff80002e88ac5, fffff8800772b8a0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 17 00:44:04.706 2013 (UTC + 6:00)
System Uptime: 0 days 2:12:16.534
BugCheck 1A, {41790, fffffa8002581bc0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  WorldOfTanks.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Oct 14 05:07:08.586 2013 (UTC + 6:00)
System Uptime: 0 days 6:36:37.398
BugCheck 19, {3, fffff8a0107708a0, fffff8a0107708a0, ffebf8a0107708a0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  WorldOfTanks.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Oct 13 22:24:48.240 2013 (UTC + 6:00)
System Uptime: 0 days 3:05:39.068
BugCheck 1A, {41284, 2d8a9001, 68cf, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  Maxthon.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Oct 10 05:15:47.881 2013 (UTC + 6:00)
System Uptime: 0 days 5:39:29.709
BugCheck 19, {3, fffff8a0102d48a0, fffff8a0102d48a0, ff5ff8a0102d48a0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  WorldOfTanks.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Wed Oct  2 22:16:49.769 2013 (UTC + 6:00)
System Uptime: 0 days 3:57:52.581
BugCheck 3B, {c0000005, fffff8000315070c, fffff8800892a9f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDoOpen+2cc )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Welcome to Seven Forums krissz.

Have a look in your BIOS hardware or monitor section. See what voltages you have there. Post what it shows for 3.3V, 5V, and 12V.

HW Monitor will also give the volts while in Windows.

My bios is set to default, no overlocking.

Bios:
Attachment 291101

HardwareMonitor:
Attachment 291027

I ve run prime95 blend test and it shows error:
Attachment 291028

Did you do the tests Koolkat listed?
Your voltages are OK.

You can get a screenshot of UEFI BIOS by inserting a formatted USB stick and then going to BIOS. Press F12 to capture what you are looking at to the USB stick.

The Prime95 error can be from too little CPU Vcore (voltage) or a RAM issue. Is the RAM operating at it's specifications? I have 2 machines that won't run Prime but work well in all other ways.
Your hardware has passed in all tests, all I could think it may be is a bad motherboard. Unfortunately there is no test we can do for that. You can give ASrock a call and speak to a tech there explaining what you've done.

You can also try a freshly downloaded BIOS and reflash it in case it is corrupted or out of date.

As I stated give ASrock a call, I have in the past. Not a good experience, sorry to say, I still have a board that won't even "turn on" yet they claim they fixed it and checked it out.