BSOD after updating windows


Joined
Aug 14, 2014
Messages
5
Reaction score
0
Everytime I try to update windows with the latest batch (the ones that were posted on August 12, 2014) my computer will BSOD after restarting once the drivers are fully installed (meaning, one restart to finish installing the files). The BSOD states, "page fault in non paged area". I'm only able to get back into windows by using a restore point before the updates were installed but then windows wants me to try to download and install them again after a short while. I'm using Windows 7 professional. Here's the minidump info:

I also found this article after doing some research: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/blue-screen-stop-0x50-after-applying-update/6da4d264-02d8-458e-89e2-a78fe68766fd
 

Attachments

Last edited:
Ad

Advertisements

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Hi,

A PAGE_FAULT_IN_NONPAGED_AREA *typically* means that it tried to access information in the page file and it either wasn't there or was corrupted.

Code:
System Uptime: 0 days 0:00:06.647
Probably caused by : win32k.sys ( win32k!bLoadFontFile+1f3 )
BugCheck 50, {fffff901c06575cc, 0, fffff9600008cca3, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments:
Arg1: fffff901c06575cc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600008cca3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR: 0x50
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_0x50_win32k!bLoadFontFile+1f3
Lets start by running chkdsk (Windows Check Disk).
  1. Click on the Start button and type in cmd.
  2. In the list you will see cmd.exe.
  3. Right click on Cmd.exe and select "Run as Administrator"
  4. Type in the following chkdsk /r /f (See the image below)
  5. Type in Y and press enter.
  6. Reboot your computer. On the restart chkdsk will check the hard disk for errors.
  7. There will be an event logged.
Event Viewer
  1. Press the Windows Key + R and type in eventvwr
  2. In Event Viewer click on Windows Logs -> Application.
  3. Right click on "Application" and select "Find"
  4. Type in "chkdsk" (without the quotes)
  5. When it finds the event, right click on the event and select Copy -> "Copy Details as Text" and paste it to the forum.


Any questions, please don't hesitate to ask.
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Just so you know, the reason that one of the post's asked about AV (Anti-virus) software, is because AV Software, can and does, become over zealous and cause problems.

A typical fault finding step would be to disable or uninstall AV software prior to installing the patch's from Microsoft.

That would be one of the few times you would disable AV software.
 
Joined
Aug 14, 2014
Messages
5
Reaction score
0
I use microsoft security essentials, nothing else for anti virus. Here's the text from the event log after running chkdsk:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 8/13/2014 9:46:16 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Moo
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Moo.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
182784 file records processed.

File verification completed.
689 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
243878 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
182784 file SDs/SIDs processed.

Cleaning up 2326 unused index entries from index $SII of file 0x9.
Cleaning up 2326 unused index entries from index $SDH of file 0x9.
Cleaning up 2326 unused security descriptors.
CHKDSK is compacting the security descriptor stream
30548 data files processed.

CHKDSK is verifying Usn Journal...
35491152 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
182768 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
35242636 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

234195967 KB total disk space.
92849412 KB in 122068 files.
83848 KB in 30551 indexes.
0 KB in bad sectors.
292159 KB in use by the system.
65536 KB occupied by the log file.
140970548 KB available on disk.

4096 bytes in each allocation unit.
58548991 total allocation units on disk.
35242637 allocation units available on disk.

Internal Info:
00 ca 02 00 33 54 02 00 ef 74 04 00 00 00 00 00 ....3T...t......
ef 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-14T02:46:16.000000000Z" />
<EventRecordID>42668</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Moo</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is Moo.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
182784 file records processed.

File verification completed.
689 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
243878 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
182784 file SDs/SIDs processed.

Cleaning up 2326 unused index entries from index $SII of file 0x9.
Cleaning up 2326 unused index entries from index $SDH of file 0x9.
Cleaning up 2326 unused security descriptors.
CHKDSK is compacting the security descriptor stream
30548 data files processed.

CHKDSK is verifying Usn Journal...
35491152 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
182768 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
35242636 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

234195967 KB total disk space.
92849412 KB in 122068 files.
83848 KB in 30551 indexes.
0 KB in bad sectors.
292159 KB in use by the system.
65536 KB occupied by the log file.
140970548 KB available on disk.

4096 bytes in each allocation unit.
58548991 total allocation units on disk.
35242637 allocation units available on disk.

Internal Info:
00 ca 02 00 33 54 02 00 ef 74 04 00 00 00 00 00 ....3T...t......
ef 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Can you post a screen shot of the updates that are waiting to be installed.
 
Ad

Advertisements

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
I would suggest that you do the following:

  1. Enable Driver Verifier (See instructions below)
  2. Download all the patches individually from Microsoft.
  3. Disable Microsoft Security Essentials. (Just until the patches are installed)
  4. Run the patches individually.

That way you will find out which patch crashes your computer and can help in the resolution, because with driver verifier on more information is gathered.


Driver verifier

The Driver Verifier tool that is included in every version of Windows since Windows 2000 it is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior.

***FIRST: Please backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Windows 7 Startup Repair feature.)
  1. Go to Start and type in "verifier" (without the quotes) and press Enter
  2. Select "Create custom settings (for code developers)" and click "Next"
  3. Select "Select individual settings from a full list" and click "Next"
  4. Select:
    ---- Special Pool
    ---- Pool Tracking
    ---- Force IRQL Checking
    ----Deadlock Detection
    ---- Security Checks (Windows 7 & 8)
    ---- DDI compliance checking (Windows 8)
    ---- Miscellaneous Checks

  5. Click "Next"
  6. Select "Select driver names from a list" and click "Next"
  7. Then select all drivers NOT provided by Microsoft and click "Next"
  8. Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Will I see anything when I enable Driver Verifier?

No, Driver Verifier configures Windows so that people looking at the crash dump files get (in most cases) more detailed information about what actually crashed the computer.
How Long should I wait for a crash?

- If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
How do I turn Driver Verifier off?!

- Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page.

- Or press the Windows Key + R, and type in "verifier /reset" (Without the quotes)

- Then locate and zip up the memory dump file and upload it with your next post. then locate and zip up the memory dump file and upload it with your next post.
I can't get in to Windows, what do I do?

- If Windows will not start and get to a login screen or desktop, because it crashes too soon, try it in Safe Mode.


- If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
How do I put the crash dump files in a Zip file?

Instructions on putting files in a Zip file and extracting (Taking them out) again are explained HERE.
 
Joined
Aug 14, 2014
Messages
5
Reaction score
0
Where will Driver Verifier put the crash dump file? In the minidump folder in C:/Windows?
 
Joined
Aug 14, 2014
Messages
5
Reaction score
0
In the meantime, I installed each patch individually to narrow it down. KB2982791 and KB2970228 are the ones that'll give me a BSOD on restart. The rest installed fine.
 
Ad

Advertisements

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Sorry for the slow responce.

Have a look in the following directories:
c:\Windows
c:\Windows\Minidump
c:\Windows\Live KernelReports\WATCHDOG
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top