Windows 10: BSOD while using Sonar Artist. Event Viewer 1001 and 18

I posted this on Sevenforums because i totally forgot I was using 10 but here's kind of a repost haha.

I was in the middle of using Cakewalk Sonar Artist and the computer randomly BSOD. It a pretty memory and CPU heavy program but I'm curious what happened.

I've had a few crashes as of lately. One I believe to be a bad GPU but now I saw ID: 18 which says something about my CPU.

Any help would be great.

Edit: It's been crashing a lot lately with different kinds of freezing, lock ups, and BSOD. Everytime it was when I used Sonar Artist. I can play new games without issues but once I start using that application it crashes after about 15-20 minutes.

The uploaded attachment is current to today.

:)

 

BSOD with IRQL NOTLESS OR EQUAL error on my comp

Original title: 6008 forcing 1001

Usually seeing bsod with irql not equal or less error on my comp

Event viewer shows two event simultaneously - first 6008 then immediately after 1001

the 6008 shows "The previous system shutdown at xxxx on ‎xxxx was unexpected (at this time the windows was working ok, I mean no crash etc.)

Noticeably, 6008 shows a previous time for unexpected shutdown always (even when at that time system was working ok) and then probably windows forces some Bugcheck 1001 which results in bsod with irql_error.

Suspecting CPU overheating, run Speccy, CPU has temperature in the range of 48-59%, occasssionally to 61% for a sec

 

Update Trusted Sites has stopped working

Look in event viewer; for my user it is not Event ID 1001 like in the Technet forum post I referenced; rather mine is saying ID 1000 and the faulting module is C:\Windows\System32\ntdll.dll. Still looking into it....

 

I only tested the CPU so far but in 15 minutes I got 1 error and just 7 minutes later I got another. CPU is only running at 64 Celsius so It's not over heating and I just got another PSU so I don't think its my powersupply. I'm going to give memtest a run in a little bit for the heck of it. Looks like I might need a new CPU.
Attachment 61295

 

My suggestion is to replace (RMA if you have warranty) the CPU before you run the other tests.
The CPU might cause some tests to either crash or give unexpected results.