Since update on 19 Jan 2019, I get page file error on boot

**Sailindawg** · 3 Weeks Ago

eLPuSHeR said:

Another idea:

Put one small static swapfile on C (minimum size allowed).
Put another one on the drive you were previously using.

Already tried. I posted that attempt in earlier thread post. The problem is that windows will not recognize a page file on a different drive. Something is broke. I want to fix it if possible.

**Sailindawg** · 3 Weeks Ago

zbook said:

There are log collectors that are used in another forum.
Please run the BETA log collector and post a zip into this thread:
BSOD - Posting Instructions - Windows 10 Forums

Will do once I'm home from work tonight.

Thank you.

**Sailindawg** · 3 Weeks Ago

Here you are. Many thanks for taking a look here.

**zbook** · 3 Weeks Ago

The computer has been having multiple BSOD.
The first one seen in the logs was on 1/5/2019.

The bugchecks were:
133
1E

When there are BSOD Windows will create memory and mini dumps.

The drive has insufficient free space.
The Windows default setting is to delete memory dumps when the free space is < 25 GB.

There were multiple logs indicating that there were pop ups displaying: Out of Virtual Memory

The log collector was not able to find any mini or memory dumps.

Perform the following steps:

1) During the troubleshooting process free up 18 to 19 GB on the Windows drive so that the total free space is approximately 30 GB. A minimum of 25 GB is needed so that the memory dump files are not deleted. Additional space is needed for the size of the memory dump file.

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

3) Uninstall MSI Afterburner

4) Make sure that there is no overclocking during the troubleshooting process

5) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums | Tutorials
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.)

6) Open administrative command prompt and type or copy and paste:
7) sfc /scannow
8) dism /online /cleanup-image /restorehealth
9) chkdsk /scan
10) wmic RecoverOS set AutoReboot = False
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

12) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. P2.00, 7/29/2011

13) Check to see if this is the most up to date version.
14) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.
15) To ensure that there are no improper bios settings please reset the bios.
16) Sometimes there can be failure to boot after resetting the bios.
17) Backup the computer files to another drive or to the cloud.
18) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

19) Create a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials

How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

20) After posting the results for the above steps there may be some modifications.
The computer should then be optimally setup to create dump files for BSOD.
If there are no spontaneous BSOD a tool can be used to stress drivers and find misbehaving drivers.
Then the mini and memory dump files can be debugged to find the misbehaving drivers or malfunctioning hardware.

21) If there are any problems posting images into the thread please use share links: one drive, drop box, or google drive

22) After any BSOD:
a) Run the BETA log collector and post a new zip into the thread
b) Open file explorer > this PC > C: > in the right upper corner search or C:\windows\memory.dmp

23) It can be easy to miss bsod when startup and recovery system failure automatically restart is checked.
An earlier command in this post will modify this setting so that automatically restart is unchecked.
When there is a bsod you should now see a bsod window with bugcheck and : (
Sometimes you may see a misbehaving driver in the form *.sys
At the very beginning of a bsod you may see a % counter.
If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

24) After the BSOD troubleshoot has completed use some of the steps in this link to manage the free space on the Windows drive:
Free Up Drive Space in Windows 10 | Tutorials

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 11.6 GB
Total Space: 59.7 GB
File System: NTFS
      Model: C300-CTFDDAC064MAG

      Drive: E:
 Free Space: 15.8 GB
Total Space: 38.2 GB
File System: NTFS
      Model: INTEL SSDSA2M040G2GC

      Drive: F:
 Free Space: 115.3 GB
Total Space: 476.8 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 500GB

      Drive: G:
 Free Space: 56.6 GB
Total Space: 109.0 GB
File System: NTFS
      Model: WDC WD5000AAKS-00TMA0

      Drive: H:
 Free Space: 0.4 GB
Total Space: 61.0 GB
File System: NTFS
      Model: WDC WD5000AAKS-00TMA0

      Drive: I:
 Free Space: 24.4 GB
Total Space: 166.9 GB
File System: NTFS
      Model: WDC WD5000AAKS-00TMA0

      Drive: J:
 Free Space: 14.0 GB
Total Space: 140.0 GB
File System: NTFS
      Model: WDC WD5000AAKS-00TMA0

      Drive: O:
 Free Space: 689.1 GB
Total Space: 953.9 GB
File System: NTFS
      Model: Samsung SSD 860 EVO 1TB

      Drive: D:
      Model: ATAPI iHAS220   6 SCSI CdRom Device
     Driver: c:\windows\system32\drivers\cdrom.sys, 10.00.17134.0137 (English), 9/7/2018 23:57:38, 159744 bytes

