[Jamila'sfilter]

BSOD again as I was accessing geeks site for Malware Bytes.

[Advertisements]

Send me the Who Crashed please.

[Macboatmaster]

Send me the Who Crashed please.

[Jamila'sfilter]

Here is the log:

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

computer name: USER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium® Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3209879552 total
VM: 2147352576, free: 1982836736



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 7/31/2011 10:50:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002AD73F6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 7/31/2011 10:50:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!XLATEOBJ_hGetColorTransform+0x41A4C)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002AD73F6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 7/31/2011 4:02:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-22900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFF680000096F8, 0x0, 0x0, 0xFFFFF80002AA6A37)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 7/30/2011 5:31:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFCA001F29750, 0x0, 0xFFFFF80002E438C0, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 7/30/2011 4:15:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-15366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFCA001C4E758, 0x1, 0xFFFFF88001115920, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 7/30/2011 4:12:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-16052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFCA00261D560, 0x0, 0xFFFFF80002E0D8C0, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 7/30/2011 4:05:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-15927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B810D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 7/29/2011 10:05:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-17643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFB04009B7500, 0x0, 0xFFFFF80002AECF86, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 7/29/2011 10:59:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-18751-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B81040, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 7/29/2011 12:14:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF680036E52A4, 0x0, 0xFFFFF8800124596C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 7/29/2011 12:04:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-18798-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B81040, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 7/28/2011 5:04:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-18532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFDCA002A97AF0, 0x1, 0xFFFFF80002D5A916, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Thu 7/28/2011 2:33:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-27019-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFB3401C486FB, 0x0, 0xFFFFF80002AD75FF, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 7/26/2011 11:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-17612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFC0A0093DD010, 0x0, 0xFFFFF80002BFCF8C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 7/25/2011 11:21:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-16021-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFA803FD10A40, 0x0, 0xFFFFF80002AF92A9, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.



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

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

[Macboatmaster]

MEMTEST

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.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+-2.11.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.



Posted with acknowledgment to- rshaffer61 and other contributors to this

[Jamila'sfilter]

I have been ill this week and haven't attempted this. I will try to run this test on the weekend and post results.

FYI, after one crash dump this week ran a very quick HP diagnostic of memory; result was: Bit high test failed.

[Macboatmaster]

I will await the results of memtest, but it certainly has the indication of faulty ram.

[Jamila'sfilter]

Macboatmaster~

I ran the mem test. One pass only, but had more than 75,000 errors. I assume this is faulty RAM.

A question: Is it possible to determine which of the two memory modules might be faulty? I had one replaced in February and am not sure which one, but can go back through records to determine that. However, I still would not be sure whether the replacement module or the remaining original module is faulty.

From Belarc:

Windows 7 Home Premium (x64) (build 7600)
3062 Megabytes Usable Installed Memory

Slot 'A0' has 2048 MB (serial number E241FDC1)
Slot 'A1' has 1024 MB (serial number 5CCC275A)

[Plastic Nev]

Hi, and as a fill in till Macboatmaster returns, I only recommend this if you are confident in removing the side cover, and also if you know and can identify the RAM modules.
If so, first turn off the power to the computer and remove the cover, I assume this is a desktop machine as it has not yet been verified.
Remove one of the modules and replace the cover, if possible place the removed module somewhere safe and away from any source of static electricity.
Power up the machine and boot, then run the memtest again, if it shows a similar number of faults shut down again, remove power and swap the modules over, then try the memtest again.
It may be unlikely but bear in mind the chance that both modules could be faulty. If however the test shows clean then the faulty one is the removed one.
Once identified, I would personally be inclined to upgrade to two modules of 2GB rather than the present combination, but that is up to you of course.
Nev.

Edited by Plastic Nev, 07 August 2011 - 10:41 AM.

[Jamila'sfilter]

Thank you for your help~ --I will not be able to attempt this until next weekend, Aug. 13-14. I will post an update then.

Jamila

[Macboatmaster]

Plastic Nev
Thank you. I am obliged to you.

Jamilasfilter
Follow the advice given. The only precaution I would add, is that you take hold of the case, with both hands, after removing the panel, this will ground any static in your body. Work on a non-static producing surface, not a nylon based carpet, as these are bad at creating static. A tiled floor is OK. At each end of the stick of ram you will see a clip, normally white or grey colured. Unless the processor is dual core, when in addition to the A slots you will likely have B slots. If this is the case the respective slots may be blue and yellow and the clips may be black. There could be other colour combinations. You release these clips by moving them AWAY from the stick of ram. The ram will itself then release. Look carefully at the ram and on the edge that goes into the slot, eg the edge with the contacts, you will see that it is itself slotted, so that it may only be inmserted ONE way. Be careful that its the way you are trying to reinsert it. As you gently press down on to the top of the ram stick, it will automatically locate and the plastic clips will close again.

After testing the one stick as advised by Plastic Nev, ensure you AGAIN take the static precautions.

This MAY be of additional help
. If you need to remove an existing module, gently push down on the clips on either side of the RAM socket. The module will pop up slightly and should be easy to pull out. 5. Take the new RAM modules out of their static-free envelope and place them on top of the envelope. Always hold a RAM module by pinching the edges of the module; avoid touching the chips or circuitry on the face.

6. To install a module, open the latches at each end of the RAM socket by gently pushing them down. Line up the notch at the bottom of the memory stick with the corresponding bump in the memory socket. Touching the top edge of the module, gently push the piece down into the socket; the latches at either end should rise and lock. Gently press each latch toward the edge of the RAM module to confirm that it is completely closed.





PLEASE NOTE the image is not meant to represent what your setup will look like, but it provides a general idea.

Edited by Macboatmaster, 07 August 2011 - 03:20 PM.

[Jamila'sfilter]

Macboatmaster,

Thank you for these detailed instructions. I will post again next weekend with an update.

Jamila

[Jamila'sfilter]

Macboatmaster,

I have had both memory modules tested and found that one was faulty, as expected. It has been removed. I haven't yet replaced it, but the computer has worked consistently with no crashes for the past 24 hours, and processes are running much more quickly.

However, my difficulties with email are not resolved, so I would ask your recommendation on how to proceed with that issue.

Again, I am using Windows Live to download from an sbcglobal.net account via Yahoo (I do not have a hotmail account). The messages download with no problems, and show up in my inbox as unread. However, after I open them, they no longer appear in the inbox. (They do remain on the server.)

Also, if I download messages, then click away from the inbox before opening those new messages, when I click back on the inbox, they are no longer visible.

The glitch has removed all messages from my inbox back to Feb. 5, 2011. Older messages remain.

The program also crashes frequently.

Thank you for any suggestions you can offer.

Edited by Jamila'sfilter, 15 August 2011 - 04:50 AM.

[Macboatmaster]

I am pleased that we appear to have solved the main problem
I am not the person you need to help with the other matter as I do not use Windows Live

I will, in your best interests, leave that aspect for someone else to help.
Good luck wih it.

Edited by Macboatmaster, 15 August 2011 - 05:19 AM.