BSOD with "Smart Assignment"
 

I'm running 4 workers doing first time LL's on an i7 2720QM with 8 GB DDR3. Most of the year it's my main PC so I've got affinity on "Run on any cpu" so I can keep working in the background and that works just fine. Now i'm using a different PC so I've got it on "Smart Assignment" which gives me 10 less ms/iter but seems to cause an occasional BSOD. Runs about the same temp so I don't think it's a hardware problem, any Ideas Why?

[QUOTE=Pegos;450683]I'm running 4 workers doing first time LL's on an i7 2720QM with 8 GB DDR3. Most of the year it's my main PC so I've got affinity on "Run on any cpu" so I can keep working in the background and that works just fine. Now i'm using a different PC so I've got it on "Smart Assignment" which gives me 10 less ms/iter but seems to cause an occasional BSOD. Runs about the same temp so I don't think it's a hardware problem, any Ideas Why?[/QUOTE]

It could be a memory issue too, if you feel confident the CPU is okay.

I assume MS Windows. What OS version?

What version of Prime95 are you using?

Do you get the same BSOD error code each time, or different codes? What error code(s) are you getting?

How often are the BSOD errors occurring with Prime95 running? (multiple times a day, once a day, multiple times a week, etc)

What temperatures are you typically seeing while Prime95 is running?

Is your CPU overclocked at all, or running at the original factory speed?

Sorry about the delay, I've been busy the past few days. CPU is stock, It seemed to be about once a day and always DPC_WATCHDOG_VIOLATION 0x00000133. I've got Windows 10 Pro, version 1607. Temps are usually between 75-85 Celsius (my max Tjunction is 100 C), Prime 95 v28.7,build 1

Thanks for the help.

Not that I'm familiar with many BSOD error codes, but that one seems very specific. From a quick look online, it may be specific to a driver that is incompatible with Windows 10 and may not have anything to do with Prime95 at all (though Prime95 might have a tendency to make any existing problems more pronounced with the extra usage). Below are some instructions for replacing that driver with a Windows 10 compatible driver that should already be available on your system.

[URL="https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bluescreen-error-dpcwatchdogviolation/100cb707-0716-40d4-88a8-7bf9dd8f836d"]https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bluescreen-error-dpcwatchdogviolation/100cb707-0716-40d4-88a8-7bf9dd8f836d[/URL]
[QUOTE]This error may occur due to the iastor.sys driver, which is not fully compatible with Windows 10.

Microsoft is currently investigating a solution to prevent the driver from being migrated when upgrading to Windows 10. For those of you already on Windows 10, you can work around this error by replacing the problematic driver with the Microsoft storahci.sys driver by following these steps:

1) Right-click the Start icon and select Device Manager.
2) Expand IDE ATA/ATAPI controllers.
3) Select the controller with “SATA AHCI” in its name (such as Standard SATA AHCI Controller). To verify that you’ve selected the right controller, right-click the controller, select Properties, click the Driver tab, and then Driver Details. Verify that iastor.sys is a listed driver, and click OK.
4) From the Driver tab, select Update Driver…
5) Select Browse my computer for driver software.
6) Select Let me pick from a list of device drivers on my computer.
7) Select Standard SATA AHCI Controller.
8) Click Next, then Close, and then restart your computer.[/QUOTE]

There are some other things that might cause that error, so if you still get it after updating drivers (or if that driver wasn't in use), you may want to research that specific BSOD error code for some other solutions.

I was already using storahci.sys but it was an intel one, tried switching to the standard microsoft one and left it overnight but still got the same blue screen. Just seems strange that this would only happen when smart assignment is turned on. In any case, I'll do some research on it but in the meantime I'll just leave it on "run on any cpu" since that's been chugging away fine for months.

Figured out the issue, it was a bad nvidia driver. The driver was too new for my gpu and it had to revert to an older version. Been running in smart assignment affinity for nearly 24 hours with no problem.