[SOLVED] Browser Crashes when Printing. FIX: I reset Chrome to its original settings.

J

joferder

Member
Joined
Dec 12, 2020
Posts
11
I'm not sure if this is the right place to put this, but here we go...For the last month or so my computer will close what ever browser I'm using (typically Chrome or Firefox) any time I try to print. I have checked numerous times to ensure that both of the browsers are up-to-date. I completely uninstalled the printer and reinstalled. I have check windows updates and done all of the updates. Even after all of this, the problem persists. It is driving me crazy because I can't print. I have run and attached the Synsative File Collection App file.

Here is a little more information about the machine I'm using:

· OS - Windows 10 (originally pre-installed on laptop)
· x64
· Approximate age of system (hardware) - 3 years
· Approximate age of OS installation - 3 years
· Have you re-installed the OS? - No
· CPU - Intel Core i5
· Video Card - Intel UHD Graphics 620
· System Manufacturer - HP
· Exact model number - 17-by0062cl
Laptop or Desktop? - Laptop

Any help or advice would be greatly appreicated. This is driving me nuts.

John F
 

Attachments

x BlueRobot said:
Does this only happen when trying to print from the browser?
Click to expand...
Yes. If I print from Adobe Reader or MS Word, that seems to work just fine. I also tested it again in Edge (I never use it, so I haven't had a reason to try it up to this point) and that seems to print fine., but otherwise Chrome and Firefox both close immediately.
 
!) 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

2) 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


3) Open administrative command prompt and type or copy and paste:
chkdsk /b /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


4) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


5) Open administrative command prompt (ACP) and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /scanhealth
8) dism /online /cleanup-image /restorehealth
9) sfc /scannow
10) wmic recoveros set autoreboot = false
11) wmic recoveros set DebugInfoType = 7
12) wmic recoveros get autoreboot
13) wmic recoveros get DebugInfoType
14) bcdedit /enum {badmemory}

15) 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


Code: 
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 474.2 GB
Total Space: 937.7 GB
File System: NTFS
      Model: Intel Optane+932GBHDD

      Drive: D:
 Free Space: 1.8 GB
Total Space: 14.9 GB
File System: NTFS
      Model: Intel Optane+932GBHDD

      Drive: F:
 Free Space: 3050.9 GB
Total Space: 3815.4 GB
File System: NTFS
      Model: WD easystore 25FA USB Device

      Drive: G:
 Free Space: 164.7 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WD Elements 10B8 USB Device
 
Here is step 1. The Health tab was blank for some reason. I couldn't find anything that would force it to do anything with that tab. I will work on those other steps in the morning.

1607825937996.png 1607837402410.png1607837430106.png
 
Run Crystal Disk standard edition:
CrystalDiskInfo
Post images into the thread.


Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of








Code: 
Event[1793]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9910000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1794]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9910000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1795]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9910000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1796]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9910000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1797]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9900000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1798]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9900000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1799]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9890000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1800]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9890000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1801]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9860000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1802]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1803]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1804]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.9390000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1805]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8940000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1806]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8940000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1807]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8930000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1808]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8470000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1809]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8470000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1810]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8460000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1811]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8020000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.

Event[1812]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T22:31:58.8020000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The device, \Device\Harddisk0\DR0, has a bad block.




Code: 
Event[59]:
  Log Name: System
  Source: disk
  Date: 2020-12-11T22:01:14.7050000Z
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The driver detected a controller error on \Device\Harddisk1\DR1.



Code: 
Event[1433]:
  Log Name: System
  Source: disk
  Date: 2020-11-27T09:40:28.7200000Z
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The driver detected a controller error on \Device\Harddisk2\DR2.



Code: 
Event[1783]:
  Log Name: System
  Source: disk
  Date: 2020-11-20T23:09:33.5240000Z
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The driver detected a controller error on \Device\Harddisk1\DR3.



Code: 
Event[1936]:
  Log Name: System
  Source: disk
  Date: 2020-11-19T21:39:10.7730000Z
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description:
The driver detected a controller error on \Device\Harddisk2\DR2.
 
joferder said:
Yes. If I print from Adobe Reader or MS Word, that seems to work just fine. I also tested it again in Edge (I never use it, so I haven't had a reason to try it up to this point) and that seems to print fine., but otherwise Chrome and Firefox both close immediately.
Click to expand...

This seems like an application specific issue. I would suggest downloading Process Monitor and then gathering a stack trace to see what is happening at the time of the crash. The following example should provide some guidance on how to save and export a trace - How to Use Process Monitor to Track Registry and File System Changes
 
Code: 
Event[405]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2020-12-10T16:43:17.2410000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description: 
Fault bucket 1241961822784231833, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: chrome.exe
P2: 87.0.4280.88
P3: 5fc6dfae
P4: 46c3
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF59D.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_chrome.exe_20d2c20ec12a82f99aefd73255818c56b142a_d9c0f5c1_0d69ba4c-b273-4ed3-be51-579f4c6ca70b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5697e886-2b25-40eb-8f89-6b9b59010994
Report Status: 268435456
Hashed bucket: 864f4b6017f6e747713c55b297a69999
Cab Guid: 0

Event[406]:
  Log Name: Application
  Source: Application Hang
  Date: 2020-12-10T16:43:15.8650000Z
  Event ID: 1002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description: 
The program chrome.exe version 87.0.4280.88 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 2d1c
 Start Time: 01d6cebac2e3d49b
 Termination Time: 4294967295
 Application Path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
 Report Id: 5697e886-2b25-40eb-8f89-6b9b59010994
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Top level window is idle

Code: 
Event[407]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2020-12-10T16:43:15.8510000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LAPTOP-JLLU8AML
  Description: 
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: chrome.exe
P2: 87.0.4280.88
P3: 5fc6dfae
P4: 46c3
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_chrome.exe_20d2c20ec12a82f99aefd73255818c56b142a_d9c0f5c1_0d69ba4c-b273-4ed3-be51-579f4c6ca70b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5697e886-2b25-40eb-8f89-6b9b59010994
Report Status: 4
Hashed bucket: 
Cab Guid: 0

The application logs for future reference.
 
I finished steps 3 and 4 above (finally). When I tried to get the log info from the "chkdsk /b /v" it was completely empty. I did run into a problem when I ran the scan, the computer didn't seem to want to start back up, so I'm wondering if that wasn't part of the problem with the missing log. "sfc /scannow" is the next step.
 
Here are steps 5 through 15:
Code: 
Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.685

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.685

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\LAPTOP-JLLU8AML\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LAPTOP-JLLU8AML\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}

C:\WINDOWS\system32>
 
I've made some progress on this... I ran a registry cleaner and afterwards I was able to print from Firefox. I then tried printing again from Chrome (my primary browser), but it crashed again instantly. I then decided to try deactivating all of my extensions. After doing so, I was able to print again. I then decided to re-add my extensions one-by-one, but as soon as I added back the first one (ad blocker) the problem started again. I disabled it again and enabled the next one and tried printing again, but Chrome crashed again. I repeated this a couple of times with different extensions and the same results each time. I'm not sure if that clears anything up or complicates anything.
 
joferder said:
I ran a registry cleaner and afterwards I was able to print from Firefox.
Click to expand...
I would suggest staying away from registry cleaners unless you're absolutely sure you know what they're removing.

joferder said:
I then decided to try deactivating all of my extensions. After doing so, I was able to print again.
Click to expand...
Could you please gather a trace if possible? I want to see if we can find out why those extensions are crashing Chrome.

Browser Crashes when Printing

As a quick test, you may want to try a different Chromium-based browser like Brave and then install the extensions to see if that browser remains stable. Brave comes with ad-blocking built into the browser itself.
 
Have you tried the extensions in a different browser or got a trace yet? This isn't a disk-related issue, it seems that it's specific to those extensions and/or browser.
 
x BlueRobot said:
Have you tried the extensions in a different browser or got a trace yet? This isn't a disk-related issue, it seems that it's specific to those extensions and/or browser.
Click to expand...
I did not have a chance to try the extensions in a different browser or get the trace, but I think I did manage to resolve this problem now. I completely reset Chrome back to it's original settings and then logged back into my account. At that point all of the extensions turned back on (except Ad Block, but I added that back in manually) and I am able to get to the print screen without it crashing. I have tried it several times and it has worked each time.

I would like to thank both of you for your help with this. I have learned a few helpful things.

John F
 
Glad you were able to get the issue resolved, I wonder if you had a corrupt user profile or something similar? I've marked the thread as solved for now. Please let us if you begin to experience any issues again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top