Need help Troubleshooting random shutdown

[Elapo]

I reaaaaaally could use some help with this, I'm out of ideas.

So yesterday, my PC suddenly shut down. No BSOD, nothing. I checked Event viewer, and I had a Kernel power (Event 41) error with bugcheckcode 0 (which is weird). I assumed it was just another "power dip". I've had those before in this area, though they're not very common.

In the evening, however, I had another shutdown, again with bugcheckcode 0. This time I asked my brother if his PC had rebooted, which it hadn't, so I knew it was an issue with my PC. It just happened again, so I'm looking for some help.

I'll just write whatever I found out up until this point in a list, might be easier to read:

- At one point, one of the Event Viewer entries displayed Bugcheckcode 281 (randomly, I can't find it anymore. I'm really sure I saw it, but it seems to have reset to 0), which is 119 (0x119) in hexadecimal. I looked it up and it's something to do with video, usually an issue with GPU drivers. As I'd installed new drivers the day before, I suspected those were the issue, but the problem persists after rolling back the drivers.

EDIT: The code is back in event viewer. I have no idea why it changes...

 

- Because windows doesn't seem to know what is causing the issue, I suspected my PSU might be the issue, so I tried stressing the entire system with AIDA64, which resulted in nothing, the PC passed (fairly short) stress tests without issues. I was hoping to be able to reproduce the issue like this, to confirm the PSU as being the culprit, but that didn't happen...

- I have 1 minidump file, from the first time it happened. The other times it hasn't created a dump. Inside the dump is the error code I saw before (0x119), supposedly caused by "watchdog.sys". 

- before every shutdown, there is the same 4 information events. Every time, without fail. They're "filter manager" events, stating:

File System Filter 'aswSnx' (6.0, ‎2015‎-‎08‎-‎12T16:44:50.000000000Z) has successfully loaded and registered with Filter Manager.File System Filter 'FileCrypt' (10.0, ‎2015‎-‎07‎-‎10T05:14:31.000000000Z) has successfully loaded and registered with Filter Manager.File System Filter 'aswSP' (6.0, ‎2015‎-‎07‎-‎27T19:34:27.000000000Z) has successfully loaded and registered with Filter Manager.File System Filter 'npsvctrig' (10.0, ‎2015‎-‎07‎-‎10T05:14:31.000000000Z) has successfully loaded and registered with Filter Manager.

It's ALWAYS these 4, in the same order, and then the shutdown.

 

- I always keep track of my temps, they're not outside spec. GPU's max at 70C and 67C, CPU maxes at 55C.

 

- I Haven't changed any hardware lately.

 

-The shutdowns happened Twice while playing Mad Max (Have played a lot of that recently, so might be coincidence) and once while watching youtube.

 

 

Specs:

 

PSU: Corsair TX850 - 850W

CPU: i7 2600k @ 4.0GHz

GPU: 2x ASUS GTX 970 STRIX (SLI)

MOB: MSI Z68A GD65-G3

RAM: Crucial Ballistix Sport 16GB (2x 8GB Sticks)

[samcool55]

Turn system back to stock speeds and just keep using it, maybe it will solve it.

[Bittenfleax]

-snip-

Do you have Avast? If so, disable it. Or uninstall it because the aswSP is to do with Avast I think. Sames goes with aswSnx. Then carry on using your PC as normal and see if the problem still happens?

 

EDIT: Uninstall all updates/roll back a few days because it could be caused by Windows Updates.

[Elapo]

Do you have Avast? If so, disable it. Or uninstall it because the aswSP is to do with Avast I think. Sames goes with aswSnx. Then carry on using your PC as normal and see if the problem still happens?

 

I'll try this first - Can I replace it already, or should I just run  w/o an AV scanner?

[Bittenfleax]

I'll try this first - Can I replace it already, or should I just run  w/o an AV scanner?

Run without and see if it happens. If that does not work, look at the edit I made above and try that.

[Elapo]

Run without and see if it happens. If that does not work, look at the edit I made above and try that.

 

Alrighty, It might be a while before I report back, as the issue is pretty random as to when it happens, but I'll try everything if it doesn't work.

 

Thanks for the help already

Turn system back to stock speeds and just keep using it, maybe it will solve it.

I'll try that as well, as soon as I have ruled out software as much as possible!

[GM_Peka]

