[jimafm]

After upgrading to IE 8 (forced by MS & Yahoo) and installing a couple of new programs, things got too weird for me to resolve. A real horror story.

One morning recently, I walked in to my office to find the BSOD with error code 0X00000050. More on that later. Then the volume control icon for Realtek AC '97 Audio for VIA disappeared a few days later. Suspecting a virus had gotten past Norton 360, I had one of their techs take a look around inside my PC. Wrong! It took half a day to re-customize my PC after his "fixes" accomplished nothing. He told me the driver was GONE, but had no ideas how to reinstall it.

But wait, there's more. This morning I decided to boot from my Norton recovery CD just to see what happens. The CD/DVD drive is totally dead, and isn't listed as a choice for booting in BIOS. My floppy is gone from BIOS, as well. Also, I notice that my HDD runs 24/7, which really has me worried, as it can't last long.

Lastly, here's a good one to strain your brain: My tool bars and address bar are backward every other time I reboot. All blacked out so I can't read them. Setting colors in Tools>Internet Options does nothing.

I'm afraid to run a backup to my portable HDD because I use Acronis, which backs up the entire PC's HDD, programs and all. Since I obviously have some major issues, I hesitate to infect my backup drive. Alas, a recovery to an earlier date isn't an option either, since I have done a lot of work since this began a week ago.

I've defragged, compacted and run CCleaner, Norton deep scan and Malwarebytes to no avail. I uninstalled recently purchased Advanced Driver Updater and the problem went away for 24 hours, then came roaring back just as I was patting myself on the back for being smarter than the Norton techs.

I did find 2 unnamed programs running in the background, but I can't find them in Add/Remove, and I have no idea how long they have been there or if I need them. I am using 2 off-site backups, and I suspect that's what they are, since they don't show up in Add/Remove.

Here's the crazy part. As long as I'm using the PC, everything works as it should except the black tool bar thing, which I can cure with a soft reboot. If I make myself a sandwich, I return in 5 minutes to the BSOD.

ANY help would be a treasure. I'm almost out of Valium.

[Advertisements]

Hello jimafm.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
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).

Most obvious choice is to test the ram memory by doing the following.

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 [b/memtest86+-4.20.iso[/b] 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.

[rshaffer61]

Hello jimafm.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
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).

