[kgr]

When I try to open Firefox, I get an error: The instruction at "0x003e8d37" referenced memory at "0x003e8d37." The memory could not be "read." I have tried uninstalling and reinstalling, but still get the same message. Could someone please help me? Thank you!

[Advertisements]

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

[rshaffer61]

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

[kgr]

Thank you for your help!

Here is the report:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sat 2/14/2009 5:39:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021409-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1193)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFFFFFBF801193, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Thu 1/1/2009 9:56:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini010109-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1193)
Bugcheck code: 0x10000050 (0xFFFFFFFFF0008087, 0x0, 0xFFFFFFFFBF801193, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 9/26/2006 1:52:21 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4E7B)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFFC, 0x2, 0x0, 0xFFFFFFFF804DBE7B)
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.

[rshaffer61]

OK lets start with the disk integrity.

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.

[kgr]

I ran the Checkdisk, but was unable to find a Winlogon file from today in the Event Viewer. I only had Winlogon files from 10/11 and 10/14. This is the one from 10/14:

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

The volume is dirty.
Deleted corrupt attribute list entry
with type code 128 in file 34558.
Unable to find child frs 0x109a5 with sequence number 0x3e.
Deleted corrupt attribute list entry
with type code 128 in file 34558.
Unable to find child frs 0x127f8 with sequence number 0x7d.
The first attribute of type 0x30 and instance tag 0x2
in file 0x86fe should not be resident.
Deleted corrupt attribute list entry
with type code 48 in file 34558.
Unable to locate attribute with instance tag 0x2 and segment
reference 0xe90000000086fe. The expected attribute type is 0x30.
Deleting corrupt attribute record (48, "")
from file record segment 34558.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x23000000012c36. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 76854.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x8d941c for possibly 0x72f clusters.
Correcting cross-link for file 141076.
Unable to locate the file name attribute of index entry WFV228.tmp
of index $I30 with parent 0x2166 in file 0x86fe.
Deleting index entry WFV228.tmp in index $I30 of file 8550.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 746 unused index entries from index $SII of file 0x9.
Cleaning up 746 unused index entries from index $SDH of file 0x9.
Cleaning up 746 unused security descriptors.
Inserting data attribute into file 34558.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

74228332 KB total disk space.
69572848 KB in 147049 files.
54076 KB in 20189 indexes.
0 KB in bad sectors.
273288 KB in use by the system.
65536 KB occupied by the log file.
4328120 KB available on disk.

4096 bytes in each allocation unit.
18557083 total allocation units on disk.
1082030 allocation units available on disk.

Internal Info:
00 00 03 00 4f 8d 02 00 48 98 03 00 00 00 00 00 ....O...H.......
7d 2e 00 00 02 00 00 00 25 0a 00 00 00 00 00 00 }.......%.......
30 de 78 0d 00 00 00 00 80 6b 56 01 01 00 00 00 0.x......kV.....
e0 86 fc 18 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 20 48 ea 29 01 00 00 00 ........ H.)....
99 9e 36 00 00 00 00 00 00 39 07 00 69 3e 02 00 ..6......9..i>..
00 00 00 00 00 c0 63 96 10 00 00 00 dd 4e 00 00 ......c......N..

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

[rshaffer61]

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.

[kgr]

I have 2 sticks of RAM. I tried starting with one at a time and got the same Firefox error each time. Should I still run the memtest?

[rshaffer61]

Yep to check now and see if either or both may have a issue.