How to save google DOC as a PDF

There is various Blue Screen of Death errors that you can encounter as you use your Windows 10 computer and some of these Stop errors have something to do with the win32kbase.sys file. This post will guide you in fixing the BSOD errors related to the win32kbase.sys file.

• A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Win32kbase.sys.
• Your PC ran into a problem and needs to restart. If you would like to know more, you can search online later for this error: win32kbase.sys.
• SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – win32kbase.sys
• STOP 0x0000001E:

KMODE_EXCEPTION_NOT_HANDLED – win32kbase.sys

• STOP 0×00000050:

PAGE_FAULT_IN_NONPAGED_AREA – win32kbase.sys

The win32kbase.sys file is a Windows operating system Base Win32 Kernel Driver file located in the System32 folder so if it ends up getting corrupted or if it went missing, your computer will throw up Blue Screen error. To fix BSOD errors that have something to do with the win32kbase.sys file, here are some possible fixes that could help. Worry not for these possible fixes are not complicated.

Option 1 – Run the Check Disk or CHDSK utility

One of the first things you can try to resolve the win32kbase.sys Blue Screen error is running the CHKDSK utility. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f C:

• Wait for the process to be completed and then restart your computer.

Option 2 – Run SFC or System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Restart your PC.

Option 3 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the win32kbase.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing Blue Screen errors related to the win32kbase.sys file. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

There are a lot of users who use their Windows 10 PCs to create and access data on their servers using their network. However, some of them reported getting an error saying that the server is not accessible. Here’s the full content of the error message:

“\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect.”

If you are among the users who experience the same issue, read on as this post will help you resolve this error when accessing your server. But before you start troubleshooting the problem, you might want to perform System Restore, especially if tend to create one. To use System Restore, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the ACPI.sys Blue Screen error now’s the time for you to make use of the potential fixes laid out below.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try checking the status of the Workstation Service

You might want to check the status of the Workstation Service as the error might have something to do with it.

• Tap the Win + R keys on your keyboard to launch the Run utility.
• Then type “services.msc” in the field and click OK or hit Enter to open the Windows Services Manager.
• After opening the Services Manager, you will see a list of all the services on your computer and from there, locate the Workstation Service.
• Double click on the Workstation Service to open its Properties.
• Next, Stop the Service and Start it again or you can also right-click on it and select Restart and then make sure that its Startup type is set to Automatic.
• Now restart your computer and check if the error is fixed.

Option 3 – Try to change the File Sharing Connections setting

You can also try to change the File Sharing connections setting. All you have to do is go to Control Panel > Network and sharing center > Advanced sharing settings > File sharing connections. From there, you need to select “Enable file sharing for devices that use 40 or 56-bit encryption and check if it helps in fixing the problem. If not, undo the changes you’ve made and proceed to the next given option.

Option 4 – Try checking the Network Configuration

Checking the Network Configuration can also help you fix the error. Refer to the steps below to do so:

• Right-click on the Wi-Fi connection or on the Ethernet connection icon located in the system tray.
• Then select open Network and Internet Settings and then click on the “Change Adapter Options”.
• After that, a new window will appear and from there, select the network connection that connects your computer to your network – this can either be a Wi-Fi connection or Ethernet connection.
• Right-click on that connection and select Properties where you will see a list of items.
• Select the Internet Protocol Version 4 or Internet Protocol Version 6 from those items according to your system requirement.
• Then click on the Properties button.
• Check if everything is now configured as to how it is supposed to be and then check if the error is resolved.

Option 5 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 6 – Run the Network Adapter Troubleshooter

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

A newfound bug in Google docs is causing it to crush and upon reopening it will crush again making it very difficult to re-access your document. The bug is manifested when a series of the same word is typed into a document and Show grammar suggestion is turned on.

How was it found

A Google Docs user, Pat Needham brought up the issue on Google Docs Editors Help forum.

"I've only tried in Google Chrome, with documents from three separate Google accounts (personal, G Suite Basic, and work one which might be enterprise). All three experience this same issue".