Most obvious choice is to test the ram memory by doing the following.

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 [b/memtest86+-4.20.iso[/b] 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.

[jimafm]

Thank you very much for the quick reply and detailed information.

I'm not sure where the mem sticks are. If you can point me to the right place on the motherboard, I'll give that a try if I find more than one. If I have 2 or more, does it matter which slot the one I leave is in?

If I only have 1 stick, I have the problem burning the boot CD with the CD/DVD drive not working. Since it has been working just fine, I suspect the Norton techs may have disabled it somehow, especially since it has had little use, was working the day before and is a nice Sony unit. Can you tell me if there is anything I can do to turn it back on in BIOS or elsewhere?

Thanks again. I'm delighted to finally have some expert advice. I'm an electronics tech, but a novice with anything besides MS programs.

[jimafm]

Is there enough room on a floppy to burn the boot?

[rshaffer61]

I suggest using the cd ISO version and don't worry about the removal of memory. Right now we are just trying to determine if there is a issue at all.

[123Runner]

Usually the CD drives and floppy are automatically recognized in bios so I suspect that if the tech was inside he may have disconnected them or bumped a cable by mistake.
The first thought would be to open the case and make sure the power and data cable s are connected.

[rshaffer61]

Good call 123Runner.

[jimafm]

Thanks, guys, for the good advice. Unfortunately, I haven't been clear enough.

rshaffer61, I not certain what a "CD iso version is, but if it is a CD, I can't run it because that drive is dead.

123runner, I want that avatar. The only tech "inside" my PC was a Norton tech looking for the problem via remote desktop connection during a chat. So, the cables, etc, haven't been fooled with. The PC hasn't been moved, touched, etc. No storms, surges, etc, and I have both UPS and Panamax surge protection. Being a AV electronics tech for 40 years has taught me to stay out of equipment I know nothing about (computers). That is, unless one of you is holding my hand.

Naturally, the Norton tech couldn't see the BIOS screen. I noticed my CD/DVD was no longer a boot option when I tried to use it to boot with and it was dead. I checked in BIOS during one of the reboots I've had to do several times a day and noticed the options of what to boot from only included my HDD and the CD/DVD. The floppy and an external HDD backup on E drive are no longer listed in BIOS, yet no one has made any changes there.

It's like something is killing my PC, bit by bit. First, Blue screen, then CD/DVD dies, then things in BIOS disappear, and now my monitor won't go to sleep despite being set to do so in Windows. As I mentioned earlier, full Norton 360, CCleaner and Malwarebytes have found nothing.

Please understand that the BSOD only happens when the PC is idle. As long as I'm using it, it runs OK. I do have Norton Backup, Acronis Constant Backup (both disabled as a test) and Zone Alarm Backup (an off-site backup, which is running).

One other thing that really has me worried is the C drive (HDD) runs 24/7. That was noticed the first time I got the Blues. It's just a matter of time until that dies and I'm done for.

[rshaffer61]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program





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

[jimafm]

rshaffer61,
OK, here goes:

Mini082211-03.dmp 8/22/2011 3:15:07 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x00000002 0xa41a3b00 0x00000000 32-bit ntoskrnl.exe+1609cb ntoskrnl.exe+151ce2 ntoskrnl.exe+1421dc C:\WINDOWS\Minidump\Mini082211-03.dmp 1 15 2600 98,304
Mini082211-02.dmp 8/22/2011 10:07:05 AM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe6fadb58 0x00000000 0x8062e732 0x00000001 ntoskrnl.exe ntoskrnl.exe+157732 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157732 ntoskrnl.exe+d9bde ntoskrnl.exe+4bbf1 ntoskrnl.exe+14ee9a C:\WINDOWS\Minidump\Mini082211-02.dmp 1 15 2600 98,304
Mini082211-01.dmp 8/22/2011 7:56:16 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x00046b76 0xa3c46b00 0x00000000 32-bit ntoskrnl.exe+1609cb ntoskrnl.exe+151ce2 ntoskrnl.exe+1421dc C:\WINDOWS\Minidump\Mini082211-01.dmp 1 15 2600 98,304
Mini082111-05.dmp 8/21/2011 8:33:52 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x805e634c 0xa415381c 0x00000000 ntoskrnl.exe ntoskrnl.exe+10f34c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+10f34c ntoskrnl.exe+10fedf ntoskrnl.exe+11078d ntoskrnl.exe+dece3 C:\WINDOWS\Minidump\Mini082111-05.dmp 1 15 2600 98,304
Mini082111-04.dmp 8/21/2011 12:55:50 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe84fbb64 0x00000000 0x80626954 0x00000001 RapportPG.sys RapportPG.sys+a01c 32-bit ntoskrnl.exe+14f954 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 ntoskrnl.exe+145292 C:\WINDOWS\Minidump\Mini082111-04.dmp 1 15 2600 98,304
Mini082111-03.dmp 8/21/2011 10:05:33 AM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe7724000 0x00000000 0x8062eb68 0x00000001 ntoskrnl.exe ntoskrnl.exe+157b68 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+14f957 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 C:\WINDOWS\Minidump\Mini082111-03.dmp 1 15 2600 98,304
Mini082111-02.dmp 8/21/2011 8:39:49 AM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe2b85000 0x00000000 0x8062eb68 0x00000001 ntoskrnl.exe ntoskrnl.exe+157b68 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+14f957 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 C:\WINDOWS\Minidump\Mini082111-02.dmp 1 15 2600 98,304
Mini082111-01.dmp 8/21/2011 3:11:09 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x8a7ea8d8 0xa79da934 0x00000000 RapportPG.sys RapportPG.sys+101c 32-bit ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 ntoskrnl.exe+145292 C:\WINDOWS\Minidump\Mini082111-01.dmp 1 15 2600 98,304
Mini082011-07.dmp 8/20/2011 11:12:19 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe3a1d000 0x00000000 0x8062eb68 0x00000001 ntoskrnl.exe ntoskrnl.exe+157b68 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+14f957 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 C:\WINDOWS\Minidump\Mini082011-07.dmp 1 15 2600 98,304
Mini082011-06.dmp 8/20/2011 10:09:38 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xffffff8a 0x00000001 0x8a7ea520 0x00000000 RapportPG.sys RapportPG.sys+601c 32-bit ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 ntoskrnl.exe+145292 C:\WINDOWS\Minidump\Mini082011-06.dmp 1 15 2600 98,304
Mini082011-05.dmp 8/20/2011 9:45:18 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe4256000 0x00000000 0x8062eb68 0x00000001 ntoskrnl.exe ntoskrnl.exe+157b68 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+14f957 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 C:\WINDOWS\Minidump\Mini082011-05.dmp 1 15 2600 98,304
Mini082011-04.dmp 8/20/2011 9:21:12 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe25ef000 0x00000000 0x8062eb68 0x00000001 ntoskrnl.exe ntoskrnl.exe+157b68 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+14f957 ntoskrnl.exe+dd9bf ntoskrnl.exe+da1b9 C:\WINDOWS\Minidump\Mini082011-04.dmp 1 15 2600 98,304
Mini082011-03.dmp 8/20/2011 8:38:58 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe115e000 0x00000000 0x8062eb68 0x00000001 sr.sys sr.sys+7b4d System Restore Filesystem Filter Driver Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5512 (xpsp.080413-2108) 32-bit ntoskrnl.exe+157b68 ntoskrnl.exe+1608cf ntoskrnl.exe+1609cb ntoskrnl.exe+151ce2 C:\WINDOWS\Minidump\Mini082011-03.dmp 1 15 2600 98,304
Mini082011-02.dmp 8/20/2011 9:28:25 AM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe851eadf 0x00000000 0x805eed39 0x00000001 ntoskrnl.exe ntoskrnl.exe+117d39 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647) 32-bit ntoskrnl.exe+117d39 ntoskrnl.exe+1566f5 ntoskrnl.exe+157604 ntoskrnl.exe+de92b C:\WINDOWS\Minidump\Mini082011-02.dmp 1 15 2600 98,304
Mini082011-01.dmp 8/20/2011 2:09:03 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x40000000 0xa385eb00 0x00000000 32-bit ntoskrnl.exe+1609cb ntoskrnl.exe+151ce2 ntoskrnl.exe+1421dc C:\WINDOWS\Minidump\Mini082011-01.dmp 1 15 2600 98,304

