Just finished letting my system idle for a whole hour with msi afterburner v4.3.0 & aida64 v5.95.4500 open. Aida64 was open on the sensors tab too for the whole hour. Not a single bsod.

I've had HWInfo, EVGA Precision OC, and Corsair Link open with the system running folding @ home on 3 GPUs (2 on 1 system, 1 on the other) for the past 24 hours on this driver...no issues.

squall-leonhart

Sajin
@Gawg36
 
squall-leonhart is sora.

Spoil sport, i was going for a surprise reveal. lol.
 
 I panicked for a moment because i have Process Explorer running which reads vram and gpu usage,  forgetting it was doing so via windows api's :p
 

HOLY COW!! That's funny, and came as a major surprise.
Anyhow, I am glad, I know Sora/squall-leonhart is an expert so it's good to know. I can trust what he says. (Same on the NV forums.) Saijin & Squall-leonhart you must have been laughing out loud. Anyhow, it's all good.

Digital_Fuzion

Gawg36

Digital_Fuzion
I would love to see a developer group like the one from Omega Drivers which was an unofficial, third-party NVIDIA graphics driver team. They differed from the official drivers in that they offered more customization and extra features. To bad that's not the case with poor buggy drivers on aging 1080 hardware. A driver shouldn't be so bad at this point of the hardware being in the market place for sometime now. I have not had any issues other then dealing with NVIDIA driver problems.  

OMEGA, yeah that rings an old rusty bell from years ago....Maybe??
The only thing I know which is in some way related is NVidia Inspector which simply reveals, and allows us to alter a lot of paramaters. Paramaters that exist in the base driver but are hidden in NVCP. Not good.
Of course they also provide profiles for many games.
 
So no new code a such, just adds a lot of accessabiltiy, for extra functionality as long as your know what sparse grid  SS AA  and more new options.
Do OMEGA go one step further and actually add/take/change the driver code itself? Complex stuff if so!!
 
P.S. I used to use NVInspector a lot for that functionality and got some beautiful screens, but for some reason, it doesn't have such an impact with Pascal? I also have 1080ftw and 1080ti ftw3 in other PC. Could just simply be as you said " poor buggy drivers on aging 1080 hardware." Basically MS + NV = shoddy, premature software that causes headaches. I think they should include a free box of aspirin with every new W10 and New NVidia GPU. I didn't say GPU drivers, I know the issues, but I have had very very few GPU driver issues in my single GPU system.

Omega tweaked the drivers and optimized them for performance. This forum just has tech talk thinkers not developers. I think companies like EVGA should tweak their own drivers with Nvidia's source code.  Point made these drivers suck and EVGA can't do anything about it now.

Yes, that would be nice. But as you said it's too late now. I guess it would take a lot work too. You made the point perfectly!!

squall-leonhart
feels like the firefox tdr all over again, except theres no workaround to run the software thsi time x.x