Code:

1/5/2019 8:10 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff803ea25e378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\010519-42875-01.dmp
\\?\C:\WINDOWS\TEMP\WER-43281-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9DA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9FA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA18.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA38.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_edea858e95288c2d721cf44265b44b47132ecd9_00000000_cab_0f40bab4

Analysis symbol: 
Rechecking for solution: 0
Report Id: aaf0bb81-8812-430a-9733-5d5c986d9a3b
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
1/5/2019 8:10 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff803ea25e378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\010519-42875-01.dmp
\\?\C:\WINDOWS\TEMP\WER-43281-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9DA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9FA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA18.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA38.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_edea858e95288c2d721cf44265b44b47132ecd9_00000000_034cba37

Analysis symbol: 
Rechecking for solution: 0
Report Id: aaf0bb81-8812-430a-9733-5d5c986d9a3b
Report Status: 4
Hashed bucket: 
Cab Guid: 0
1/18/2019 12:03 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff802a6fc67c9
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\011719-64437-01.dmp
\\?\C:\WINDOWS\TEMP\WER-68375-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F4A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F6B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FC8.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_27acba2a8be0797fd27075faa12a9d7aa2ff8d74_00000000_cab_37292064

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0fa7251d-3232-4c57-9140-429fdd781ff9
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
1/18/2019 12:03 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff802a6fc67c9
P4: 0
P5: ffffffffffffffff
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\011719-64437-01.dmp
\\?\C:\WINDOWS\TEMP\WER-68375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F4A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F6B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FC8.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_27acba2a8be0797fd27075faa12a9d7aa2ff8d74_00000000_034d1fd7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0fa7251d-3232-4c57-9140-429fdd781ff9
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Event[2543]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-01-17T19:03:44.712
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-6OOMNU2
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff802a6fc67c9, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0fa7251d-3232-4c57-9140-429fdd781ff9.

Event[2545]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-01-17T19:03:50.069
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-6OOMNU2
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.



Event[6313]:
  Log Name: System
  Source: Application Popup
  Date: 2019-01-21T08:54:32.007
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. 






Event[6314]:
  Log Name: System
  Source: Microsoft-Windows-Resource-Exhaustion-Detector
  Date: 2019-01-21T08:54:33.009
  Event ID: 2004
  Task: Resource Exhaustion Diagnosis Events
  Level: Warning
  Opcode: Contains the results of the diagnosis.
  Keyword: Events related to exhaustion of system commit limit (virtual memory).
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: InsurgencyClient-Win64-Shipping.exe (9432) consumed 10207768576 bytes, firefox.exe (4204) consumed 467517440 bytes, and firefox.exe (9232) consumed 286756864 bytes.







Event[6421]:
  Log Name: System
  Source: Microsoft-Windows-Resource-Exhaustion-Detector
  Date: 2019-01-21T09:52:12.233
  Event ID: 2004
  Task: Resource Exhaustion Diagnosis Events
  Level: Warning
  Opcode: Contains the results of the diagnosis.
  Keyword: Events related to exhaustion of system commit limit (virtual memory).
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: InsurgencyClient-Win64-Shipping.exe (3212) consumed 12881244160 bytes, MBAMService.exe (3880) consumed 215941120 bytes, and MsMpEng.exe (4028) consumed 171823104 bytes.

Event[6422]:
  Log Name: System
  Source: Application Popup
  Date: 2019-01-21T09:52:45.262
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. 



Event[6741]:
  Log Name: System
  Source: Microsoft-Windows-Resource-Exhaustion-Detector
  Date: 2019-01-21T10:14:08.022
  Event ID: 2004
  Task: Resource Exhaustion Diagnosis Events
  Level: Warning
  Opcode: Contains the results of the diagnosis.
  Keyword: Events related to exhaustion of system commit limit (virtual memory).
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: InsurgencyClient-Win64-Shipping.exe (7044) consumed 12270727168 bytes, MBAMService.exe (3620) consumed 171438080 bytes, and MsMpEng.exe (3888) consumed 168116224 bytes.

Event[6742]:
  Log Name: System
  Source: Application Popup
  Date: 2019-01-21T10:14:24.232
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. 


