Corrupt-modulelist Type 0

[janetbinbum]

Corrupt-modulelist Type 0
Can anybody help with this probelm please, i have no idea how to fix it.


Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.2
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini121409-04.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 1000008e
BCP1: C0000005
BCP2: 8204A96A
BCP3: 812D3B30
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: c89648af-2b24-4c50-8cc8-a193033cb185

. CORRUPT_MODULELIST, C:\windows\minidump\mini010710-03.d C:\Users\ELLIOTT\AppData\Local\Temp\WER-129699-0.sysdata.xmal
C\Users\ELLIOTT\AppData\Local\Temp\WERF7B6.tmp.Ver sion.txt
C:\ProgramData\microsoft\windows\WER\Report0fa3297 f
keywords- 0x80000000000000

It happens when i am using the internet and will not load some websites, it will try for a certain amout of time and then the bluescreen will appear and then the computer will shut itself down and restart. Any advice?

[Glenny]

Check out the following threads, you may possibly find a solution for the "blue screen" and "Corrupt-modulelist Type 0":

1. Blue Screen STOP: 0x000000D1 in Windows 7
2. Windows XP Crash Blue Screen
3. PROBLEM WITH BLUE SCREEN - PHYSICAL MEMORY DUMP
4. Bad Pool Caller Blue Screen

[Elieis]

Damage RAM stick is the common cause behind blue screen. It can occur while adding a new ram or with the existing one. You can go ahead with simple troubleshooting tips to fix the same. First try to remove the ram stick and clean the lower edges. Then place them back. If you have two ram stick then remove one of them and test. If the system stops crashing them among two ram one might be damage. I got this issue on my laptop which has dual ram and one of them had stopped working. But as I removed the damage one the issue is resolved.

[Agavoli]

Without removing the ram sticks you an find out whether any of those is proper or not. You can try using Memtest. It work through bootable disc format. Try to burn the iso file on a cd and then boot your system with the same. Then run a full ram scan. If you get any error popup then one ram stick from both is not proper. If you won't get any error from this then the second option left is to go ahead with checking out damage system files. You can run sfc /scannow from cmd and try to find the problem.