Jump to content
Posted 04 September 2016 - 10:55 PM
Posted 06 September 2016 - 03:13 PM
Please wait until it crashes for you, then recover and immediately generate these 2 reports:
Report Set #1) Please run this report collecting tool (even though you may not be experiencing BSOD's) so that we can provide a complete analysis: (from the pinned topic at the top of the forum) http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities.
.ZIP is the type file that can be uploaded to the forums.
Report Set #2) Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here: http://support.microsoft.com/kb/2028504
While waiting for a reply, please monitor your temps with this free utility:
SpeedFan v. 4.5.1 and later (free from here: http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.
To make it work (log the temps to a file) you have to do BOTH of the below:
1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.
2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.
The log will be located at C:\Program Files (x86)\SpeedFan
Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.
Notes: whenever you change the options related with logging, SpeedFan starts a new log file.
Posted 07 September 2016 - 11:59 AM
It only took me 4 freezes to get through it all and finally send this. Help please this is driving me crazy. The admin zip file also has the temp reports
Thanks so much
Posted 08 September 2016 - 09:47 AM
Your hard drives are running a bit hot.
Have you checked the airflow around them?
Nothing real certain in the Admin logfile
We usually start looking for low-level problems (hardware, compatibility, low-level drivers) when we see this.
Also, this appears to be an upgrade to W10 - so any old problems may have been upgraded with it (in other words, we may suggest a fresh install of WIndows later on, so now's a good time to backup your stuff).
Are you able to boot to Startup Repair? If so, does the system freeze there?
Try pressing the power key to shut down the system while the little circle thing is rotating.
Do that several times, it should get you into Startup Repair that way.
Your UEFI/BIOS (version 2.3.1) dates from 2007. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).
I am very concerned about compatibility issues in this system. Unfortunately, the only certain way to rule them out is to reinstall the previous OS.
You have a Belkin USB Wireless Adaptor:
I do not recommend using wireless USB network devices.
These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
Video Controller PCI\VEN_1002&DEV_71A3&SUBSYS_0D031028&REV_00\4&182A81B0&0&0108 The drivers for this device are not installed.
0 members, 0 guests, 0 anonymous users