Windows 10 64 bit BSOD Page Fault In Nonpaged Area

You get BSODs just during Windows start-up/booting the system?

Then try running Driver Verifier as there may be a boot driver involved, if software is the cause.

Be sure to run Windows System Restore and create a restore point per the sticky because if Driver Verifier detects a violation in a boot driver, it will force-BSOD the system, disable the driver and you'll be in a no-boot situation.

Then you'll need to boot into Recovery and use that restore point to re-boot.

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Regards. . .

jcgriff2
 
Sorry for the late response I have been busy with some IRL things and I haven't been able to spend a lot of time on the computer. When I booted my computer today from sleep 5 minutes after it started up and I was using firefox I got another bsod which said critical structure corruption and it also brought up win32kbase.sys. I also just saw that you recommend that I run driver verifier should I still do that even with this new bsod?
 

Attachments

This type of bugcheck is pointing towards memory corruption. I think you will need to test the RAM by physically removing one stick at a time and seeing if the problems are associated with one or other of the modules.

Code: 
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32kbase
2 errors : !win32kbase (ffffce25d23a9482-ffffce25d23a9bba)
ffffce25d23a9480  17  48 *cb  49  40  44  8d  4d  7a  44  8d  45  0f  4c  89  78 .H.I@D.MzD.E.L.x
...
ffffce25d23a9bb0  0c  f5  05  00  66  39  71  48  74  1a *4a  8b  49  40  41  b9 ....f9qHt.J.I@A.

MODULE_NAME: memory_corruption


FAILURE_ID_HASH_STRING:  km:memory_corruption_stride
 
philc43 said:
This type of bugcheck is pointing towards memory corruption. I think you will need to test the RAM by physically removing one stick at a time and seeing if the problems are associated with one or other of the modules.

Code: 
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32kbase
2 errors : !win32kbase (ffffce25d23a9482-ffffce25d23a9bba)
ffffce25d23a9480  17  48 *cb  49  40  44  8d  4d  7a  44  8d  45  0f  4c  89  78 .H.I@D.MzD.E.L.x
...
ffffce25d23a9bb0  0c  f5  05  00  66  39  71  48  74  1a *4a  8b  49  40  41  b9 ....f9qHt.J.I@A.

MODULE_NAME: memory_corruption


FAILURE_ID_HASH_STRING:  km:memory_corruption_stride
Click to expand...
4 passes on each stick with memtest86 then right?
 
No, just use the computer as you normally would but with one stick of RAM at a time. It helps if you know what triggers the BSOD or you just carry on and use it until one occurs or you feel you have tested long enough to satisfy yourself that the system is stable.
 
philc43 said:
No, just use the computer as you normally would but with one stick of RAM at a time. It helps if you know what triggers the BSOD or you just carry on and use it until one occurs or you feel you have tested long enough to satisfy yourself that the system is stable.
Click to expand...
How confident are you that one of the memory sticks is causing the bsods because if any of them are causing issues it doesn't really matter to me which one it is since i'll have to send them all back for warranty anyways.
 
Also I'm not sure what is causing these bsods at all since they only happen when I'm pretty much doing nothing soon after startup from sleep or a hard boot and the only recent software change i can think of before these happened is updated to 1809 on feb 18
 
About 60% confident, which is why confirmation is required by the strategy I suggested.
 
From what you wrote in post #49 it should happen soon after a start from sleep but only you know the pattern that tends to produce the BSOD so use your best judgement.
 
philc43 said:
From what you wrote in post #49 it should happen soon after a start from sleep but only you know the pattern that tends to produce the BSOD so use your best judgement.
Click to expand...
its barely a pattern considering how many successful boots i'm getting compared to bsods but I'll try my best to test them enough
 
Ran 1 stick of ram for about 3 weeks each and it worked fine then I went back to 2 sticks of ram for about 2 weeks and just I got another bsod when starting from sleep which said ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY and pointed to usbccgp.sys
 

Attachments

It would be worth testing the other stick of RAM on its own - its looking as if that stick might be faulty.
 
Sorry, I misread your post. It could be one of the slots on the motherboard so you will need to think about the problem in terms of the slots as well as the modules. When you ran the single RAM modules did you use the same slot? Can you use a different pair of slots for testing them together?
 
philc43 said:
Sorry, I misread your post. It could be one of the slots on the motherboard so you will need to think about the problem in terms of the slots as well as the modules. When you ran the single RAM modules did you use the same slot? Can you use a different pair of slots for testing them together?
Click to expand...
I have them in ddr3 slot 1 and 2 and when I did them solo I kept them in their original slots of 1/2
 
I'm assuming you are numbering the slots as shown in the manual on page 4 - these would be slots 2 and 4 counting from the CPU end. You could try slots DDR3_3 and DDR3_4, they would be slots 1 and 3 counting from the CPU end. The slots to be used in pairs are usually identified by being the same colour. Sorry if you already know all this but it is better to be sure.
 
philc43 said:
I'm assuming you are numbering the slots as shown in the manual on page 4 - these would be slots 2 and 4 counting from the CPU end. You could try slots DDR3_3 and DDR3_4, they would be slots 1 and 3 counting from the CPU end. The slots to be used in pairs are usually identified by being the same colour. Sorry if you already know all this but it is better to be sure.
Click to expand...
I am currently using slots 2/4 from the cpu and I just realized while opening my pc that I can't do slots 1+3 because of my cpu cooler. Also I just realized that yesterday night the power for my house had some problems and by any chance do you think could that have been a factor to cause the bsod since both of the single ram stick test runs went fine.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top