Solved

BSOD page fault in non paged area

Posted on 2009-03-31
6
583 Views
Last Modified: 2013-11-27
I have an application written in Access 2003 with VBA code that accesses serial ports of platform scales and prints directly to thermal printers.  The application runs fine 99% of the time.  Periodically I get the "blue screen of death" along with error message "page fault in a non paged area".  The error is random and not really based on time or data transaction volume.  It does seem to happen during the print operation.  The system may work for weeks and some days it will actually crash twice in the same day.

How do I troubleshoot this problem and determine what is causing the crash?  Any information will be greatly appreciated.
0
Comment
Question by:compuzak1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 1

Expert Comment

by:cool_apj
ID: 24035242
Kindly upload the result of system dump for furthur analysis.
You can use the Windebug and post the result./
0
 

Author Comment

by:compuzak1
ID: 24041124
I am not familiar with Windebug.  How do I execute the command?  Do I need to run the command just after it crashes or can there be a delay (currently 3 days since it crashed).
0
 

Author Comment

by:compuzak1
ID: 24042199
I found WinDbg and downloaded it from Microsoft website.  How do I use the program to get information from the crash?  
0
Transaction Monitoring Vs. Real User Monitoring

Synthetic Transaction Monitoring Vs. Real User Monitoring: When To Use Each Approach? In this article, we will discuss two major monitoring approaches: Synthetic Transaction and Real User Monitoring.

 
LVL 3

Accepted Solution

by:
cubeeq earned 500 total points
ID: 24043871
hello, at first create directory for symbols (C:\websymbols)

then set web symbols path with Ctrl+S to SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols

then press Ctrl+D to load a crashdump (save any changes to workplace) - you will find the dump in C:\WINDOWS\MEMORY.DMP (if it is BSOD) - maybe you will have to increase memory amount dumped in MyComputer-Properties (Win+Pause) - somewhere in Start/Boot tab - at least to kernel memory dump

after some time all the symbols will be downloaded to windbg

then write into row at bottom: !analyze -v

finally look at CAUSED BY line or send the output here
0
 

Author Comment

by:compuzak1
ID: 24051082
Thank you for the detailed explanation.  I will attempt this tomorrow (Friday) and let you know how it goes.
0
 
LVL 1

Expert Comment

by:cool_apj
ID: 24230408
DID YOU FIGURE HOW TO RUN THE DEBUG.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question