"It's case-sensitive. So trying with 'and. and. And. and. And.' doesn't cause it to crash."

While Needham publicly reported the bug, it appears that the issue was discovered by Eliza Callahan who was writing a poem novel for her novel using Google Docs.

Needham's findings have also been confirmed by other users running Firefox 99.0.1

Another user, Sergii Dymchenko, said strings like "But. But. But. But. But." triggered the same response. Some also noticed putting any of the terms like "Also, Therefore, And, Anyway, But, Who, Why, Besides, However," in the same format achieved the outcome.

A YCombinator HackerNews reader suspected the cause to be the "Show grammar suggestion" option in Google Docs.

A Google spokesperson confirmed the presence of the issue adding, "we're aware of this issue and the team is working on a fix."

How to recover your document

First thing first, turn off Show grammar suggestions so you do not run into issue by accident. In order to turn it off go to Tools and then into Spelling and grammar and untick Show grammar suggestions.

Now, if you already have a document that has been crushed, fear not because there is a workaround to access it. For some strange reason this bug does not manifest on Google Docs mobile app, so you can open the crushed document in the mobile app, delete words that have caused the bug and reopen the document on your desktop.

Until Google comes up with the solution this is currently the only way to address the issue.

Error Code 22 - What is it?

Code 22 is a type of Device Manager Error code. Device manager errors are reported by the drivers causing the problem. It indicates that the devices are disabled in the Device Manager. This error code is displayed in the following format:

This device is disabled. (Code 22)

It looks like a very simple matter to enable a device from the Device Manager interface but if the device fails to load then there are likely greater underlying problems with the drivers. Drivers allow hardware devices to communicate with other hardware devices and the operating system. Drivers contain instructions and operating procedures for devices. Without a driver, a hardware device will not function and may not even appear in the Device Manager.

Solution

Error Causes

Common causes of error code 22 are:

• Device is disabled
• Driver is outdated
• The driver is missing or corrupt
• The previous attempt to update the driver failed
• Device is damaged
• The device is not configured as the default device

This means that though the error code 22 typically indicates that the device reporting the error is disabled but other causes can also be associated with the error occurrence.

Further Information and Manual Repair

Here are some of the best and easy do-it-yourself methods to resolve error 22 on your PC. Try these methods to repair the issue.

Method 1

If the error code 22 is triggered due to a disabled device, then all you need to do to resolve the issue is enable the device. To enable the disabled device, follow these steps. Simply go to the start menu and type Device Manager in the search bar. Now click on the Device Manager and then click Actions. After you Click Actions, double click Enable Device. The Enable Device Wizard will pop up. Follow all the prompts from the Enable Device Wizard. This will hopefully resolve the issue.

Method 2

If method 1 doesn’t work then this means the problem is deeper than you think.  The problem can be triggered by the missing, corrupted, or outdated driver for the device reporting the error. In such a situation it is advisable to reinstall the driver for the device. To do this first uninstall the driver for the device reporting error code 22 then reinstall the driver.

• For this simply click the Start menu, go to the control panel and then click Performance and Maintenance, and then System.
• In the new window, you will then see a tab called Hardware and the Device Manager.
• Double click on the device whose driver you need to uninstall.
• Click on the properties window with a tab marked driver. Then click on the driver you want to uninstall.

To activate changes reboot your PC. Now reinstall the latest and updated version of the driver uninstalled using the Plug and Play feature.

Method 3

Sometimes devices can also get damaged due to registry issues. In such an event, install Restoro. It is a PC Fixer deployed with a registry cleaner. The registry cleaner wipes out all the unnecessary and obsolete files damaging the registry and repairs them in a few minutes. Click here to download Restoro.

If you have a BlueTooth device on your computer, you know that each time you need to receive or transfer the file you need to find the icon in the system tray, right-click on it and choose the desired option. But there is a simpler solution, create a Bluetooth icon on the desktop so it is always easy to access. Open File Explorer by pressing ⊞ WINDOWS + E Go to C:\Windows\System32 Find fsquirt.exe Right-click on it and choose copy Go to the desktop and right-click, choose paste Rename the file to Bluetooth And, you are done!

