BSOD - Page Fault in Non Paged Area

Experienced a BSOD for the first time on my Lenovo Thinkpad T400 laptop yesterday.

The BSOD error that I got was this:
Page Fault in Non Paged Area 0x50 (0x.....)

I have a dual-boot Fedora 12(default) and Windows 7 Home edition 64 bit (OEM). The BSOD is happening whenever I try to boot into Windows. Pressing F8 post boot and trying different options does not seem to make a difference. I always encounter the BSOD and the laptop restarts. Is there any way I can get into the system and extract the dump files? Is there any way to install the BSOD Dump & System File collection app or Windbg?

I can access the Windows partition after booting into Fedora. Can I extract the dump files from there? If so, what could be the location of the dump?

Thanks in advance.

https://www.sevenforums.com/crashes-d...tructions.html
It takes certain skills, knowledge and time to understand what to do with WinDBG.

I did read the BSOD posting instructions. However, my system displays the BSOD post boot and restarts immediately thereafter.

My apologies for being so dense, but how can I install the app and extract the BSOD dump , if I can't log into Windows? None of the options that appear after pressing F8 (Safe Mode, Safe Mode with Command Prompt etc) prevent my laptop from showing the BSOD and restarting.

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

I have been searching the \Windows folder but it does not have a \Minidump directory. I also searched (using Fedora) for files that were last modified before my Windows crashed. The last files to be modified were in the AVG directory, Soft Grid directory (don't know what that is) and also a couple of NTUSER.dat and NTUSER.dat.log files. Would the .dat files be useful?

While trying to boot Windows into Safe Mode, I noticed that the BSOD appears after AVG drivers (AVGIDSEH.sys, although it wasn't modified recently) have been loaded. Could an update to AVG be causing this problem? Although I've had AVG installed ever since I got the system about 15 months back.

Thanks much for your help, Dean.

FarsideArgus said:

I have been searching the \Windows folder but it does not have a \Minidump directory. I also searched (using Fedora) for files that were last modified before my Windows crashed. The last files to be modified were in the AVG directory, Soft Grid directory (don't know what that is) and also a couple of NTUSER.dat and NTUSER.dat.log files. Would the .dat files be useful?

While trying to boot Windows into Safe Mode, I noticed that the BSOD appears after AVG drivers (AVGIDEH.sys or something like that) have been loaded. Could an update to AVG be causing this problem? Although I've had AVG installed ever since I got the system about 15 months back.

Thanks much for your help, Dean.

.DAT isn't helpful much. Look for MEMORY.DMP in :\Windows and see if it's in there

I looked for MEMORY.DMP in \Windows, but it is not there . Strangely enough, when I select the "boot log" option after pressing F8, the BSOD shows "Dumping physical memory to disk : 100" and then restarts. However, I can't find the .DMP file afterwards.

Nevertheless, there are a couple of .DMP files, that seem to have been created around the time the problem started appearing. Their locations are "/Windows/LiveKernelReports/WATCHDOG/WD-20110307-1408.dmp" and "/ProgramData/Microsoft/Windows/WER/ReportQueue/Kernel_0_0_cab_163c89ec/WD-20110307-1408.dmp". Would it be of any use to look at these files and if so, should I attach them?

Thanks.

Are you running CCleaner? If so, make sure it is configured to not delete dump files
Create a folder in C:\Windows and name it Minidump

No, I am not running CCleaner.

At the moment, the only way I can access the Windows directory structure is through my Linux OS. In this way, I created a Minidump folder in C:\Windows and restarted my system to boot into Windows. The BSOD appeared and did a memory dump and rebooted my system. I logged into Linux again and checked if any new memory dump was created in C:\Windows or elsewhere. Unfortunately, no dump was created.

Could you please tell me what do I do next?

So I have been trying to get to the root of this BSOD. Logging into my Linux OS, I once again had a look at what files were modified before the crash happened. It seems that the AVG folder was modified - an upgrade might have taken place, which could have caused the system to crash.

I downloaded the AVG rescue utility and made a bootable USB out of it. I booted into the utility and ran the memtestx86 and also did a virus scan for the Windows partition. Both came out clear.

Is there any way I could uninstall or suspend the AVG installation using the Rescue Utility? Is it possible to make the SF Tool bootable?

I am unable to log into Windows since the system restarts right after booting (Page Fault x50 Stop error). That is really hampering my efforts. Any pointers would be much appreciated. Thanks.