BeamNG argument w/AMD gfx driver = BSOD 0x18

Twice now, mind you, I've been editing and trying to make awesome BeamNG.Drive maps, this program has downed this system. I have driver package version 15.20.1062.1003.150728A1-187447C as per the first box in the Catalyst Control Center INFORMATION tab for 'driver packing version' and 15.7.1 for Catalyst version. Direct3d version 9.14.10.0.1128 and OpenGL version 6.14.10.1.3399.

A bit about this system:
Windows 7 x64 Home OEM no-major-brand (legitimate, activated too)
Asus Maximus Hero VII Z97 Motherboard
i7 4790k cpu @ 4.4ghz (phanteks red cooler)
16gb 2400mhz ram, 2x8 configuration (corsair)
Radeon R7 265 2gb (HD 7850 2gb). Asus Brand
3x SSD's MLC-Nand, no HDD's
SB X-FI Titanium
Seasonic 750W PSU.

THIS SYSTEM IS STABLE 100%. NOTHING crashes on this, ever.
NO power issues, NO heat issues (it's air cooling, LOTS of nice quiet fans).

SOMETHING is not getting along between the BEAM editor (specifically, vertex manipulation) & the AMD driver. I had the driver from november or so, I am in the process of updating it now... hopefully this problem goes away. It's not particularly common, but this is the 2nd time, in two weeks it's downed the system.
Sound locks & repeats, once I got the blue screen with the 0x18 'reference by pointer' which basically is leading my to believe it's the GFX card driver, but there's not artifacts, etc, signs of a dying/dead card etc.
Only BEAM is doing this, though, never actually have seen that error in all these (20-21) years. I am going to say that it's possible something BAD happened during editing, but I was just nudging vertices with a 1-size tool, one at a time and BZZZZZZZT *CRASH* (old saying from MS Monster truck madness voice "Microsoft Windows has CRASHED leaving an incredible path of destruction behind it" ...yea).
Maybe it's AMD's reason for having these (sarcasm) wonderful driver reputation issues...
I don't know, but I can be sure of one thing - it isn't the system. I am not quite sure what's happening with this. Hopefully the driver update fixes it. I'd like to be able to call this thing stable running Beam.
Incidentally... I can run 8-16 vehicles on this game, run it for hours, until the thing can't process any more of them and I darest not put in another - handy when testing AI functions on a map under development, and it won't crash (if it does, it's the AI doing it).
The processor isn't clocked past it's standard turbo speed (it only stays @ that when running fast enough it needs it), the memory speed is supported by the CPU in dual channel, board, and obviously the memory itself (integrated memory controller on these Haswell/DC cpu's is pretty good).
The video card was not currently overclocked when this happened.
Basically, this thing has been running 18 months no issue, I just want to know if maybe it's possible it's Beam doing this 0x18 REFERENCE BY POINTER or it's something more with the gfx driver.
The reference happened @ location 0xFFFFFA800C7832E0 in memory. I have been editing most of the day, though I had to restart the editor 10 minutes before because the decal road layering is bugging out sometimes (rendering however it wants to, not paying attention to the #'s I'm giving for priority).

I don't think it'll give me a BEAM crash report because it BSOD's the system in the process.

Normally this thing stays on for a few months before I restart it, and until the last 2 weeks, it's been fine. Now it's not - even one BSOD is bad news, here's to hoping a new driver fixes it.

If anyone else has gotten a reference by pointer error check-code 0x18, please give some input.

 

It's been a few days and lots of vertice editing, and no crash has recurred whilst using the in-game F11 editor (this is the one I meant). If it goes two weeks from when this was posted, I'll consider it an AMD driver issue. I don't know why it would happen, but the editor runs the game pretty much full-on, so if there's a bug or instability in the driver, it'll be found! Just posted because I didn't know if others were having this exact issue.
Thanks for taking the time to reply, Nadeox1.