Computer freezes but does not crash (no BSOD)

zbook said:

Nice progress.

If you run the log collectors on post #9 the logs can be scanned for significant problems.
Then significant problems can be troubleshooted.

OFFICE64-(2020-05-22_14-17-31).zip

OFFICE64-Fri_22_05_2020_141949_19.zip

Done!

zbook said:

Update the specs in the my computer section:
System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

I will add this as a second system as I still have and use the system already in my profile.

The last BSOD in the logs was in March 2020.

The logs reported drive problems including a bad block.

HP has supported drivers for windows 7 and 8.
There are no supported (tested) drivers for windows 10.

The BIOS is out of date.

For all steps / tests make sure images are posted into the thread:


Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


12) Make sure that there is no over clocking while troubleshooting

13) The BIOS: BIOS Version/Date Hewlett-Packard J01 v02.06, 9/06/2011

14) Open the HP website at HP.com > support > software and drivers > enter the product or serial number > select the operating system > view drivers > post a URL or hyperlink into the thread.

15) Check to see whether this is the most up to date BIOS > then download and install

https://support.hp.com/us-en/drivers...-2?sku=LE248PA

16) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

17) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

18) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


19) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

20) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.

a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool

The testing is done not by time but by passes.
The more passes the better the testing conditions.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM

21) These tests can be performed overnight:
a) HD Tune full error scans
b) Sea Tools long generic tests
c) Memtest86+ version 5.01

22) More to follow pending the above results

Thank you zbook.

This is going to have to wait for the weekend as the computer is in full use during the week.

Just a thought. I forgot about the W10 Control Panel.Security & Maintenance/View Reliability history whilst trying to fix the same symptoms on you on my PC (which had had my old OS drive and CPU from my previous machine) put into a new but similar model PC (Shuttle). Mostly worked fine, except... when I looked at the above CPL option, it was clear I had driver problems and no option but to re-install W10.

Which fixed the problem. I think it is a very useful tool for such as this.=

Ok, I've been busy and a have a few things to report - I think I have solved this problem. The following is a detailed description for anyone else who runs into this or a similar problem.

First up, I had another, seemingly separate issue with my network. On some mornings, I would arrive at work to find the shop network down. The EFTPOS would be offline - webpages would not load, photos from the WiFi enabled camera were not arriving, Google Drive wasn't syncing & my proprietary software was unable to communicate with its servers. Usually I could fix this by restarting the Fibre modem, the WiFi and all the computers (usually, in that order) However, a few weeks back I found the network down and the subject computer frozen and on this occasion, I happened to turn off the frozen computer first, using the power button, and when I did that, the network immediately popped up. Every morning after that, I checked the computer first - every time it was frozen, the network was down, every time the computer was not frozen, the network was OK. The two issues were connected, the only problem now was determining if it was the network causing the computer to freeze or the computer crashing the network.

I did a little online research and found several posts referencing something called "C-States" in the BIOS, These are supposed to be for power saving but have been known to cause computers to freeze and networks to crash. Disappointingly, I could not find anything in my HP8200 BIOS (v0.206) that referred to "C-States" but after reading about them and finding what they do, I made two changes in the BIOS...

1. In "Power > OS Power Management" I disabled "Unique Sleep State Blink Rates"
2. In "Power > Hardware Power Management" I disabled "S5 Maximum Power Savings"
...then saved the changes and restarted the computer.

I have now gone from having these freezes and network crashes 3-4 times a week; sometimes twice in a day, to NOT having a computer freeze or a network crash for five weeks.

While the problem is likely solved, I would still welcome any insight from our more computer-savvy members as to why these power settings could cause these problems.

Please update the progress with the steps in post #22.

Upload a new V2:
BSOD - Posting Instructions

zbook said:

Please update the progress with the steps in post #22.

Upload a new V2:
BSOD - Posting Instructions

Zbook

I'm not seeing any benefit to going to all this work as the issue was never about a BSOD. The computer simply froze (mouse and keyboard locked, and clock stopped), so there was no error code to chase, no data dump, and the only way to restart was power off (at least with a BSOD you could use CTRL-ALT DEL)
Also, this issue seems to have been resolved - the computer runs 24/7 and I have not had a lockup in the six weeks since making the BIOS changes I mentioned in post #25.

The logs are 5 months old.

If you're no longer having problems you can consider preventative maintenance.

They had displayed many entries related to drives.

These can be tested as per post #22.



Steps 1 - 11 can be performed with this new script:
Tuneup.bat

Code:

Event[5000]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5001]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5002]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5003]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5004]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5005]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.


Event[5007]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5008]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5009]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5010]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5011]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5012]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5013]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5014]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5015]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5016]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.398
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5017]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.414
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Event[5018]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:31.414
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Code:

Event[5006]:
  Log Name: System
  Source: disk
  Date: 2020-03-25T20:08:29.933
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OFFICE64
  Description: 
The IO operation at logical block address 0x39a0 for Disk 7 (PDO name: \Device\000000dc) was retried.

Code:

Event[3941]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2020-03-17T09:43:28.724
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: OFFICE64
  Description: 
Windows failed fast startup with error status 0xC0000411.