BSOD starting again.

Bear

Well-Known Member
I'm still only running windows defender as requested in previous thread and suddenly the crashes have started again. When it triggers, its either a BSOD or total lockup of the system.
 

Attachments

Neemobeer

Windows Forum Team
Staff member
I don't see any dump files. Can you check and manually upload any new ones. C:\Windows\Minidump.


I do see that your system failed to create a dump. You may want to turn off automatic manage page file and set it specifically for the C drive.


Page File: Bad User Agent detected
 
Last edited:

Bear

Well-Known Member
it's in a different place... %SystemRoot%\MEMORY.DMP
and I guess that explains why i saw the no page file error when infact there is plenty..
upload_2017-1-19_12-4-38.png
 

Bear

Well-Known Member
I had installed a keyboard driver but uninstalled it and have rebooted several times since. i've checked for malware and issues reported by glary ( none found ) there is nothing in the minidump folder at this time. I did just experience a freeze while watching a amazon prime video.. no BSOD just total freeze
upload_2017-1-19_14-1-46.png
 

Bear

Well-Known Member
lol I'm cursed.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online cleanup-image /restorehealth

Error: 87

DISM doesn't recognize the command-line option "cleanup-image".
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>dism /online/cleanup-image/restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0


Error: 87

The online/cleanup-image/restorehealth option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>
 

Bear

Well-Known Member
I had another lock up ( not bsod ) just a few minutes ago, ran it right afterwards but I guess it didn't find anything wrong...

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>
 

Neemobeer

Windows Forum Team
Staff member
If you're able to run commands when it's "locked up" it's probably just an application hanging. If you open task manager and go to the details tab. If the video hangs again right click on the process associated with the player and select 'Analyze Wait Chain' if there is anything listed in the Windows post a screen shot.
 

Bear

Well-Known Member
I was watching a video on amazon prime. the video froze audio started a sputtering sound and all inputs were non-responsive, so it was an actual lock-up not hung app
 

Bear

Well-Known Member
do I need to remove the entire suite or just the video driver itself?
Things have changed so much since the 80's / 90's I feel like a dummy now days
 

Bear

Well-Known Member
I threw a BSOD on restart after running DDU but then worked on second restart. The display settings I think are wrong now however :( I"m using a Hisense 40H3E with hdmi but windows is saying the monitor is s "generic pnp monitor" .
I mainly do Photoshop & lightroom so colorspace is critical
 

Attachments

Bear

Well-Known Member
UGH, another lockup.. system was idle and I was away for about 15minutes... gpu temp 43c cpu temp 26c so I'm pretty sure its not overheating.
malware anti-malware bytes and housecall both showed no issues.
 

Bear

Well-Known Member
sorry to be a pest... another bsod and audio stutter.. this time it created a file even though the audio was stuttering.
update: after playing for 30 min I noticed the temps spiked a bit,
Capture.PNG
which is weird since I'm watercooled.
 

Attachments

Last edited:

Bear

Well-Known Member
ok, i ran the online version of housecalls so there is nothing but defender currently for anti-virus, I went ahead and removed glary.. yes, I did ddu in safe mode, it rebooted to BSOD, rebooted again to running system..
on the event viewer idk what to look for nor where..
I don't see SearchIndexer running anywhere, not services nor processes.
There is a game I recently installed ( WarThunder) .. could that be causing issues?
 

Bear

Well-Known Member
I'm beginning to suspect warthunder but odd thing is It works fine for a while... like 3-4hrs this time...
here's another dump file, this time the error was different.
I sure do appreciate all your doing to help.
 

Attachments

Bear

Well-Known Member
just an fyi I tried to run driver verifer and it crashed on startup..
Code:
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(String fileName)
   at W7F_Diagnostic_Tool.Form1.Button2_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
W7F Diagnostic Tool
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Bear/Desktop/W7F%20Diagnostic%20Tool/W7F%20Diagnostic%20Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8750 (QFE.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 

Bear

Well-Known Member
i don't remember I thought I got them directly from asus. It's interesting that pcprobe is still showing because its not been installed for a very long time.
Apparently you can't use amd's chipset drivers without a radeon card, which honestly makes no sense..
upload_2017-1-23_4-17-32.png
I'm waiting to talk to asus right now to see what can be done about the pcprobe and inability to update the sata driver. Also find out if they have the latest chipset drivers.
 

Bear

Well-Known Member
Asus refused to tell me exactly what changes in the registry need to be made to remove pcprobe settings.
they also said they do not have any windows 10 drivers for the 990fx chipset.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
No drivers are need by the 990fx chipset, the ones build into windows 10 are just fine. Removing all of PCProbe would no doubt help.
 

Bear

Well-Known Member
last 24hrs has been good.. I purged all the usb drivers ( I found a generic one from a photography tethering app ) and then updated all the asus related drivers I could find. I think the sata one is still nerfed though, I can't seem to get it to update fully.
I removed warthunder, reinstalled it and was able to play all day heavily yesterday w/o a single issue, so I'm fairly certain its not warthunder. Nvidia released a update today also. I'm comfortable with the registry but just don't know which keys other then the ASIO key itself. I see the driver in the files but no uninstall... Is there a reliable free driver removal software?
 
Top