random BSOD related to ntoskrnl.exe

Hello phantomsa and welcome to Sevenforums.

To be able to help you, we'd need a full attachment in order for us to analyse your crash. The below link will guide you through some steps for catching these files. If you have any questions just ask us.

https://www.sevenforums.com/crashes-d...tructions.html

With that said, I'll look at the stand-alone dumps.

BSOD Analyse

ATI-driver was blamed. Do the below tutorial in order to achieve a clean install without leftover files of the driver.

i) Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance
ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
iii) Download Driver Sweeper
iv) Get to safe mode (without network) and search for Driver Sweeper in your
v) Select all the ATI components and analyse them
vi) Clean them, head into Windows without internet and install the driver you've downloaded previously

Memtest86+

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff1001673859c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88007864b95, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

Best Regards,
Frederik.