BSOD's occurring frequently, mostly error 0x00000124

The latest driver update will contain all the previous fixes.

Code:

BugCheck D1, {0, b, 8, 0}

Probably caused by : atikmdag.sys ( atikmdag+f2ec7 )

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04800000 fffff880`05134000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Apr 20 02:53:29 2011 (4DAE3C99)
    CheckSum:         008E91DD
    ImageSize:        00934000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update to the latest WHQL AMD graphics card driver, it seems to have used a NULL instruction pointer.

Latest AMD Catalyst Video Driver for Windows 7

I've updated both my BIOS and AMD driver as you requested and I'm still unfortunately having the crashes.
I've had a single bluescreen since then as the rest are complete freezes (screen locks up requires hard reset, screen goes black as if PC has been turned off despite system remaining on requiring hard reset). I'll upload the bluescreen that occurred yesterday.

Two of the crashes today forced the sound in my headset to crackle whenever sound from anything was heard and forced all the applications I had opened to not respond and close themselves. Not sure if this is to do with the new changes I've made with the driver and BIOS updates.

Code:

BugCheck 4E, {99, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

This bugcheck is caused by a corrupt PFN or PTE, as a result of a Bad Share Count, the Share Count is the number of PTEs which point to a physical page, Working Set Trimming will typically reduce the Share Count, as well as, the freeing of virtual memory.

Code:

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`033fb1d8 fffff800`02d1847c nt!KeBugCheckEx
01 fffff880`033fb1e0 fffff800`02cfa49b nt!MiBadShareCount+0x4c
02 fffff880`033fb220 fffff800`02d002a1 nt! ?? ::FNODOBFM::`string'+0x31b67
03 fffff880`033fb2a0 fffff800`02cc946e nt! ?? ::FNODOBFM::`string'+0x3806d
04 fffff880`033fbb30 fffff800`02c87ad3 nt!NtFreeVirtualMemory+0x2de
05 fffff880`033fbc20 00000000`770af89a nt!KiSystemServiceCopyEnd+0x13
06 00000000`02dee118 00000000`00000000 0x770af89a

I would run Driver Verifier again, and also test the RAM for any possible issues too:

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 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.

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.

I apologise for again double posting, but it's been a week since I received my last bit of advice for my problem. Are there any other recommended procedures for me to figure out my problem?

Thanks.