New
#1
BSODs different errors, crash dump does not initialize/no dump files
Please forgive me for any formatting problems or lack of posting etiquette as this is my first post.
Hi All,
I am experiencing constant BSODs during different activities, although a higher percentage of them are when playing games (any game). The error codes vary from 'PAGE FAULT IN NON-PAGED AREA' to 'IRQL NOT LESS OR EQUAL' to 'BAD POOL HEADER' to ‘SYSTEM SERVICE EXCEPTION’. To compound this problem, no dump files are generated in the Minidump folder. During a BSOD the system freezes at the ‘Collecting data for crash dump’/’Initializing disk for crash dump’ stage.
The lack of dump files being created started at the beginning of the year and did not coincide with any major hardware. Since then, I have installed a new video card (ASUS Strix GTX1080)
I have run multiple passes of CHKDSK, SFC Scannow, memtest86, Malware Bytes, MSE etc. all coming back clean.
Startup and Recovery options are set up as follows:
System failure
- Write an event to the system log (checked)
- Automatically restart (unchecked)
Write debugging information
- Small memory dump (256KB)
Small dump directory
- %systemroot%\Minidump
- Overwrite any existing file (unchecked/grayed out)
For Virtual Memory, the settings are as follows:
- Automatically manage paging file size for all drives (unchecked)
- C: (System Managed)
- E: (None)
- F: (None)
Total paging file size for all drives
- Minimum allowed: 16 MB
- Recommended: 24541 MB
- Currently allocated: 16361 MB
I have tried multiple different option settings here based on information available on this forum and others such as Tom’s Hardware etc. For example, if I let the system automatically manage the page files, it sets it to drive E:, even though my Windows drive is drive C: (neither makes a difference as far as halting the crashes though).
My Windows drive (C: ) is 104.75 GB total, 89.30 GB used, and 15.45 GB free. Drives E: and F: have 60+ GB of space each.
I am really at a loss as to what the problem could, especially considering there is no significant event that I can remember that caused the sudden lack of dump files.
Last edited by Popples; 04 Jun 2017 at 05:13.