Are you running windows 10? Check your CPU voltages that CPU-Z reports. I had random restarts when I was running win 10 because win10 can mess with voltages for some odd reason (undervolts without you telling it to).

[Elapo]

Are you running windows 10? Check your CPU voltages that CPU-Z reports. I had random restarts when I was running win 10 because win10 can mess with voltages for some odd reason (undervolts without you telling it to).

I am, Win 10 Pro 64Bit, forgot to include that.

During the stress testing I was keeping an eye on Vcore, because I suspected my PSU. As far as I could tell there wasn't an issue there. I did use HWMonitor, but since that's made by the CPU-Z guys, so I don't think that matters too much.

A minimum of 1.008V and max 1.264, so that doesn't seem off to me. I'll keep an eye on it though!

[GM_Peka]

I am, Win 10 Pro 64Bit, forgot to include that.

During the stress testing I was keeping an eye on Vcore, because I suspected my PSU. As far as I could tell there wasn't an issue there. I did use HWMonitor, but since that's made by the CPU-Z guys, so I don't think that matters too much.

A minimum of 1.008V and max 1.264, so that doesn't seem off to me. I'll keep an eye on it though!

When did you go down to 1.008? Seems quite low, unless it was during idle.

[GM_Peka]

Try re-seating all your PSU cables.

[Elapo]

When did you go down to 1.008? Seems quite low, unless it was during idle.

I started HWMonitor first, so that's most likely an idle reading.

Try re-seating all your PSU cables.

I'll do that next time it restarts as well!

[ionbasa]

You mention you have 1 minidump?

Follow the BSOD posting instructions pinned at the top of this subforum here: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

[Elapo]

You mention you have 1 minidump?

Follow the BSOD posting instructions pinned at the top of this subforum here: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

Only 1 though for 3 shutdowns so far, which is rather weird, anyway, here's the files and additional info:

Folder with Zip files:

https://drive.google.com/folderview?id=0B5hgjq_xmAc0UUc4cmVsRDVtOG8&usp=sharing

 

Additional info:

OS - Windows 10 Prox64It originally had Windows 7 UltimateThe OS is full retailThe Mob, CPU, PSU and HDD's are 4 years old, SSD ~1 year and GPU's, RAM and case is 4-5 Months oldOS installation is 1 Month old, I did the upgrade on my W7 install. Last re-install was when I got my SSDCPU - i7 2600k @ 4GHzGPU - 2x ASUS GTX 970 Strix (SLI)Motherboard - MSI Z68A GD65-G3PSU - Corsair TX850 - 850WManufacturer - I built it myself!Desktop.

[ionbasa]

 

Only 1 though for 3 shutdowns so far, which is rather weird, anyway, here's the files and additional info:

Folder with Zip files:

https://drive.google.com/folderview?id=0B5hgjq_xmAc0UUc4cmVsRDVtOG8&usp=sharing

 

Additional info:

OS - Windows 10 Prox64It originally had Windows 7 UltimateThe OS is full retailThe Mob, CPU, PSU and HDD's are 4 years old, SSD ~1 year and GPU's, RAM and case is 4-5 Months oldOS installation is 1 Month old, I did the upgrade on my W7 install. Last re-install was when I got my SSDCPU - i7 2600k @ 4GHzGPU - 2x ASUS GTX 970 Strix (SLI)Motherboard - MSI Z68A GD65-G3PSU - Corsair TX850 - 850WManufacturer - I built it myself!Desktop.

Took a look at the Minidump.

 

The VideoScheduler which is part of an DIrectX component had an exception. This is an GPU or GPU driver issue. Do you have another GPU to cross check if its faulty hardware?

 

Also, you should use Display Driver Uninstaller (DDU) to remove old Nvidia Drivers: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then re-install the latest driver. 

 

I see you're running GTX970s in SLI. Maybe one of the cards is bad? You're best bet would be to start troubleshooting with the GPUs. Try running only one at a time and see if Windows still crashes. If it crashes with one of the two GPUs, then that GPU will need to be RMA's. I doubt it's your PSU, you have adequate wattage given your setup.

 

I'll wait for your reply, please keep us posted.

