New
#21
Okay, thanks for clarification.
zbook is great with the logs.
V2 was just updated.
Please run the new version and upload into the newest post.
DM can be run in addition to V2.
BSOD - Posting Instructions
The DM log collector is the old log collector.
It collects only 15 files whereas V2 collects other and many more useful files for troubleshooting.
The DM was seen in the new thread.
Please upload V2 and DM into this thread.
The logs started on 9/27.
There was only 5 - 6 days of data.
The computer has Ccleaner which can delete/clean important files
DM does not report kernel crashes.
V2 will report kernel crashes.
The BIOS is out of date.
There were 4 missed upgrades.
The BIOS: Version/Date Hewlett-Packard L02 v02.49, 04/10/2016
Upgrade the BIOS: 02.49 > 02.56 Rev.A
https://support.hp.com/us-en/drivers...Id/vc-229763-1
Last edited by zbook; 03 Oct 2019 at 13:47.
Hi Zbook-
have already done V2 etc (see Constant reboots)
Found both DM and V2.
There were many unexpected shutdowns / restarts.
There were no BSOD.
When were the RAM modules installed?
The RAM modules are mismatched.
Mismatched RAM modules and RAM that is not on the Qualified Vendor List (QVL) is a frequent cause of unexpected shutdowns / restarts.
Other causes can be temperature, firmware, software, and hardware.
Please always use paired RAM modules.Code:Location : DIMM3 BankLabel : BANK 2 Manufacturer : 1315 MemoryType : DDR3 FormFactor : DIMM Capacity : 4GB Speed : 1600 Serial : 16219338 PartNumber : CT51264BA160B.C16F ECC : False TypeDetail : {Synchronous} Location : DIMM1 BankLabel : BANK 0 Manufacturer : Samsung MemoryType : DDR3 FormFactor : DIMM Capacity : 4GB Speed : 1600 Serial : 33901619 PartNumber : M378B5173DB0-CK0 ECC : False TypeDetail : {Synchronous}
And make sure the RAM modules are on the computer or motherboard manufacturer's Qualified Vendor List (QVL).
The exception is if provided by the manufacturer (compatibility already tested) or if a vendor guarantees/warranties compatibility.
For testing purposes remove both RAM modules, re-seat the oldest module and evaluate the computer for several days.
Then replace the RAM module with the second module (using the same DIMM) and evaluate the computer for several days.
Then use both modules again and report if there are any changes.
Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer
Find a flash drive > download and install HP Diagnostics UEFI > run extensive tests overnight > the next AM run component tests as needed > post images of the results into the thread
https://www8.hp.com/us/en/campaigns/.../pc-diags.html
For drives the SMART results are designed to predict drive failure.
We see normal results with drives that have failed.
And we may see abnormal results before drives fail.
Some end users replace drives as soon as any problem is displayed by SMART.
Others with backup images will use the drive until the terminal event.
If there are drive performance problems then replace the drive.
Some HP business computers come with 3 year warranties.
HD Tune can display problems but HP does not typically replace drives under warranty unless they fail HP diagnostics.
The HP diagnostics is similar to Sea Tools long generic.
It would be useful to see HD Tune full error scan and other diagnostics.
However if Caldeon Ken prefers that they are not done that's ok with me.
Code:Event[277]: Log Name: Application Source: ESENT Date: 2019-09-27T01:10:36.141 Event ID: 643 Task: Table/Column/Index Definition Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Trisha-PC Description: taskhostw (1524,D,50) WebCacheLocal: Out of date NLS sort version detected on the database 'C:\Users\Trisha\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat' for Locale 'en-US', index sort version: (SortId=00000000-0000-0000-0000-000000000000, Version=0006010100060101), current sort version: (SortId=00000001-57ee-1e5c-00b4-d0000bb1e11e, Version=0006020F0006020F). Event[278]: Log Name: Application Source: ESENT Date: 2019-09-27T01:10:36.204 Event ID: 614 Task: Table/Column/Index Definition Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Trisha-PC Description: taskhostw (1524,D,50) WebCacheLocal: Database 'C:\Users\Trisha\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat': The secondary index 'PartitionIdIndex' of table 'Containers' is out of date with sorting libraries. If used in this state (i.e. not rebuilt), it may appear corrupt or get further corrupted. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.Code:Event[3399]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2019-10-03T16:49:53.318 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Trisha-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.Code:Event[3386]: Log Name: System Source: EventLog Date: 2019-10-03T16:50:17.920 Event ID: 6008 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Trisha-PC Description: The previous system shutdown at 4:39:20 PM on ?10/?3/?2019 was unexpected.
Last edited by zbook; 03 Oct 2019 at 14:35.
[QUOTE=zbook;1737570]Found both DM and V2.
For testing purposes remove both RAM modules, re-seat the oldest module and evaluate the computer for several days.
Then replace the RAM module with the second module (using the same DIMM) and evaluate the computer for several days.
Then use both modules again and report if there are any changes.
ok. ty
Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
l]
I've already installed and is running ok temps
Find a flash drive > download and install HP Diagnostics UEFI > run extensive tests overnight > the next AM run component tests as needed > post images of the results into the thread
did those already
If there are drive performance problems then replace the drive.
Yes- I'm going to do that anyway- have decided as it's now 5 yrs old
thank you again for your time
Also- for your info found a Bios update 30 mins ago which I have now used to flash the bios- am hoping this may help
- - - Updated - - -
V2 was just updated.
OK
The logs started on 9/27. There was only 5 - 6 days of data.
yes- as I said in original post this problem started occurring after i upgraded to windows 10 very recently
The BIOS is out of date. There were 4 missed upgrades.
fixed already
I want to thank Caledon Ken and zbook for their time here. I'm pleased to say that although things weren't resolved quite the way I 'd hoped I do now have a healthy running PC.The issue was almost certainly drivers after installing win10 over win7 i suspect (yes the HD was faulty but not the sole reboot cause imo).
After many attempts at using driver verifier to isolate the dodgy driver (where DO those logs get saved???) I decided at ken's suggestion to replace HD and reinstall win10. I now have a FAST SMOOTH machine (as it runs a great SSD drive).
If I'd had more time (outside my busy job teaching challenging teens 40 hours a week) I'd have pursued driver verify for longer to catch those dodgy drivers! (just to beat them down-lol)
thanks everyone!![]()
Talk about going down the rabbit hole, if you can, please provide the bugcheck code. To do this, over the event viewer, find the latest Event ID 41, go to the xml view, and provide the bugcheck values. They look similar to the following -
The specific bugcheck code will tell you why your PC is experiencing the random shutdown.
EventData
BugcheckCode 159
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa80029c5060
BugcheckParameter3 0xfffff8000403d518
BugcheckParameter4 0xfffffa800208c010
Hi everyone
for anyone searching for help with this issue:
after I changed my hard drive my reboots diminished to 3-5 days apart (not daily)
I then removed automatic restart AND removed Nortons and have had NO more reboots.
I am still not sure what was behind it but when I rang Nortons they seems to be aware of an issue but said it's not their product it's microsoft's issue.
However removing has helped!
thanks again all![]()