My Daily BSOD

Kazzandra · Nov 9, 2015

This Lenovo laptop has bluescreened regularly since I purchased it. I thought it was a hard drive error for a while but have since done multiple /f /r chkdsk runs, which I thought used to help, but doesn't seem to be helping anymore.

Attached is my zip file.

axe0 · Nov 9, 2015

Hi Kazzandra,

Welcome to the 8forums.

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.

Please make sure your Windows is up to date with the latest updates.
Please make a backup BEFORE proceeding!

It looks like the pagefile has been corrupted, there are a few methods for fixing this. I would prefer method 1 because if any other system corruption is on the system it will be taken care of too.

Code:

ADDITIONAL_DEBUG_TEXT:  [COLOR="#FF0000"]Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original data written.This indicates the data was corrupted by the storage stack, or device hardware[/COLOR].

Method 1

Diagnostics Test

System File Check

Please try following:

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Method 2
Disable pagefile, reboot, enable it and let the system handle it, reboot again.
please read the tutorial below carefully for how to change the pagefile settings.
Virtual Memory Paging File - Change

Kazzandra · Nov 9, 2015

Here is the SFC log. The message was that it found corrupt files but was unable to fix some of them. Thank you very much for your effort so far and thank you in advance for the analysis. As this issue has been remedied before by check disk and has reappeared twice without any seeming relation, I'd like to get to what is causing it instead of just knowing how to fix it in a time-consuming manner,

CBS

Mysers Briggs · Nov 16, 2015

axe0 said:
It looks like the pagefile has been corrupted, there are a few methods for fixing this. I would prefer method 1 because if any other system corruption is on the system it will be taken care of too.

Code:

ADDITIONAL_DEBUG_TEXT: [COLOR=#FF0000]Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original data written.This indicates the data was corrupted by the storage stack, or device hardware[/COLOR].

You don't fix corruptions on the page file, because the page file is just an additional way of storing more data in memory, temporarily. It allows for a larger working set to reside in memory, while other data is paged to disk for use another time.
As a result, the data is temporary, so you don't "fix it".

Code:

0: kd> !pte fffff6e000929140                                           VA ffffc00125228000
PXE at FFFFF6FB7DBEDC00    PPE at FFFFF6FB7DB80020    PDE at FFFFF6FB70004948    PTE at FFFFF6E000929140
contains 000000000360F863  contains 000000000358E863  contains 000000020E1A0863  contains 0000000251795880
pfn 360f      ---DA--KWEV  pfn 358e      ---DA--KWEV  pfn 20e1a0    ---DA--KWEV  not valid
                                                                                  Transition: 251795 //Transition page to be placed onto the page file
                                                                                  Protect: 4 - ReadWrite

0: kd> !address ffffc00125228000
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...




Usage:                  
Base Address:           ffff8000`00000000
End Address:            fffff680`00000000
Region Size:            00007680`00000000
VA Type:                <unknown>

0: kd> !error ffffffffc000003f
Error code: (NTSTATUS) 0xc000003f (3221225535) - {Bad CRC}  A cyclic redundancy check (CRC) checksum error occurred.

Search: READ_PVOID error 
Search: READ_ULONG error 
Search error: cannot allocate system memory descriptor

You'll not find much with a minidump like this.
It hasn't saved much, of course. So finding which thread the address belonged to is pretty much impossible.

However, looking at the page in play, the pte is in fact valid, so I do not believe that is the cause.
Judging by the CRC check failure, and bad blocks detected with check disk, I'm positive this is a failing drive.

Have you tried testing the drive?
SeaTools is a good start.

Kazzandra · Nov 16, 2015

Yeah, I was aware that you can't 'fix' a page file, but I was hoping maybe it would fix the way it was committing the items. As far as it being a failing drive, the usual built-in tests haven't showed anything, but I'll test it with Seatools.

As a follow-up, I disabled the page file, and had a bluescreen while it was disabled (the usual behaviour is that it does so while I'm asleep-- perhaps a power setting I need to disable, too). I haven't checked, but I'm pretty sure it was the same one. I've since recreated the page file, and so far, have not had another bluescreen (fingers crossed).

I'll update if it reoocurs and let you know if Seatools reports a drive issue.

Mysers Briggs · Nov 16, 2015

If it passes, upload a larger memory dump to a file sharing site.
It will be located in C:\Windows\MEMORY.dmp

Kazzandra · Dec 12, 2015

Hello all,

Just thought I'd update. The drive does pass all tests in Seatools; however, it needs check disked very often, and I do see a pattern to the sectors with the wrong index file (all relate to the same sector).
Furthermore, this is a Lenovo Y50-70 laptop, and Nvidia has neglected the 860M graphics card inside, leaving us with either graphics driver failures or a several month old driver.
I decided to upgrade to 10 now that games are mostly all compatabile with 10s core.
....
And now my bluescreen has changed to Kernal_Security_Check_Failure. So something is still going on. I guess now I'll need to go to the Windows 10 forum, lol.

Edit: After reading about Driver verifier, I thought I'd try it out. After turning it on, I failed on boot with IOBit's Smart Defrag. Not sure if there is all there is to it, but it's uninstalled now, after a harrowing system restore due to the inability to boot because of Driver verifier.

My Daily BSOD

Kazzandra

New Member

My Computer

System One

axe0

BSOD Analyst & Security Analyst

System File Check

My Computer

System One

Kazzandra

New Member

My Computer

System One

Mysers Briggs

Member

My Computer

System One

Kazzandra

New Member

My Computer

System One

Mysers Briggs

Member

My Computer

System One

Kazzandra

New Member

My Computer

System One