Windows 8 Kernel Version 10240 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff803`f1c10000 PsLoadedModuleList = 0xfffff803`f1f35030Debug session time: Wed Sep  2 05:02:53.654 2015 (UTC - 4:00)System Uptime: 0 days 21:25:07.329********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_SCHEDULER_INTERNAL_ERROR (119)The video scheduler has detected that fatal violation has occurred. This resultedin a condition that video scheduler can no longer progress. Any other values afterparameter 1 must be individually examined according to the subtype.Arguments:Arg1: 0000000000000002, The driver failed upon the submission of a command.Arg2: ffffffffc000000dArg3: ffffd000285f49f0Arg4: ffffe000793c0ec0Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  0x119PROCESS_NAME:  SystemCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff800eaf13c3d to fffff803f1d5e240STACK_TEXT:  ffffd000`285f4928 fffff800`eaf13c3d : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffd000`285f49f0 : nt!KeBugCheckExffffd000`285f4930 fffff800`eda29ea2 : ffffe000`793c0ec0 00000000`c000000d 00000000`0000000b 00000000`0000000b : watchdog!WdLogEvent5_WdCriticalError+0xcdffffd000`285f4970 fffff800`eda972e3 : ffffe000`793c0ec0 ffffe000`793c0ec0 ffffe000`77eaf000 ffffe000`7c2abce0 : dxgmms2!VidSchiSendToExecutionQueue+0x8422ffffd000`285f4a90 fffff800`eda66318 : ffffe000`7c2abce0 ffffe000`78417140 ffffe000`7c2abce0 ffffe000`78a87a30 : dxgmms2!VidSchiSubmitPagingCommand+0x343ffffd000`285f4b60 fffff800`eda6342a : ffffe000`77eaf000 ffffd000`285f4bc8 ffffe000`78a87a30 ffffe000`00000000 : dxgmms2!VidSchiSubmitQueueCommand+0x180a8ffffd000`285f4b90 fffff800`eda633e0 : ffffe000`77eaf000 00000000`00000000 ffffe000`6be66040 ffffe000`6be66000 : dxgmms2!VidSchiRun_PriorityTable+0x46ffffd000`285f4bc0 fffff803`f1cf6e88 : ffffd000`285f0000 ffffd000`285f4d50 00000000`00000001 ffffd000`285f4d44 : dxgmms2!VidSchiWorkerThread+0x80ffffd000`285f4c00 fffff803`f1d63326 : fffff803`f1f73180 ffffe000`7dc4d040 fffff803`f1fe9740 00000000`00000001 : nt!PspSystemThreadStartup+0x58ffffd000`285f4c60 00000000`00000000 : ffffd000`285f5000 ffffd000`285ef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: dxgmms2!VidSchiSendToExecutionQueue+8422fffff800`eda29ea2 cc              int     3SYMBOL_STACK_INDEX:  2SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+8422FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms2IMAGE_NAME:  dxgmms2.sysDEBUG_FLR_IMAGE_TIMESTAMP:  55bec217FAILURE_BUCKET_ID:  X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+8422BUCKET_ID:  X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+8422Followup: MachineOwner 

[Elapo]

Took a look at the Minidump.

 

The VideoScheduler which is part of an DIrectX component had an exception. This is an GPU or GPU driver issue. Do you have another GPU to cross check if its faulty hardware?

 

Also, you should use Display Driver Uninstaller (DDU) to remove old Nvidia Drivers: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then re-install the latest driver. 

 

I see you're running GTX970s in SLI. Maybe one of the cards is bad? You're best bet would be to start troubleshooting with the GPUs. Try running only one at a time and see if Windows still crashes. If it crashes with one of the two GPUs, then that GPU will need to be RMA's. I doubt it's your PSU, you have adequate wattage given your setup.

 

I'll wait for your reply, please keep us posted.

 

Event viewer actually listed Bugcheckcode 281 (which is 0x119), that's why I tried rolling back drivers and updating again. I didn't uninstall it with DDU though, just the standard clean install, So I might have to try that again.

 

I'd love to be able to quickly test whether or not it is one of the GPUs (They're still within warranty for another year and a half or so, that's easily RMA'd), but the problem is that it hasn't crashed yet since I uninstalled Avast! (One of the first suggestions) yesterday, so I'm still waiting for it to crash before I can rule avast out and try any of the other solutions.

 

Also, the fact that Event viewer doesn't seem to have recorded anything (and no minidumps) the last 2 shutdowns was why I initially thought of a PSU issue, due to it's sudden nature.

 

Anyway, I'll update as soon as I know more, thanks for your help!

