It's always helpful if there are dump files, but there are other supporting documents in there that can be helpful in figuring it out. No problem with the dropping by, but you seemed to be on the right track in chasing it down, just like you always are.
You should also look in the Event Viewer after a crash, even if you don't have dump you will have an event. IMO, it's certainly a hardware problem. Are the headphones plugged into a sound card?
Thanks for joining in.
I have requested the OP to try the system without Head Phones or any other plug in device not needed to try and isolate the problem.
Steve what do you think about verify drivers to try and make a BSOD. It might give you some clues?
I've thought about that. But it seems we are talking to each other. We haven't heard from the op recently. That was why I asked for the BSOD posting instructions to be uploaded, in case I could see something. If not, we could move to Driver Verifier, but we've received no response as of yet.
Hello and thank you for the replies,
Here we go, starting from the older posts to newer..
-I haven't had a chance to uninstall Avira, but performed another ESET scan last night and it came up with one detection (included in attachments). I'll include the first scan results as well. Both times the items were quarantined and deleted.
-I'll unplug all peripheral USB cables I'm not using and will plug them in when necessary.
-I'll disable f.lux for the time being. I'll have to adjust my brightness on my monitor at night manually then.
-I adjusted some of the typos in my system specs.
-I have not monitored my system temperatures, as it's quite cold in the room where the computer is. But by using speccy, I'll also include attachments for the CPU, mobo voltage (and fans), as well as GPU temps.
-If the problem persists, I'll try unplugging my headphones. Kind've in a louder environment so I'll try setting up speakers if it's still a problem.
-While I haven't had a lock-up (with no BSOD screen) in a while *knocks on wood* I've included a previous thread with several zip files using DM Log Collector. There are no dump files associated with them, even though I had followed the BSOD instructions and using the program upon hard restart (Random BSOD while browsing/gaming).
-Upon essenbe's advice, here's another screenshot included displaying that there were no integrity violations.
I'll look through the Event Viewer upon re-reading my older thread. Kinda hard to sieve through all these event logs.
Thank you again and hopefully that was some of the information you were looking for.
How about unplugging all external peripherals from the computer and running Driver Verifier. The first this is to create a restore point (link below). This is important as it can sometimes be your only way back. Accept the fact that you may have to do a clean install, which you may have to do anyway, so not a big risk. Also, make sure your computer is configured for Small Memory dumps. Dump Files - Configure Windows to Create on BSOD
When you set up verifier, sort all drivers by Provider and enable all drivers not provided by Microsoft.
WarningBe sure to create a Systm Restore point before proceeding further System Restore Point - Create
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any. Be aware that your computer may seem slow and sluggish, this is normal. What we are doing is placing stress on the drivers, trying to make the computer crash in hopes of catching the offending driver in the subsequent dump file. Please run it for a minimum of 24 hours of actual use. I don't consider idling actual use. There are no restrictions on your use of the computer. Do what you normally do. If there is anything that usually makes your computer freeze or crash, do that often. Again, we are trying to make it crash.
Hi essenbe,
Thanks for the reply. So once I have time to run it for 24 hours, which should be in the next day or so, and to double-check:
-Create a System Restore point prior to doing anything else. Would it be advantageous to back up my personal files at this point as well..? In the event that I need to reformat/clean install, or can that be performed later?
-Followed small memory dump instructions. Included a pic just in case.
-I can continue to use my computer to use the internet/email/word docs while using Driver Verifier. I should just expect a fair amount of slow down? In the event of a BSOD, I'll use DM Log Collector again?
-Lastly, and the only thing that didn't make a whole lot of sense to me, was unplugging all external peripherals. Did you mean to remove any peripheral cables that I'm not using (i.e. printer, ipod cables, etc) vs. the ones I need to use to 'use' the computer (i.e. keyboard, mouse) while using the computer while Driver Verifier is working?
Thanks and will report soon upon stressing the system and your further instructions. It's appreciated.
Quote