2 files attached as requested.
Jump to content
Posted 28 August 2015 - 01:11 AM
2 files attached as requested.
Posted 28 August 2015 - 04:30 AM
Further relevant information.
After I attached the two files as requested, I followed instructions as in section 6. However, upon downloading/initiating the Driver Verifier in the first instruction, my computer crashed then rebooted into a start up loop of Reboot, Driver Verifier Detected_Violation (yes, the underscore appeared in the error report) and System Automatic Repar/Diagnositics. The only options I had in the advanced menu available were Re install or System Restore. I did a System Restore, the computer is running "normally" but with the obvious problems . I await further instructions as to whether to proceed to No 2 in section 6 or wait for direction as to how to complete Driver Verifier section safely.
Posted 29 August 2015 - 03:45 PM
Please be sure to zip up the contents of C:\Windows\Minidump and upload it with your next post.
This should contain the Driver Verifier memory dumps, which we'll be very interested in seeing.
If you have trouble zipping them up, just copy them to your Desktop and zip them up there.
AFAIK - HP SimplePass is not compatible w/W10. Please uninstall it immediately.
No memory dumps in the uploaded reports
None listed in the KernelDumpList report
Your UEFI/BIOS (version F.63) dates from 2012. 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.
I see several different topics that you have started. Please keep all of your replies in one topic - it will help with the troubleshooting.
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 Administrative Events
- 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: http://www.cpuid.com/softwares/hwmonitor.html
Posted 30 August 2015 - 02:49 AM
firstly, there was no intent to multiple post my problem. I posted firstly and Blueelvis gave me adifferent link to follow to reply with attached information. I made my reply but it did not appear in the reply section of the link he gave me, I waited a day and had no reply from him so reposted the same info in the open forum dialogue I had started, nothing more nothing less.
I will attempt a Windows Bios update.
Temp monitor downloaded.
Simple Pass and associated software uninstalled.
Posted 31 August 2015 - 05:05 AM
I'm really late for work - but here's the text of the webpage that you couldn't see.
I'll have a look at the reports after work today:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, or Windows Server 2008 R2SymptomsIn Windows 8, Windows 7, Windows Server 2012, Windows Server 2012 R2 or Windows Server 2008 R2, your computer restarts, and a critical error message that resembles the following is recorded in the event log:Note The values for the Stop error BugcheckCode and the BugcheckParameters can vary.
Log Name: System
Event ID: 41
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
The Details tab displays the following information:
PowerButtonTimestamp 129165039139928187More informationThe kernel power event ID 41 error occurs when the computer is shut down, or it restarts unexpectedly. When a computer that is running Windows starts, a check is performed to determine whether the computer was shut down cleanly. If the computer was not shut down cleanly, a Kernel Power Event 41 message is generated.
An event 41 is used to report that something unexpected happened that prevented Windows from shutting down correctly. There may be insufficient information to explicitly define what happened. To determine what may have happened and to identify a potential resolution, it is important to know what the computer was doing at the time just before the event occurred.
If event 41 is logged because power to the computer was interrupted, consider obtaining an uninterruptible power supply (UPS) such as a battery backup power supply. An underpowered or failing power supply may cause this behavior. For example, if you added RAM or additional devices or hard disks when this problem began, the power supply may cause the problem.
An event 41 can occur in the following scenarios. Scenario 1: The computer restarts, and there is a Stop error BugcheckCode in the event data When a Stop error occurs, the Stop error data is written in Event ID 41 as part of the additional event data. There may be the instances in which the Stop error code information cannot be written before the computer restarts or shuts down. Such instances are covered in scenario 3.
Note The BugcheckCode data in the event is written in decimal format instead of a more typical hexadecimal format. Therefore, the decimal value should be converted to a hexadecimal value.
If the Stop error BugcheckCode entry in the event ID data is not zero, you should convert the BugcheckCode value from decimal to hexadecimal. Most documentation on Stop error codes reference the code as a hexadecimal value instead of a decimal value. To do this, follow these steps:
Note The value that the calculator displays is now the hexadecimal code. Repeat these steps for other nonzero values.
- Click Start, and then type calc in the Search box.
- Click View, and then click Programmer.
- Make sure that the Dec option button is selected on the left side of calculator.
- Use the keyboard to enter the decimal value from the BugcheckCode value.
- Click the Hex option button on the left side of the calculator.
The following example contains a Stop error BugcheckCode entry from an event ID 41:
PowerButtonTimestamp 0Converts to 0x9f (0x3, 0xfffffa80029c5060, 0xfffff8000403d518, 0xfffffa800208c010)
Note The zeros that appear in front of the code are not typically displayed. When a BugcheckCode entry is converted to a hexadecimal format, it should have eight digits. For example, 0x9F is typically documented as 0x0000009f, and 0xA is documented as 0x0000000A. After you identify the hexadecimal value, go to support.microsoft.com, and search for the converted hexadecimal code (0x0000009f) and the word bugcheck.
For more information, see the following article on the Microsoft TechNet blog:
The preferred way to shut down Windows is to click Start, and then click an option to turn off or shut down the computer. In this case, the operating system closes all files and notifies all services and applications that are running so that they can write any data to disk and flush any caches.
If you have to press and hold the power button because of an issue that limits the ability of the computer to function correctly, you should run a query about the symptoms that you are experiencing so that you can get help with troubleshooting. Keywords that you might use in your search are "hang," "responding," or "blank screen."
For more information about a specific situation in which a computer may stop responding, click the following article number to view the article in the Microsoft Knowledge Base: 974476 The computer stops responding when an USB device resumes from the USB Selective Suspend state in Windows 7 or in Windows Server 2008 R2
For troubleshooting help, go to the Support for Windows 7 Microsoft website. Scenario 3: The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang) The Stop error code and the PowerButtonTimestamp are listed as zero. For example, consider the following scenarios:
To check whether this scenario is occurring, press the CAPS LOCK key on the keyboard. When you do this, if the CAPS LOCK light on the keyboard does not change when you press the CAPS LOCK key, the computer may be completely unresponsive (hard hang).
- The Stop error BugcheckCode value is listed as zero. Circumstances can prevent writing the Stop error BugcheckCode information before the computer restarts or shuts down. In this case, a BugcheckCode value of zero is logged. Also, perhaps no Stop error occurred, and the shutdown resulted from a power loss. For example, on a portable computer, this could mean that the battery is removed or completely drained. Or, on a desktop computer, this could mean that the computer was unplugged, or a power outage occurred.
- The PowerButtonTimestamp is listed as zero. Circumstances can prevent writing the PowerButtonTimestamp information before the computer restarts or shuts down. In this case, a value of zero is logged. This can occur if the power button is pressed and held for at least four seconds when Windows has an operation running that prevents writing the event to disk. You might also see this scenario if the computer is “hard-locked” and therefore unresponsive to any input, and the computer has to be powered off. To determine whether the computer is unresponsive, try pressing the CAPS LOCK key to toggle the CAPS light on the keyboard.
This scenario usually indicates a problem with the hardware. To help isolate the problem, check the following items:
- Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
- Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
- Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
- Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
- Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.
If you see that the computer generates a Stop error that contains a BugcheckCode value that is not reported in an event ID 41, change the restart behavior for the computer. To do this, follow these steps:
- Right-click My Computer, and then click Properties.
- Click Advanced system settings.
- Click the Advanced tab.
- In the Startup and Recovery section, click Settings.
- Click to clear the Automatically restart check box.Feedback Was this information helpful?Properties
Article ID: 2028504 - Last Review: 08/14/2015 07:16:00 - Revision: 13.0Applies to
- Windows 10 Pro, released in July 2015
- Windows 10 Enterprise, released in July 2015
- Windows 8 Enterprise
- Windows 8
- Windows 8 Pro
- Windows Server 2012 Foundation
- Windows Server 2012 Standard
- Windows Server 2012 Datacenter
- Windows 7 Enterprise
- Windows 7 Professional
- Windows 7 Ultimate
- Windows Web Server 2008 R2
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Datacenter
- Microsoft Hyper-V Server 2008 R2
- Windows HPC Server 2008 R2
- Windows 8.1
- Windows 8.1 Enterprise
- Windows 8.1 Pro
- Windows Server 2012 R2 Datacenter
- Windows Server 2012 R2 Foundation
- Windows Server 2012 R2 StandardKeywords:
- kbcip KB2028504Tell us what we can do to improve the articleYesNoSomewhat
Posted 31 August 2015 - 03:46 PM
Nothing significant that I can find in the Admin logfile
The Critical events don't seem to be preceeded by anything in particular - so the most likely cause is a hardware problem.
Have you had any hanging recently? If so, what were the temps when it happened?
What is the purpose of the WMICrecoveros.zip file?
Still need the zipped contents of C:\Windows\Minidump - or you telling me there's nothing there.
Posted 01 September 2015 - 01:39 AM
maybe I got confused somewhere and attached the wrong zip. Its possible this was one of the files requested by Blueelvis.
It contains info re Minidump but dont know if this is the exact file you require.
Name=Microsoft Windows 10 Home|C:\WINDOWS|\Device\Harddisk0\Partition2
I have looked in C\Windows\minidump but no Minidump file appears. When I put that into the searchbox, the above file appears.
I have web pages hanging all the time, the pages just wont popu regardless of browser, Also graphics on desktop like start menu and new notifications sidebar either take seconds to appear or sometimes dont appear at all.
My computer froze again at the point of trying to send this to you earlier, had to do a manual reboot.
Posted 01 September 2015 - 06:49 AM
Temperature moniter text file. attached.
Posted 01 September 2015 - 08:06 AM
HWMonitor logfile is empty - what have the temps been?
Does it list a reading for your video card? If so, what was the max temp there?
The WIMCrecoveros file is just a file telling us where the files are stored. It's not surprising that it showed up in a search - I was just confused about it's presence.
Since it's probably video, try these free diagnostics: http://www.carrona.org/hwdiag.html
Start with the video tests and monitor the temps while doing so (not just the video temps - monitor all of the temps for anything over 80ºC )
Posted 01 September 2015 - 10:10 AM
for some reason, the information disappears from the .txt file on my desktop, happened twice now. Also, somewhere between utilising the CPU monitor and trying to retrieve the text file from the desktop to send, my computer has completely frozen.
The only way I can send you the info is via attached images of the screen in two parts, as some info is just off the page....and no, my screenshot facility doesnt work.
Posted 01 September 2015 - 10:35 AM
attached are two images, 1) the highest temps recorded after 5.5 minutes of running Fur Mark Stress tester. 2) running temperatures five minutes after the stress test.
Posted 01 September 2015 - 03:46 PM
Notice in the first set of images, the Intel Graphics chip registers at 0º C
Yet in the second set of images it registers at 73ºC
Unless this system is stored in a freezer, I have to wonder about the temps.
Do you have any other way to measure the temps (can you borrow and IR thermometer?)
Other temps are in the 80's - hot, but not overly so.
While it's not definitely the video, we still can't be 100% sure it's not to blame.
Do you have another video card that you can try?
If not, then try purchasing one from a shop/store where you can return it for your money back if it's not needed.
Posted 02 September 2015 - 12:08 AM
Unfortunately Usama, as a non IT engineering type I am not confident enough to strip my laptop down to change the video card or take its temperature. Hope you understand.
Posted 02 September 2015 - 04:39 AM
Sorry, I thought this was a desktop system.
You can't do the tests that I suggested on most laptops.
There's not much else at this point. We can either continue with attempting to fix W10, or have you revert back to the previous version of Windows
If you choose to revert back, make sure that you have recovery media handy - and that you have a backup of all your data - as I've seen a number of attempts to revert that have failed (and needed a wipe and reinstall to fix it).
Troubleshooting will be much easier with the previous OS - as the system was designed for this, and there will be compatible drivers available.
Posted 02 September 2015 - 06:11 AM
Probably not much to do then with W10 as you say, but I also cannot revert back to 7 now as revert time has expired. I will have to try and work through the problems and fixes one by on. Thanks for all your help.
0 members, 0 guests, 0 anonymous users