On Wed 5/23/2018 10:54:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aida64.sys (0x0000000000000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aida64.sys .
Google query: aida64.sys KMODE_EXCEPTION_NOT_HANDLED

 
A couple of hours of leaving AIDA64 open which was entirely accidental.

squall-leonhart
let me know how it is in 4-7 days, theres a variable or two i've presently excluded because it didn't make sense for aida to be the faulting process (ie, slight load on the video decoder engine), and having different gpu's active in the same machine.

At 4 days now...still no issues.
 
Maybe (as said above) there is an issue with AIDA?
 
I few months back, I was having random crazy issues that I swore was Precision X OC, a graphics driver, Corsair Link, etc.
 
It turned out to be a bad memory stick...and it took me a while to isolate which stick.  I purchased new memory and the problems went away.
 
Then they came back...so it must be something wrong with these things...I just fixed the memory...right?
 
So, I removed my overclock...played with just about every setting.  Removed, inspected, and reconnected every cable.  Heck, I even updated the BIOS on my motherboard to the latest rev.
 
This time, it turned out to be a few bad sectors on the hard disk where the Windows Swap File sits!  (Why does Windows need to use a swap file when I have 32 GB of RAM?  /shrug).  I moved the swap file to a different disk...and the problems went away.
 
This may sound simple or silly...but the LAST thing I suspected was a bad memory stick (as just about every piece of software and/or driver out there (including Windows patches) are just total junk...what has happened to software QA anyway?).  And after that, the LAST thing I suspected was a bad sector for the Windows swap file...
 
Since I figured this all out...the system has been rock-solid stable.

Sajin
I let aida64 & msi afterburner run overnight, and everything was running just fine when I got up. 

My wife hates noise of any type so she would never allow me to do that.

Gawg36

HeavyHemi

squall-leonhart
feels like the firefox tdr all over again, except theres no workaround to run the software thsi time x.x

On Wed 5/23/2018 10:54:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aida64.sys (0x0000000000000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aida64.sys .
Google query: aida64.sys KMODE_EXCEPTION_NOT_HANDLED

 
A couple of hours of leaving AIDA64 open which was entirely accidental.

Thanks for this valuable info Direct X 12. I will not be using AIDA anymore, well until I'm sure it's fixed. Bloody awful that this can/does happen!

Yes...apparently there are a few who still don't believe this is an issue in this an other threads. Nor do we know if those telling us they don't have any issues are using Windows 1803...seems a bit off topic to me. I don't believe it is actually AIDA causing the issue.

HeavyHemi

Gawg36

HeavyHemi

squall-leonhart
feels like the firefox tdr all over again, except theres no workaround to run the software thsi time x.x

On Wed 5/23/2018 10:54:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aida64.sys (0x0000000000000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aida64.sys .
Google query: aida64.sys KMODE_EXCEPTION_NOT_HANDLED

 
A couple of hours of leaving AIDA64 open which was entirely accidental.

Thanks for this valuable info Direct X 12. I will not be using AIDA anymore, well until I'm sure it's fixed. Bloody awful that this can/does happen!

Yes...apparently there are a few who still don't believe this is an issue in this an other threads. Nor do we know if those telling us they don't have any issues are using Windows 1803...seems a bit off topic to me. I don't believe it is actually AIDA causing the issue.

I agree. I also fully think everything squall=leonhart, AKA xxxx, is correct. The problem is that there is no easy way to reproduce it. It may happen in an hour, or take over a week, but it does happen as referenced by others.
And yeah, AIDA itself is not the problem - I think. With the driver in question and the Win 10 1803 everyone is open to it (please correct me if that's wrong). So it's a personal choice to take a few measures that greatly reduce the risk or to ignore it. People who ignore it will I assume mostly,  but not all,  be OK as they don't run 
affected programs/processes run for hour after hour.
 
World wide the majority of regular PC users wouldn't have a clue what we are talking about anyway; and I haven't seen
headline reports of this problem. Hence my opinion about risk factor.
 
To me it's the fact that this exception can happen at all with Nvidia drivers, and  Win 10 1803. [Question: Are earlier Win 10 vs affected?] Continuing,  It's just very poor. What angers me is that NV have business wise done excellently with Pascsal. Huge profits. Some of that should be re-invested in more RD, especially software/drivers, and take on a few more of the world best soft engineers - of course their salary would be astronomical, but that's how it is.
 
Simply put, I am not concerned as a few simple measures have been taken, but the big point: IT SHOULD NEVER HAVE HAPPENED in the first place, regardless of how high or low the risk is!! 
 
Edit: If anything I wrote is somewhat off, wrong I mean, please tell me what and why. This forum/thread has some very knowledgeable posters. We are lucky. I am also
ready to stand corrected, when written by someone I know, knows their stuff. Simply learning never stops. But not someone pushing their own opinion as if it's fact. That happens a lot in the NV forums. Not so much here which is why I like this whole EVGA forum. Thanks gents!

HeavyHemi

Gawg36

HeavyHemi

Gawg36

HeavyHemi

squall-leonhart
feels like the firefox tdr all over again, except theres no workaround to run the software thsi time x.x

On Wed 5/23/2018 10:54:52 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aida64.sys (0x0000000000000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aida64.sys .
Google query: aida64.sys KMODE_EXCEPTION_NOT_HANDLED

 
A couple of hours of leaving AIDA64 open which was entirely accidental.

Thanks for this valuable info Direct X 12. I will not be using AIDA anymore, well until I'm sure it's fixed. Bloody awful that this can/does happen!

Yes...apparently there are a few who still don't believe this is an issue in this an other threads. Nor do we know if those telling us they don't have any issues are using Windows 1803...seems a bit off topic to me. I don't believe it is actually AIDA causing the issue.

I agree. I also fully think everything squall=leonhart, AKA xxxx, is correct. The problem is that there is no easy way to reproduce it. It may happen in an hour, or take over a week, but it does happen as referenced by others.
And yeah, AIDA itself is not the problem - I think. With the driver in question and the Win 10 1803 everyone is open to it (please correct me if that's wrong). So it's a personal choice to take a few measures that greatly reduce the risk or to ignore it. People who ignore it will I assume mostly,  but not all,  be OK as they don't run 
affected programs/processes run for hour after hour.
 
World wide the majority of regular PC users wouldn't have a clue what we are talking about anyway; and I haven't seen
headline reports of this problem. Hence my opinion about risk factor.
 
To me it's the fact that this exception can happen at all with Nvidia drivers, and  Win 10 1803. [Question: Are earlier Win 10 vs affected?] Continuing,  It's just very poor. What angers me is that NV have business wise done excellently with Pascsal. Huge profits. Some of that should be re-invested in more RD, especially software/drivers, and take on a few more of the world best soft engineers - of course their salary would be astronomical, but that's how it is.
 
Simply put, I am not concerned as a few simple measures have been taken, but the big point: IT SHOULD NEVER HAVE HAPPENED in the first place, regardless of how high or low the risk is!! 
 
Edit: If anything I wrote is somewhat off, wrong I mean, please tell me what and why. This forum/thread has some very knowledgeable posters. We are lucky. I am also
ready to stand corrected, when written by someone I know, knows their stuff. Simply learning never stops. But not someone pushing their own opinion as if it's fact. That happens a lot in the NV forums. Not so much here which is why I like this whole EVGA forum. Thanks gents!

All I can say for 100% certain, is I have never had it happen with just Afterburner running. It has always been in combination with AIDA64 and it's relatively quick when it happens... within hours. I don't run the Corsair AIO software or keyboard software.  Surprised the carp out of me the first time because I never have BSOD's from just random stuff. It's always my own doing.  So far, I've had three but I bet if I don't run AIDA64 for a week, I won't have one...ready set.....go.

So you're saying (in bold above) that when running Aida & AB, that within hours you're getting a BSOD?  And is that with just normal/typical or gaming use?  I'm just asking out of curiousity because I have Aida & AB running daily (both load on startup), all day long and haven't had any BSOD's.
 
This new driver 397.93, and the last one 397.64, both with no issue's.  OS is 1803 and my PC is running from about 8:30 AM to ~ 6:00 PM.  It does get shut down at ~ 6:00 if that has any bearing.

ksgnow2010
At 4 days now...still no issues.
 
Maybe (as said above) there is an issue with AIDA?
 

No, this is a driver fault - gpu-shark can bring it on too and that has basic nvapi access compared to aida64,  though a bit more involved than what precision and afterburner expose.
 
You can bring precision up to gpu-shark level by enabling overlay or lcd output for all sensor types, including VPU/Decoder engines, and per card vram usage.
 

HeavyHemi
Yes...apparently there are a few who still don't believe this is an issue in this an other threads. Nor do we know if those telling us they don't have any issues are using Windows 1803...seems a bit off topic to me. I don't believe it is actually AIDA causing the issue.

We can rule out Windows 10 version differences, its occuring across Windows 7, 8 and 10.  I ran some windows 8 users dumps through osronline the other day (ps, osronline doesn't handle 17134 dumps properly yet), as well as locally with windbg.
 
 Hemi, can you get that dump file to Fiery?