[jimafm]

Here's Whocrased. I hope you get more out of it than I did!


--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: AFM-MAIN
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon™ 64 Processor 3000+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 2146680832 total
VM: 2147352576, free: 2025553920



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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 8/22/2011 7:13:17 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082211-03.dmp
This was probably caused by the following module: rapportpg.sys (RapportPG+0x53AA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x2, 0xFFFFFFFFA41A3B00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys
product: Rapport
company: Trusteer Ltd.
description: RapportPG
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rapportpg.sys (RapportPG, Trusteer Ltd.).
Google query: rapportpg.sys Trusteer Ltd. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Mon 8/22/2011 1:59:11 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157732)
Bugcheck code: 0x10000050 (0xFFFFFFFFE6FADB58, 0x0, 0xFFFFFFFF8062E732, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 8/22/2011 11:54:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082211-01.dmp
This was probably caused by the following module: rapportpg.sys (RapportPG+0x53AA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x46B76, 0xFFFFFFFFA3C46B00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys
product: Rapport
company: Trusteer Ltd.
description: RapportPG
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rapportpg.sys (RapportPG, Trusteer Ltd.).
Google query: rapportpg.sys Trusteer Ltd. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Mon 8/22/2011 12:32:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x10F34C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805E634C, 0xFFFFFFFFA415381C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 a kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Sun 8/21/2011 4:53:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F954)
Bugcheck code: 0x10000050 (0xFFFFFFFFE84FBB64, 0x0, 0xFFFFFFFF80626954, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 1:56:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157B68)
Bugcheck code: 0x10000050 (0xFFFFFFFFE7724000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 7:33:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157B68)
Bugcheck code: 0x10000050 (0xFFFFFFFFE2B85000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 7:09:13 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F957)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8A7EA8D8, 0xFFFFFFFFA79DA934, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 a kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Sun 8/21/2011 2:32:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-07.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157B68)
Bugcheck code: 0x10000050 (0xFFFFFFFFE3A1D000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 2:07:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F957)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFF8A, 0x1, 0xFFFFFFFF8A7EA520, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 1:43:16 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157B68)
Bugcheck code: 0x10000050 (0xFFFFFFFFE4256000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 1:19:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x157B68)
Bugcheck code: 0x10000050 (0xFFFFFFFFE25EF000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 8/21/2011 12:37:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-03.dmp
This was probably caused by the following module: rapportpg.sys (RapportPG+0x53AA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE115E000, 0x0, 0xFFFFFFFF8062EB68, 0x1)
Error: CUSTOM_ERROR
file path: C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys
product: Rapport
company: Trusteer Ltd.
description: RapportPG
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rapportpg.sys (RapportPG, Trusteer Ltd.).
Google query: rapportpg.sys Trusteer Ltd. CUSTOM_ERROR




On Sat 8/20/2011 12:04:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x117D39)
Bugcheck code: 0x10000050 (0xFFFFFFFFE851EADF, 0x0, 0xFFFFFFFF805EED39, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 8/20/2011 5:59:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082011-01.dmp
This was probably caused by the following module: rapportpg.sys (RapportPG+0x53AA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x40000000, 0xFFFFFFFFA385EB00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys
product: Rapport
company: Trusteer Ltd.
description: RapportPG
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rapportpg.sys (RapportPG, Trusteer Ltd.).
Google query: rapportpg.sys Trusteer Ltd. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M





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

15 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rapportpg.sys (RapportPG, Trusteer Ltd.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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]

Rapporpg.sys is part of the Bank of America software.

This seems to be the root of the issue.

[jimafm]

I noticed that. Should I update my driver, or uninstall and get the latest version from bank?

Also, what do you think about all the crashes caused by our friends at MS? I have the XP installation CD around here somewhere, but I've never used it since my PC came with it installed. As I understand it, I have to call MS to get the key, which could mean hours on hold and the royal runaround.

[rshaffer61]

I would suggest seeing if they have a upgrade for the software and if not then you may have to uninstall it and try a newer version or reinstall the version you have.. Newer would be better if they have it.

[jimafm]

Thanks. Will do.

What about MS crashes. Do you think they are caused by Rapport, of a different problem?