none
BSOD win32k.sys Page fault in non-paged area RRS feed

  • Question

  • Had this BSOD error today (while trying to print a pdf of an IE Web Page).  This minidump file doesn't give me a clear cue as to the origin of the problem, but it shows on my machine that there is a problem with they symbols.

    Any help in tracking down this issue would be appreciated.


    Ron

    Thursday, August 29, 2013 6:38 PM

Answers

  • RR

    This crash was related to memory but the driver causing it could not be determined.

    BugCheck 50,

    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!GreRestoreDC+23f )

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. 

    Since it is probably a driver the fastest way to find which one is to run driver verifier.

    2-Driver verifier
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    But sometimes it'll crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    I'd suggest that you first backup your data 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 Vista/Win7 Startup Repair feature).

    Here is the procedure:

    Go to Start and type in "verifier" (without the quotes) and press Enter
    Select "Create custom settings (for code developers)" and click "Next" (or  Type "verifier /standard /all"  (no quotes) if you want to verify all of them (this will slow your computer down))
    Select "Select individual settings from a full list" and click "Next"
    Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
    Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    If you can't get into Windows 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.

    Further Reading
    http://support.microsoft.com/kb/244617


    Wanikiya & Dyami--Team Zigzag

    Friday, August 30, 2013 8:46 AM
    Moderator

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)
    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here



    Wanikiya & Dyami--Team Zigzag

    Thursday, August 29, 2013 6:40 PM
    Moderator
  • WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    Can you tell anything from the first minidump file at the Skydrive link I posted in my original post above?
    Or is that link not working?

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    How does booting into safe mode allow me to get a second minidump file? I thought they were only generated after a crash?

    I had already booted into safe mode during the recovery process, and still only see the original minidump file.


    Ron


    Friday, August 30, 2013 8:29 AM
  • RR

    This crash was related to memory but the driver causing it could not be determined.

    BugCheck 50,

    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!GreRestoreDC+23f )

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. 

    Since it is probably a driver the fastest way to find which one is to run driver verifier.

    2-Driver verifier
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    But sometimes it'll crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    I'd suggest that you first backup your data 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 Vista/Win7 Startup Repair feature).

    Here is the procedure:

    Go to Start and type in "verifier" (without the quotes) and press Enter
    Select "Create custom settings (for code developers)" and click "Next" (or  Type "verifier /standard /all"  (no quotes) if you want to verify all of them (this will slow your computer down))
    Select "Select individual settings from a full list" and click "Next"
    Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
    Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    If you can't get into Windows 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.

    Further Reading
    http://support.microsoft.com/kb/244617


    Wanikiya & Dyami--Team Zigzag

    Friday, August 30, 2013 8:46 AM
    Moderator
  • Interesting utility.  I will give it a try after studying the documentation and when I have sufficient time to devote.

    Thanks!

    -- Ron


    Ron

    Friday, August 30, 2013 11:45 AM
  • Fought this for a bit, but had noticed a slight anomaly with graphics display.. removed drivers (nvidia) and system stabilized.. however, it continued to crash with same message..  Ended up being a hardware issue with the actual graphics card.. replace, system stable and fixed..
    Monday, November 4, 2019 5:08 PM