Error 0x80004005 - What is it?

Error 0x80004005 is a typical Outlook error. This error code occurs either when sending emails or receiving them. The error message may be displayed in either of the following formats:

‘Sending and receiving reported error "0x80004005": The operation failed.’ ‘This message could not be sent. Try sending the message again or contact your network administrator. The client operation failed. Error is [OX80004005- 0X0004B9-OXOO501].’

Error Causes

There are several causes for the error 0x80004005 such as:

• The Script Blocking Feature Enabled While Using Norton Antivirus
• Spyware
• Viruses
• Registry problems-Missing or corrupt registry keys

It is advisable to repair and resolve error 0x80004005 immediately as it may cause a great deal of inconvenience to you. This error may hamper your ability to receive and send emails from your Outlook account and lower your productivity too as you may be unable to communicate with your peers.

Further Information and Manual Repair

To fix error 0x80004005, you don’t have to wait for the network personnel or be a technical expert yourself. This may be a critical error but the good news is that it is easy to resolve. Here are some effective methods and quick fixes to resolve the error 0x80004005 instantly.

Method 1: Disable Script Blocking Feature in Norton Antivirus

After installing Norton Antivirus on your PC, if you start experiencing the Outlook error 0x80004005, then the best way to resolve it is to simply disable the script blocking feature. However, the downside of this is that by disabling this feature your PC will become vulnerable to viruses and malware.

Method 2: Disable the New-Mail Notification Feature in MS Outlook

If you don’t have Norton Antivirus downloaded on your PC, then try method 2. This method involves disabling the new-mail notification feature in MS Outlook. The error code 0x80004005 is often resolved by switching off this feature. Try it to see if it works. To disable the new-mail feature all you have to do is open your Outlook account and then go to the Tools menu, then go to Options and then select the ‘Preferences’ tab. After that click on the ‘Emails Options’ tab and then simply uncheck the check-box against ‘Display a notification message when new mail arrives’. To confirm changes press OK.

Method 3: Scan for Viruses

The error 0x80004005 may also be triggered due to viral infection or spyware. Such malicious software enters your PC through phishing emails and while downloading files and attachments. You may not be aware of this but your PC may be infected by viruses. It is important you remove them immediately as they can expose you to serious risks including privacy issues, identity thefts, data breaches, and more.

Error Code 30088-26 is shown when the user tries to install the MS Office suite to their PC. It is mostly due to several reasons including corrupted Office installation, the remnant of old office installation, or even Windows updates. We will cover all reasons along with provided solutions to each one. Follow the guide below to address each scenario with the fix for it.

Corrupted Office installation

In order to fix this issue, you will need to repair the installation itself.

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in Control Panel
• In the control panel double click on Programs and features
• In the list of installed application find MS Office and click on it to select it
• On top, just above the application list click on the change
• Office dialog will be opened with multiple choices
• Click and select Online repair and then click on Repair
• Make sure that you have a stable internet connection and leave the process to be finished

Remnants of old office installation

Manually cleaning remnants of old office installation is not an easy task and it can be different from system to system depending on the previous Office version. Luckily Microsoft has a dedicated office cleaning tool made for purpose of removing old tails and remnants of old office installations.

• Download tool here
• After the tool has been successfully downloaded, double-click on the .diagcab file to open it
• Click on Advanced and make sure that the box associated with Apply repair automatically is checked.
• Click the Next button to proceed
• Wait until the initial detection phase is complete, then click on Installing at the first prompt
• Select the program that you’re encountering issues with (most likely Microsoft Office) and click Next once again
• At the next screen, click on Yes, try to uninstall
• Wait until the operation is complete, then restart your computer and re-install the Microsoft Office suite

Windows Updates

After digging and trying out various solutions for this issue we came to the conclusion that this error can occur if Windows is not fully updated, and by fully updated we mean fully, not just critical updates, but all available ones. Check-in your setting to see if there are some uninstalled or pending updates waiting to be installed and if that is the case install them all. After completely updating your Operating system error should vanish and you should be able to install Microsoft office without issues.

