BSOD crashes frequently

I was here a little while ago and was suffering from BSOD's, you helped out (thanks) it turned out to be a memory crash and was a timing issue in the bios. My system has been fine for a while and now i am back to bsods. I have checked the memory and run the memtest etc and all seems ok.

Well, since I dont have the debugger installed, I can't check you minidump... (too lazy to install it )
I'll leave that to Howard

However, more information would help in spite of you providing the minidump.
Like - when does the crash happen - at random, gaming, running some app...?
When did it start happening - can you remember if you updated drivers about that time or installed a new program?

Have you tried loading 'safe defaults' in the bios and if the problem is gone, start changing settings to your previous ones until you encounter the problem itself?
Are you overclocking? - it's known that even though memory or CPU can take a certain bump in the beginning, this bump in frequency tends to get lower and lower over time - thus requireing lowering the OC or slack timings... (or upping voltage, which in turn may or may not help, or even makes the problems worse).

Just guessing for now, until someone analyzes the minidump (hint to howard )...

2 minidumps crash at ShldDrv.SYS. Panda. They have bugchecks of 0A, and 50.

2 minidumps crash with memory corruption, and a bugcheck of 4E.

2 minidumps at ntoskrnl.exe. Windows boot up kernel. They have a bugcheck of 8E.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

0x0000004E: PFN_LIST_CORRUPT

This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Faulty ram is probably the culprit. It could also be caused by faulty video ram/L2 cache ram of your cpu/Faulty mobo/psu

Check your mobo for bulging, or leaking capacitors. See HERE for more info.

I believe the culprit is faulty memory. Your windows is crashed randomly and this is the symptom of hardware error. One minidump has one bit memory corruption and one minidump has memory access fault. All of the evidence show that it is faulty memory. Failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM.

I don't think you have to run memtest as the minidump confirms that it is faulty memory.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor

If it still crashes, diagnostic which memory stick is faulty
Take out one memory stick. If windows does not crash, the removed memory stick is faulty.

Mini121905-01.dmp
BugCheck 1000000A, {fffff124, 1c, 0, 804e3336}

Probably caused by : memory_corruption

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff124, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e3336, address which referenced memory

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.