Event[8043]:
  Log Name: System
  Source: Microsoft-Windows-Resource-Exhaustion-Detector
  Date: 2019-01-21T20:24:57.891
  Event ID: 2004
  Task: Resource Exhaustion Diagnosis Events
  Level: Warning
  Opcode: Contains the results of the diagnosis.
  Keyword: Events related to exhaustion of system commit limit (virtual memory).
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: InsurgencyClient-Win64-Shipping.exe (244) consumed 14067159040 bytes, MBAMService.exe (3716) consumed 175452160 bytes, and MsMpEng.exe (3472) consumed 161075200 bytes.

Event[8044]:
  Log Name: System
  Source: Application Popup
  Date: 2019-01-21T20:27:05.673
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-6OOMNU2
  Description: 
Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

**Sailindawg** · 3 Weeks Ago

Thanks for the analysis. Your first point about the windows drive, it's too small. I need to clone it to a larger drive. I was getting away with a smaller drive for a number of years. Those days are over.

The system is probably about 7 years old. The cpu is a 2600K that I bought new when Intel issued that cpu. The motherboard is the same age. I think it's time I finally rebuild my system.

**eLPuSHeR** · 3 Weeks Ago

I have found out that Windows default manage pagefiles for all drives doesn't work fine when you have several drives. I have got an SSD as primary system drive and an older slow SATA II drive as data drive. If I left pagefile settings at default, Windows creates a 8GB pagefile on the slower SATA II drive instead of the SSD (which has got enough free space). I am not interested in memory dumps so I am forcing a static 1GB swap on the SSD. I haven't run into any issues.

Also, there should be an option to RESET pagefile size calculation. Having a pagefile size as big as main RAM is absurd, unless you are having issues and want to analyse memory dumps.

**lx07** · 3 Weeks Ago

eLPuSHeR said:

Also, there should be an option to RESET pagefile size calculation.

You can set it to manual size (say 400MB) and reboot. Then set it back to system managed and reboot.

This resets to recommended size - otherwise it seems it never shrinks after requiring a larger size in the past so it just grows and grows.

**Sailindawg** · 3 Weeks Ago

Regarding page file size, I enjoy gaming AAA title games. Have enjoyed it for over 10 years. I set my machines up to run 3D apps very well. Most 3D apps want a page file. Even now with 16 G system RAM and higher. Back when there was only mechanical hard drives, the I/O latency was real and much higher than now. Something simple like putting the page file on another drive, not the C:/ drive allowed for better throughput of I/O process. 3D games proved this out by playing more smoothly, rather than choppy or laggy.

However, that's all changed now with the new cpu's having the memory controller, pci slot controller and HD controller all on die with the CPU. Add in SSD's instead of mechanical hard drives. The I/O latency has been greatly reduced because of innovation within the technology.

I'm thinking that the old strategy of placing a page file on a separate disk may be over.

Reading over the analysis of my system files, number 1 is my OS SSD is pretty much out of capacity. Win 10 wants to see at least 25G extra capacity in reserve on the OS drive! Back in previous versions of earlier windows a 60G OS hard drive was plenty. As I speak, Win 10 occupies 46 G of my OS hard drive. That's a lot of space to take up. I don't run hibernate or keep the system on sleep or standby. So no hibersys file taking up more space.

I need to upgrade my system! It's tried, true & still kicks ass, but Windows is leaving it behind. Too bad.

**Sailindawg** · 3 Weeks Ago

eLPuSHeR said:

I have found out that Windows default manage pagefiles for all drives doesn't work fine when you have several drives. I have got an SSD as primary system drive and an older slow SATA II drive as data drive. If I left pagefile settings at default, Windows creates a 8GB pagefile on the slower SATA II drive instead of the SSD (which has got enough free space). I am not interested in memory dumps so I am forcing a static 1GB swap on the SSD. I haven't run into any issues.

Also, there should be an option to RESET pagefile size calculation. Having a pagefile size as big as main RAM is absurd, unless you are having issues and want to analyse memory dumps.

The rule of thumb for a page used to be something like 1/3 of your total system RAM should be set aside for your page file. A static page file generally kept Windows from over managing the page file and wasting cpu cycles.

A good 3D game today will kick out a memory error if one tries to run a 1G page file, even with 16G system RAM and a vid card with 8G video RAM.

If you don't play 3D vid games or run intensive 3D apps, you will never see this page file error because you are not taxing the system resources hard enough.

**eLPuSHeR** · 3 Weeks Ago

I play 3D games and I have no issues with 1GB pagefile. I guess it depends on what games.

Since update on 19 Jan 2019, I get page file error on boot

Posting Permissions