There are times when you upgrade or install Windows 10 on an old computer and the Aspect Ratio of the screen is in a mess. This issue occurs when a new Windows version does not support the GPU or the driver does not work in Windows 10. And in such cases, Windows uses a generic driver which does not support all the resolution as well as the correct aspect ratio. So in this post, you will be guided on how you can fix the issues with the screen aspect ratio in Windows 10. It could be that your screen has an aspect ratio of 16:9 but after the upgrade, you changed to screen resolution, and is now set to 16:!0. And later on, you found that you are unable to go back to the previous aspect ratio. Thus, you will notice that everything on the screen might look stretched. You might be wondering if it’s possible to change the aspect ratio in Windows 10 directly even if the GPU does not have the compatible driver, well it really isn’t. However there is another way to resolve the problem. Refer to the options given below to get started.

Option 1 – Try using the Compatibility Mode

The first thing you can do is to run the driver in a Compatibility Mode. Follow the steps below to do so:

• You need to download the driver and place it on your desktop.
• After that, right-click on it and select Properties.
• Next, switch to the Compatibility tab where you should see two options:
  • Compatibility troubleshooter, and let Windows figure out what works best for you. If it fails, follow the next.
  • Manually choose the version of Windows it was correctly working.
• You also have the option to change the DPI settings and see if that helps. Then click the Apply and OK buttons.
• Now right-click on the file and select the “Run as administrator” option to install. After that, you should now be able to change your screen aspect ratio to what you were using early on.

Note: If you have other programs that won’t work on the existing version of Windows, then make sure to run the program in a Compatibility mode.

Option 2 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job.

Option 3 – Update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

If you’ve tried resetting your Windows 10 computer using the Reset This PC option in order to restore your computer’s factory settings and the process suddenly fails for some reason and you got an error message instead stating, “There was a problem resetting your PC, No changes were made on your Windows 10 computer”, then this post might help you resolve the problem. Carefully follow each one of the options given below to resolve the “There was a problem resetting your PC error on Windows 10.

Option 1 – Try renaming the System and Software hive

• If you’re still able to boot to the desktop of your Windows 10 PC, open an elevated Command Prompt from the WinX menu.
• Now use the CD command and change the directory to Windows\System32\config folder. Simply type in the following command and hit Enter:

cd %windir%system32config

• After that, you have to rename the System and Software registry hives to “System.001” and “Software.001”, respectively. To do that, just type each one of the following commands and hit Enter after you type each of them.
  • ren system system.001
  • ren software software.001

On the other hand, if your Windows 10 PC isn’t able to boot to the desktop, you can just access Command Prompt from the Advanced Startup options or you can also boot into Sage Mode and open Command Prompt from there and then run the given commands above. Note: If you only want to use the Refresh your PC option, you must only rename System hive and not Software hive. On the other hand, if the Software hive is really corrupted, you might not be able to use the Refresh your PC option in such a case. Thus, you really need to rename the Software hive as well. Once you’ve renamed the Software hive, you won’t be able to use the Refresh your PC option but only the Reset your PC option.

• Type “exit” to close the Command Prompt and then restart your PC and try resetting your PC again.

Option 2 – Try to disable and re-enable the Windows Recovery Environment

If the first option didn’t help, you can try disabling the Windows Recovery Environment and then enable it back again. To configure a Windows Recovery Environment or Windows RE boot image and recovery options, you have to use the REAgentC.exe tool.

• Tap the Win + S key and type “REAgentC.exe” to open the REAgentC.exe tool.
• After that, type the following command and hit Enter to disable the Windows RE:

reagentc /disable

• After disabling the Windows RE, you need to enable it back by typing the following command:

reagentc /enable

Option 3 – Try to boot the USB recovery drive

If the two previous options failed, you need to try another workaround which is to boot to the USB recovery drive > Troubleshoot > Recover from a drive. From there, follow the on-screen instructions and you should be good to go.