BSOD playing Runescape

Code:

BugCheck 50, {fffffa0002e75e46, 8, fffffa0002e75e46, 7}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43781 )

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

A invalid memory address was referenced, which in this case was a a memory address residing in the non-paged pool region which is only reserved for Kernel Mode drivers and processes.

Remove:

Code:

Start Menu\Programs\Norton Internet Security

Norton is known to cause BSODs, and you also have Avast installed (keep this) you should never run two real-time protection programs on the same computer, since this can reduce performance and cause conflicts between the two programs which can result in crashes. Use the Norton Removal Tool to remove Norton.

Reduce the number of programs at startup, to avoid any driver or program conflicts:

• Troubleshoot Application Conflicts by Performing a Clean Startup
• Startup Programs - Change

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

thanks ill keep you updated.

Your welcome.

hey just had another bsod while running driver verifier.. how should i react? ill attach the dump file.
thanks.

Code:

BugCheck C1, {fffff980256d8e10, fffff980256d826d, 901f0, 32}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )

Code:

Usual causes:  Device driver, Memory

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

I've run the program for 1 hour so far and have gotten 1 pass and 377 errors.. Should I stop it or continue? Thanks.

I would stop the test. Have you managed to determine if it was a bad slot or a bad stick?

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.