• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 609
  • Last Modified:

BSOD page fault in non paged area

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
compuzak1
Asked:
compuzak1
  • 3
  • 2
1 Solution
 
cool_apjCommented:
Kindly upload the result of system dump for furthur analysis.
You can use the Windebug and post the result./
0
 
compuzak1Author Commented:
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
 
compuzak1Author Commented:
I found WinDbg and downloaded it from Microsoft website.  How do I use the program to get information from the crash?  
0
Technology Partners: 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!

 
cubeeqCommented:
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
 
compuzak1Author Commented:
Thank you for the detailed explanation.  I will attempt this tomorrow (Friday) and let you know how it goes.
0
 
cool_apjCommented:
DID YOU FIGURE HOW TO RUN THE DEBUG.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now