[Khurram]

Facing a very weird issue lately. Random BSODs(bccode 50, page fault in nonpaged area, ntoskrnl.exe) at very odd times but specifically when browsing sitting idle or doing minimal work. doesn't happen during load or when gaming. Specs are given below. Sometimes it occurs 5 mins after logging in sometimes after 12 straight hours of usage. occurs mostly when pc is idle or doing minimal work i.e browsing e.t.c. works fine during heavy gaming etc. Can't say that it won't crash during gaming as i don't know the root of the problem but it hasn't crashed in game so far during 4,5 hour sessions of gaming. it happened a week ago i changed ram slots and it seemed to disappear but now has resurfaced again and doesn't seem to go away. doesn't happen in safe mode. once happened on log on screen when i just waited to see if the problem is with any of the installed applications. here is what I have done to solve the issue but hasn't been successful so far.

1. cleaned dust from pc especially ram slots.
2. changed ram slots, checked both rams separately in both slots still BSOD.
3. problem occurred after a few days i updated GPU drivers so I though it might be them uninstalled them and did a clean installation of old drivers still issue remains.
4. Did a clean fresh installation of windows. seemed to work fine for a couple of hours i installed some stuff drivers browsers, daemon tools, utorrent steam etc. shutdown pc, turned on after a couple of hours and again BSOD loop (sometimes it seems like a loop i.e consistent BSODs sometimes starts working fine and happens after good 12-24 hours).
5. Googled the [bleep] out of the problem. microsoft says it might be faulty ram. forums say software or driver conflicts. haven't installed any new hardware recently . system working fine for almost 1.5 years now with the same configuration.
6. checked all cables etc nothing loose. temps are fine too, irrelevant as doesn't happen during load.

Now at my wit's end. can't really figure out what is going on. BSOD error is always BCCode 50. Page fault in non paged area. file crashing is ntoskrnl.exe. sometimes there are other files but mostly its this one. attaching latest minidump they are all the same. any help would be appreciated thanks.

specs:

Monitor: Viewsonic VA1912w
CPU: Intel Core2Quad Q9300
Cooler: Foxconn Stock LGA 775
Motherboard: Foxconn G41wv
Memory: 4 GB DDR3
GPU: Gigabyte GTX 550 Ti OC
HDD: Seagate 750 GB
Chassis: HP Pavilion Micro Tower
PSU: Thermaltake Lite Power 450w
Soundcard: Creative Sound Blaster X-Fi XtremeGamer SB0730
OS: Windows 7 Ultimate 64-Bit

[Advertisements]

Since both memory modules checked independently still throw BSOD's then we need to go to the next step in diagnosing. From your description the manual test listed below has already been done so you can skip straight to the software test.

A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.





When done please do the following also:


Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[rshaffer61]

Since both memory modules checked independently still throw BSOD's then we need to go to the next step in diagnosing. From your description the manual test listed below has already been done so you can skip straight to the software test.

A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.





When done please do the following also:


Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[Khurram]

Thanks for the detailed reply!
i checked both sticks separately, one by one in both slots and also one stick at a time. problem still occurred. about memtest it isn't possible here in our country due to massive power load shedding. all I can do is to arrange another memory stick to confirm but I doubt that it will solve the issue as I have read a bit about the other people having the exact same issue. their memtest always came clean and they still were having the issue.

here are a couple of examples of people having almost the same issue.

http://rog.asus.com/...-but-not-gaming!
http://www.tomshardw...mes-happen-load

[Khurram]

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 22-06-2013 AM 08:23:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-19094-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A59B000, 0x0, 0xFFFFF80002F37079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 22-06-2013 AM 08:23:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF8A00A59B000, 0x0, 0xFFFFF80002F37079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 22-06-2013 AM 12:02:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-15912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008B66000, 0x0, 0xFFFFF80002F4F079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 11:55:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-17238-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008D66000, 0x0, 0xFFFFF80002F45079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 11:47:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008BFB000, 0x0, 0xFFFFF80002F97079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 11:40:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-17643-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008B66000, 0x0, 0xFFFFF80002F81079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 11:32:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-17628-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A966000, 0x0, 0xFFFFF80002F9D079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 09:31:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-18517-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009F66000, 0x0, 0xFFFFF80002F4D079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 09:23:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062213-18267-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009966000, 0x0, 0xFFFFF80002F39079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 05:51:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-20935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A34F000, 0x0, 0xFFFFF80002F99079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 PM 03:56:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-15849-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A003966000, 0x0, 0xFFFFF80002F39079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21-06-2013 AM 02:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-16224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A003B66000, 0x0, 0xFFFFF80002F8D079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 20-06-2013 PM 05:24:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-17799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008B66000, 0x0, 0xFFFFF80002F3B079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 20-06-2013 PM 05:17:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-16676-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008B66000, 0x0, 0xFFFFF80002F9D079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 20-06-2013 PM 05:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-16114-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A008B66000, 0x0, 0xFFFFF80002F81079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

31 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[rshaffer61]

OK first here is the explanation of the bug check you are getting.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.

First what AV are you using?
Second are all your drivers up to date?
Third have you run HD diagnostics?
Fourth did you check the System File Checker for anything?

[Khurram]

first no antivirus at all
second yes drivers are mostly. atleast the ones that are available. its a pretty old pc.
ran a complete error scan of hd tune. hdd is clean.
also did sfc scan but then again sfc wouldn't have mattered as problem persists even after fresh installation of windows.

[rshaffer61]

I'm beginning to believe it is just the age of the system but I have one more trick up my sleeve to make sure it is not a driver. I know you said the ones that are available are up to date but lets make sure.


Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
If you want you can post screenshots of all the drivers in the list that need to be updated and I will suggest in what order to get them.

[Khurram]

last night did a fresh windows installation then turned off windows updates removed internet cable before installation then only installed creative sound and Nvidia GPU drivers. watched a couple of movies and left it on all night night with sleep mode off. just plugged in the cable to update that no BSOD so far.

[rshaffer61]

OK possibly a faulty update then could be the cause. Do you have updates set to auto install or do you go through them and verify what is being installed first?

[Khurram]

i have turned them off altogather but didn't turn off the option for other users so thats may be the problem, but i am not entirely sure that the issue is gone. for other people it has resurfaced even after 6 months. my first target is to see it through 24 hours first. just installed steam and chrome lets see how it goes.

[rshaffer61]

OK let me know

[Khurram]

sure will do. stable so far. will keep updating.

[rshaffer61]

If you only do 5 updates at a time then you will have the culprit when it does or if it happens again.

[Khurram]

If you only do 5 updates at a time then you will have the culprit when it does or if it happens again.

for the time doing i am not doing the update at all.I am even afraid to install essential programs like office and media players etc. btw still stable.

[rshaffer61]

OK Windows has Media Player already. I personally have not used it in years once I found VLC. No worries about codecs or any of that nonsense. Just a thought but you could install one update at a time and that way you would know exactly what is causing the issue. I agree though if it is working now enjoy it for awhile.