[rshaffer61]

Start with the third page with the nforce memory controller and get everything on that page first then do all the rest after. Let me know once you are done with the 3rd page if anything gets better.

[Advertisements]

Installed 5 drivers from page 3 starting with nforce memory controller.
Rebooted and retested (Tetris test) after each of the 5 installs.
No change.

Not every install tells me to reboot, but I do anyway.

So that makes 2 plus 5 = 7 installs so far.

I assume I just continue doing all the rest in any order?

And let me ask this.. is it ok to install more than one at a time whether or not some require rebooting?
I ask because it would be a whole lot simpler to install them all so we can move onto more treatment(s).

But I can continue doing them one by one and booting after each - that way we can know which one makes the test - which would be nice to know.

/nick

[NickKeenan]

Installed 5 drivers from page 3 starting with nforce memory controller.
Rebooted and retested (Tetris test) after each of the 5 installs.
No change.

Not every install tells me to reboot, but I do anyway.

So that makes 2 plus 5 = 7 installs so far.

I assume I just continue doing all the rest in any order?

And let me ask this.. is it ok to install more than one at a time whether or not some require rebooting?
I ask because it would be a whole lot simpler to install them all so we can move onto more treatment(s).

But I can continue doing them one by one and booting after each - that way we can know which one makes the test - which would be nice to know.

/nick

[rshaffer61]

You can install them as many at a time as you want. I agree when you have each installed or a set of them installed you should reboot to make sure. At least that way you will have a ideal which set hopefully resolves the issue for you.

[NickKeenan]

Refer to driverList01-04 as p01 - p04 and #1 - #5 on each page

1. installed/booted/tested p01 #1 - no change

2. installed/booted/tested p01 #2 - no change

3. installed p01 #5
installed p02 #1
installed p02 #2
installed p02 #3
installed p02 #4
booted and..
4. got Windows msg "System has recovered from a serious error. A log has been created. Please tell MS about this problem. We have created an error report" Then a prompt to Send or Cancel. I cancelled. I can send report/log.
5. Tried to connect to internet - got a 'server down' msg (709? not sure). Power cycled modem. No help.
6. Rebooted and again got "System has recovered etc.." msg and couldn't get rid of it.
7. And couldn't connect to internet
8. Figured maybe driver p02 #3, NVIDIA Network Bus Enumerator, caused problems
9. Mounted driver CD that came with system, selected nForce chipset driver, sub-selected Ethernet driver (but not SM Bus nor Storage drivers)
10. Driver install begins then halts with a Stop Error crash..
11. Reboot.
12. And it came up without any error msgs
13. Tested Tetris - no change
14. Connect to internet and here we are.

Should I go ahead with the rest of the new driver installs starting with p2 #5, skip p3, p4 #1 - #5?
I'll wait to hear from you for awhile in case you have some suggestions.. let me know.
I figure if I install all the updates I can, then I can rerun the scan to see if there's anything still to update.

What do you think?

/nick

[rshaffer61]

Yep get everything updated and that way we narrow down the variables as to what is causing the errors.
Just to check also can you do the following.

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

[NickKeenan]

OK - updated everything, rebooted, tested - no change

Rescanned - response was that my system is up to date.

WhoCrashed report follows

/nick

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

computer name: GENERALSPECIFIX
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon™ 64 Processor 3500+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 2079637504 total
VM: 2147352576, free: 2046054400



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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 3/27/2012 11:35:35 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032712-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB915B911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/25/2012 4:42:36 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032512-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sat 3/24/2012 2:47:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sat 3/17/2012 11:18:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x66EA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFFBF8066EA, 0xFFFFFFFFB485AB18, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 3/13/2012 12:44:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031312-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Tue 3/13/2012 2:21:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031212-04.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Tue 3/13/2012 2:20:40 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031212-03.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Tue 3/13/2012 2:15:21 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031212-02.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Mon 3/12/2012 5:56:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031212-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9930911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 10:28:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031112-05.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9930911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 10:26:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031112-04.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 9:38:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031112-03.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 7:08:48 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031112-02.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 9:17:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031112-01.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR




On Sun 3/11/2012 3:16:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031012-03.dmp
This was probably caused by the following module: nvnrm.sys (NVNRM+0x2911)
Bugcheck code: 0x100000D1 (0x50, 0x2, 0x0, 0xFFFFFFFFB9951911)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\nvnrm.sys
product: NVNRM
company: NVIDIA Corporation
description: NVIDIA Network Resource Manager.
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: nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation).
Google query: nvnrm.sys NVIDIA Corporation CUSTOM_ERROR





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

49 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have 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:

nvsnpu.sys (NVIDIA Networking Soft-NPU Driver., NVIDIA Corporation)

nvnrm.sys (NVIDIA Network Resource Manager., NVIDIA Corporation)

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]

Strange they almost all indicate a video driver issue.
Tell you what run this again and see what comes up.

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[NickKeenan]

As requested.
/nick


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 15 unused index entries from index $SII of file 0x9.
Cleaning up 15 unused index entries from index $SDH of file 0x9.
Cleaning up 15 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

40957685 KB total disk space.
15970456 KB in 50721 files.
16684 KB in 5596 indexes.
0 KB in bad sectors.
142145 KB in use by the system.
65536 KB occupied by the log file.
24828400 KB available on disk.

4096 bytes in each allocation unit.
10239421 total allocation units on disk.
6207100 allocation units available on disk.

Internal Info:
50 fc 00 00 09 dc 00 00 6a 2c 01 00 00 00 00 00 P.......j,......
be 00 00 00 02 00 00 00 f9 05 00 00 00 00 00 00 ................
6a ed 92 01 00 00 00 00 fc 23 4e 1e 00 00 00 00 j........#N.....
14 80 d4 05 00 00 00 00 06 45 5b 58 01 00 00 00 .........E[X....
a6 bb af 97 01 00 00 00 f0 3a 23 1d 03 00 00 00 .........:#.....
99 9e 36 00 00 00 00 00 e8 3e 07 00 21 c6 00 00 ..6......>..!...
00 00 00 00 00 60 c2 ce 03 00 00 00 dc 15 00 00 .....`..........

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at
http://go.microsoft....ink/events.asp.

[rshaffer61]

Well it's not a hard drive issue.

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.

[NickKeenan]

I've got 4 sticks of 512KB for a total of 1.93GB

You wrote:
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

I'm a little confused - is "option A" = "try starting computer with one RAM stick at a time"?
I think that's what you mean.. but I don't see 'option A' anywhere.

Do you want me to boot with one stick at a time?
And what am I looking/testing for? Bad ram?
Please advise.

I'll be away from the machine for awhile..

/nick

[rshaffer61]

Yes that is what it means exactly. I know it is a long process and may be counter productive since less memory will slow the OS down even more. I would suggest skipping the manual test and go straight to running memtest86 instead. If any of the memory is bad it will show in the test.

[NickKeenan]

OK.. thanks, for clarifying.
For now I'll sleep on it and undertake Plan B tomorrow when I'm more alert
and less likely to blunder.

Thanks for staying with me on this.. much appreciated.

/nick

[rshaffer61]

No problem and I am here till we find the answer good or bad.

[NickKeenan]

I need to tell you what's happening this morning..
1. on a boot but before windows has settled down I get the 'Windows Recovered from Serious Error' msg (WRSE)
2. then crash - Stop error.
3. while down, I notice my modem has TX on steady, so I power cycle it to normal lights, ie no RX and no TX, rest all ON.
4. reboot - and again WRSE, and crash, at about the same place as before, and I notice TX went on steady
5. I power off the modem and reboot.
6. Again WRSE but no crash. I leave WRSE on display, play Freecell once, the select Don't Send on WRSE
7. It stays up, so I power on the modem, and it comes up to normal lights
8. I connect (I use a PPPOE dialer to connect) and sign into GTG, and here I am.

If the modem is on when WRSE happens then it crashes, but when modem is off and WRSE happens it doesn't crash.

I'm worried that at some point I will not be able to connect to the internet and so be unable to reach you. Can I suggest that if you don't hear from me for an hour or two today that you give me a call,

If you've got any comment on this, please let me know.
I'll now try to prepare for the memory test.

/nick

Edited by rshaffer61, 31 March 2012 - 09:24 AM.
Removed phone number. Privacy issue

[rshaffer61]

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 31 03 2012
  In the To: boxes type today's date (presuming the crash happened today) 31 03 2012
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply