BAD_POOL_CALLER problem

[DingleJohn]

I have a problem with my computer.
The last month I have had serial problems with different kinds of BSOD's.

First, my system:
MSI P965 Platinum, Bios 1.7
Intel E6600 Rev B2 @ 3.15 Ghz
OCZ OCZ2T8002GK @ 1.05 Ghz
MSI ATI X1950 pro (Ram is underclocked with 7 mhz, Dont know why..)
WD Caviar SE16 WD2500KS (SATA)
Maxtor DiamondMax 10 250 GB (IDE - Slave cable position)
Lite On DVD-burner (IDE -Master cable position)
Fortron Blue Storm II 500W PSU (Makes screeching noises in standby)
Creative SoundBlaster Live! 24 bit External
Microsoft Windows Vista Ultimate x64

Okay.. Here we go..
My harddrives and DVD drive are controlled by a Jmicron controller.

About a half year ago I shifted from Windows XP til Vista because of the evil BSOD.. That was probably my Soundblaster's fault.
Then I shifted to Windows Vista x64 where, as I can remember, I had the same problem, maybe with a couple other BSOD, it became very instant and I shifted til Windows Vista x86, where I didnt had that many problems with BSOD's.. But Now I have shifted back to X64 and after 14 days of usage I got A LOT of BSOD's..
Here are some of my BSOD's:
http://www.fuscrew.dk/incomming/BSOD/PICT2740.jpg
http://www.fuscrew.dk/incomming/BSOD/PICT2741.jpg
http://www.fuscrew.dk/incomming/BSOD/PICT2742.jpg
http://www.fuscrew.dk/incomming/BSOD/PICT2744.jpg
http://www.fuscrew.dk/incomming/BSOD/PICT2746.jpg

I updated my BIOS and my Jmicron devicedriver and now I only get the Bad_pool_caller BSOD, like this: http://www.fuscrew.dk/incomming/BSOD/PICT2740.jpg
As I can read on the Internet, this is usually caused by a device driver. Installing "Driver Detective" I can see that the only driver I that arent "up-to-date" is my Intel ICH8 device drivers. Downloading and installing the drivers from Intel.com did not help alot, because the x64 drivers is older than the x86 drivers on their website.. Another posibility is my Realtek MSI driver who is screwing my computer. An agument for that could be that I usually get my BSOD while playing TF2 with a Skype conversation open.
It could also be a Hardware error, but I have tested my Memory with memtestx86 and i gave me random results with random errors..
What can I solve my BSOD and what do you think causes my BSOD? A solution could really make my day/year/christmas!

PS. Just did a Prime-test and I got an error after 17 minutes. What could have caused that Error?

 

[raybay]

I wouldn't rule out anything. The Fortron power supply is a very good unit, but any power supply can go bad.
If it were mine, I would start over.
MSI motherboard, Reformatted WD Caviar SATA Drive as a clean install (or the DiamondMax but not both), power supply, memory, video card, onboard ethernet socket, and one optical drive. Windows XP SP 2, using the latest drivers for the video card.
Then download all the microsoft updates. Then defragment.
Then run Memtest86 on the memory for four hours or seven passes.
Then upgrade to Microsoft Interent Explorer, and run the computer again, working it for a day or two.
Add your software for word processing, Adobe Acrobat, Flash, Shockwave, Java, etc. and other utilities.
Add the soundcard, and run for a day.
Keep adding one component at a time as long as it works for 24 hours.
I would not add the second hard drive until the end of the cycle. The DiamondMax is a horribly unreliable drive.
Be ready to trade out your power supply for one of the tests.
Keep good notes for each change you make.
I would not reinstall Windows VISTA ever.
Good luck. Be sure to let us know what you discovered. Somewhere in this chain, the problem will recur.
Be sure to watch your Device Manager carefully for red or yellow flags.
Be sure to check your Event Viewer in Control Panel->Administrative Tools->Computer Management->Event Viewer for errors, events, pauses, hangs.

 

[DingleJohn]

I tried to adjust my memory voltages from 2.1 to 1,9v with helped! The Funny is that the Recommended voltate from OCZ is 2.1.. So it looks like a RMA on my OCZ modules.. I will try an memtest past the night to make sure that they are stable at 1.9v.

 

[vegasgmc]

Ive gotten that error with Vista 64, caused by the nVidia chipset driver. Going to an older version of the driver cleared it up.

 

[DingleJohn]

Looks like my computer are completely stabel with my RAM voltage set to 1.9v. Is this a memory error or my motherboard? Pretty annoring that i cannot overclock my OC-garantied RAM..

 

[raybay]

Most likely a motherboard, or perhaps a BIOS, issue.

 

[DingleJohn]

As I can see my Memory arent stabel at even 2.1 or 2v. But they fail not as often at 2v as 2.1. But are you saying that I should try my Memory in another computer to make sure that if it is my Memory or Motherboard who are the "Criminal"?