Windows 8 Kernel Version 10240 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff803`f1c10000 PsLoadedModuleList = 0xfffff803`f1f35030Debug session time: Wed Sep  2 05:02:53.654 2015 (UTC - 4:00)System Uptime: 0 days 21:25:07.329********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_SCHEDULER_INTERNAL_ERROR (119)The video scheduler has detected that fatal violation has occurred. This resultedin a condition that video scheduler can no longer progress. Any other values afterparameter 1 must be individually examined according to the subtype.Arguments:Arg1: 0000000000000002, The driver failed upon the submission of a command.Arg2: ffffffffc000000dArg3: ffffd000285f49f0Arg4: ffffe000793c0ec0Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  0x119PROCESS_NAME:  SystemCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff800eaf13c3d to fffff803f1d5e240STACK_TEXT:  ffffd000`285f4928 fffff800`eaf13c3d : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffd000`285f49f0 : nt!KeBugCheckExffffd000`285f4930 fffff800`eda29ea2 : ffffe000`793c0ec0 00000000`c000000d 00000000`0000000b 00000000`0000000b : watchdog!WdLogEvent5_WdCriticalError+0xcdffffd000`285f4970 fffff800`eda972e3 : ffffe000`793c0ec0 ffffe000`793c0ec0 ffffe000`77eaf000 ffffe000`7c2abce0 : dxgmms2!VidSchiSendToExecutionQueue+0x8422ffffd000`285f4a90 fffff800`eda66318 : ffffe000`7c2abce0 ffffe000`78417140 ffffe000`7c2abce0 ffffe000`78a87a30 : dxgmms2!VidSchiSubmitPagingCommand+0x343ffffd000`285f4b60 fffff800`eda6342a : ffffe000`77eaf000 ffffd000`285f4bc8 ffffe000`78a87a30 ffffe000`00000000 : dxgmms2!VidSchiSubmitQueueCommand+0x180a8ffffd000`285f4b90 fffff800`eda633e0 : ffffe000`77eaf000 00000000`00000000 ffffe000`6be66040 ffffe000`6be66000 : dxgmms2!VidSchiRun_PriorityTable+0x46ffffd000`285f4bc0 fffff803`f1cf6e88 : ffffd000`285f0000 ffffd000`285f4d50 00000000`00000001 ffffd000`285f4d44 : dxgmms2!VidSchiWorkerThread+0x80ffffd000`285f4c00 fffff803`f1d63326 : fffff803`f1f73180 ffffe000`7dc4d040 fffff803`f1fe9740 00000000`00000001 : nt!PspSystemThreadStartup+0x58ffffd000`285f4c60 00000000`00000000 : ffffd000`285f5000 ffffd000`285ef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: dxgmms2!VidSchiSendToExecutionQueue+8422fffff800`eda29ea2 cc              int     3SYMBOL_STACK_INDEX:  2SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+8422FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms2IMAGE_NAME:  dxgmms2.sysDEBUG_FLR_IMAGE_TIMESTAMP:  55bec217FAILURE_BUCKET_ID:  X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+8422BUCKET_ID:  X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+8422Followup: MachineOwner 

[Elapo]

So, a little update.

I've been doing some of the different fixes, removing overclocks, etc... without any result, but I've a strong feeling it's one of the GPU's now. I've had another shutdown with a code today (0x10E), related to video, but also this:

I woke up my PC from sleep (this has caused 2-3 shutdowns in itself already), and I was greeted by both my screen flashing a white image with small purple dots. The flashing was not synced between the two displays, and my secondary display seemed to have a lower resolution version of the "image", with black bars. My only option was to reboot the PC using the power button, after which it booted normally.

Event viewer did not show anything abnormal during the issue.

I'm now testing each card separately, so hopefully I can find out which one of the cards is causing this.

[Elapo]

So, back again.

 

Both cards triggered a shutdown, one "normal" one, the other the one with the flashing screens again (not really a shutdown, but I have to reboot it using the power button). I think it'd be very weird if both cards were bad, So I'm just going to assume neither GPU is faulty for now.

 

I did notice a LOT of entries stating "Display driver nvlddmkm stopped responding and has successfully recovered." right before I shut down the PC with the power button.

 

Next thing I'm going to try is just resetting W10, and reinstalling everything. I'm not really sure what to do after that, so any help is welcome.