📎 AI Summary: In this thread, the original poster reports recurring system crashes, including BSODs and freezes, while troubleshooting through system scans and driver management. Respondents suggest checking for application hangs and analyzing wait chains, but the user continues experiencing lock-ups and display issues, particularly with monitor recognition. Overall, the user is seeking guidance on resolving stability and display configuration problems, expressing frustration and uncertainty about next steps.
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
W7F_19-01-2017.zip
1.3 MB
· Views: 438
Microsoft Defender: No threats detectedScan details
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.
I always growl @ my son for doing this, but would it help temporarily to leave the case "open".. its running 86-87F during the day inside the room right now.. our AC just can't keep up.
Also, did you get a chance to look @ the PSU readouts? I don't know if I need to replace it or not. I do want to get 3 more HD's and a more modern graphics card, as well as another 16G of ram.... SOMEDAY.
Also, there are 4 cpu temps.. i finally found the temp limit for the cpu and its 61c. So, I'm thinking I should set an alarm for that temp but of the 4 i have no clue which to monitor.. they are not the same.
I always growl @ my son for doing this, but would it help temporarily to leave the case "open".. its running 86-87F during the day inside the room right now.. our AC just can't keep up.
Also, there are 4 cpu temps.. i finally found the temp limit for the cpu and its 61c. So, I'm thinking I should set an alarm for that temp but of the 4 i have no clue which to monitor.. they are not the same.
coretemp matched hwinfo so I set the alarm for overheat
Microsoft Defender: No threats detectedScan details
After the temp in the house dropped I was able to play warthunder for short time without an alarm.
I'm going to have my son open the case up today.. supposed to hit 110F heat index today *sigh*
It may be just down to the piece of silicon the chip is on. It's a bit of a lottery and some chips will need more vcore than others.
If you guy's have never manually changed the vcore then I'm tempted to say leave it but you could try reducing it to 1.35v. It also looks like the LLC is enabled because you can see the voltage increase's.
LLC or load line calibration is something used by overclockers to counter vdroop and normally you don't need it enabled under stock running conditions.
More voltage means higher temps so it can be worth finding what your true vcore is and not just the one assigned by the motherboard.
Well, happy to report systems been very nice *knock on wood* for a while now..
Microsoft Defender: No threats detectedScan details
I let this run 24/7 and this report is after a passmark benchmark run
Microsoft Defender: No threats detectedScan details
I'm fairly sure it's nvidia's geforce experience. I've removed it and things seem wonderful as I said.
CRAP! here we go again *sigh*... I removed the asmedia usb drivers and replaced them with Asus drivers because I am having a problem with my wd passport ultra 1tb external drive been seen by device manager but no drive letter assigned. If I go to diskpart and assign one it will be gone on reboot. Automount IS active. My usb thumbdrive works fine.
now, I get a bsod *sigh*
This error was received during log collection.. ( which is running SUPER slow )
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\WINDOWS\dxdiag.txt'.
File name: 'C:\WINDOWS\dxdiag.txt'
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
at W7F_Diagnostic_Tool.Form1.Button1_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)
************** 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.
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.
Here's the error when I try to assign a drive letter..
Microsoft Defender: No threats detectedScan details
In this thread, the original poster reports recurring system crashes, including BSODs and freezes, while troubleshooting through system scans and driver management. Respondents suggest checking for application hangs and analyzing wait chains, but the user continues experiencing lock-ups and display issues, particularly with monitor recognition. Overall, the user is seeking guidance on resolving stability and display configuration problems, expressing frustration and uncertainty about next steps.