Vista 64 BSOD (Blue Screen Of Death). Do I need to re-install?

Hello,
About two weeks ago I had a catastrophic failure of my X45 joy stick (Read: "I busted the throttle handle off my 6 year old unit"). Upgrading to the X52 pro was long over due, so I shopped around and ordered one. My machine is just over 6 months old and has been stable with my old config that entire time. I also have the Saitek flight Pro Yolk, and Saitek Pro rudder peddles. (I've also built a virtual cockpit, as an example of how serious a flyer I am.).
But with the addition of the X52 Pro stick I started to experience problems. It started where my flight sim, IL-2, would stutter. This progressed to desktop crashes, and now I'm getting Blue Screens of Death (BSOD), with the text "BAD_POOL_COLLECTOR". At first I was only getting these BSOD's while in IL-2, so I thought that piece of software was the problem. But now I am getting them from Aces High II as well. This told me that something else was the problem. I updated all the drivers and the SST software to the latest versions I pulled off your [Saitek's] website. But this did not resolve the issue. I then started to do some debugging on my own.
I gathered the info to read the memory dumps (Read the Debug Memory dump.
http://forums.majorgeeks.com/showthread.php?t=35246) and found that the problem was with the driver "SaiH0762.sys". When I looked up this driver I found out that it belongs to you guys [Saitek], so you get the first tech support email. To facilitate trouble shooting this ticket I've included the following: A list of my peripherals. A synopsis of my system environment. The relevant excerpt of the memory dump. An attached file with my DxDiag dump. Attached the last two BSOD Memory Dumps


I fired off the above email to Saitek and asked them for advice. They wanted the X52 unit back for testing. But there were other, long standing problems with this computer I realized, and I thought I might try fixing them before I paid to ship a new joy stick back to the manufacture. For about two months now I've been having two other problems, but I've been ignoring them because they wern't causing me problems and I didn't want to mess with them. They are:
I don't know what the HP MediaSmart TV is, I don't use it, I just wanted the errors on my system to go away so I could prove my system was stable before sending in the Joystick. So I contacted HP support to try and resolve these two problems. Their technician made a remote connection to my system and tried to do the update for HP MediaSmart TV herself, but got the exact same results. Then she had the idea of creating a new Admin user and trying the update under that profile. This is when things turned scary. Every time she would try to make a remote connection to my machine it would BSOD. So she talked me through the install to the HP MediaSmart TV update using the new Admin profile. But I got the same result. To make matters even more scary, I started getting BSOD's when doing simple tasks like "Log off user admin" = BSOD. "Exit application <Several at random>" = BSOD <Also at random>
The HP tech, knowing that the .NET framework was a part of this equation, now proposed that my .NET framework was corrupt and my system needed to be flashed back to the factory install (This would, of course, wipe all my data, save games, game profiles, emails, and basically make the machine like I just got it from the vendor). I've already started the process of backing up as much of my data as I possibly can. But I'm still looking at a week of installing software, and configuring this machine to get it back to where it is now. A prospect I am not looking forward to. So, before I take that draconian step, which I am preparing for, I thought I would ask you folks if you have any input. I've attached all my Raw Mini-dumps, and a DxDiag to facilitate Analysis.


System:
OS: Windows Vista 64. Home Premium SP2
Processor: Intel Core i7 CPU 920 @2.67GHz
Memory: 6.00 Gb
HD: 640 GB (Dual 326Gb disks in RAID 0 configuration)

Peripherals:
Saitek Pro Flight Yolk
Saitek Pro Flight Rudder Peddles
Saitek X52 Pro (Replaced X45 that was stable and did not cause this problem)
Track IR 4 with Vector Clip.

Excerpt of BSOD Memory Dump: Saitek Driver
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 110b, 4040000, fffffa800a248010}

Unable to load image \SystemRoot\system32\DRIVERS\SaiH0762.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SaiH0762.sys
*** ERROR: Module load completed but symbols could not be loaded for SaiH0762.sys
GetPointerFromAddress: unable to read from fffff8000206f080
Probably caused by : SaiH0762.sys ( SaiH0762+1974f )

Example of BSOD Memory Dump: Log off
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800020931b2, fffffa600a831ef0, 0}

Unable to load image rcmirror.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rcmirror.dll
*** ERROR: Module load completed but symbols could not be loaded for rcmirror.dll
Probably caused by : rcmirror.dll ( rcmirror_fffff96000a00000+1096 )

I'm running Windows 7 64bit and I've also been having BSOD's whilst using my X52 Pro and after troubleshooting the issue it returned that SaiH0762.sys is most probably the cause of the issue.

I've had to reinstall my OS a couple of times due to getting a new HDD but the problem has persisted so I don't think a reinstall will fix your problem.

Looks like we're in the same boat.

============ UPDATE ===================

I called back HP to get an extension of my ticket while I waited for a second opinion from this website. Instead I got a hold of a tech who really seamed to know what he was doing. He asked some better questions, which got me confident enough to allow him to connect to my machine. He poked around in places the other tech's never even ventured, and then had me run a bunch of stress tests that I don't think the previous tech's knew about. We ran a Video Card stress test: passed. We ran a memory stress test; Passed. We ran a CPU stress test: Machine locked up hard about 70% of the way through. This got us looking at the CPU, though there was a HUGE memory hogging app running just before the box seized.
Perhaps the app was something related to the processor test, but the tech had never seen it before during other runs of that same test. Also, the tech doc on the error codes from the memory dump files - the same ones I posted here for you folks - seemed to indicate that the problem could be a bad memory. So even though it may still be a memory issue, because it locked during the processor test, the Tech was about 80% confident we had a Core Processor issue. The Core Processor, unfortunately, is the only unit that HP won't send out for field installation. So I'm expecting a Self Addressed Stamped BOX to arrive today so I can send the tower back to the manufacture (I'm still under full warranty).
They will put in a new processor, and if necessary new memory, and even a new video card (the focus of another ticket I had with HP because of my game ARMA II, which kept crashing and I never got a full resolution to). I won't have my gaming box for about 7 to 9 days, so I'll have to get some real work done I suppose.

In the end I tried not to prove out my prejudices, but failed. All of the other techs I had dealt with until this guy were obviously Indian. They all had the Indian accent. This guy didn't. I was hoping that he was just American trained, and had lost his accent. Perhaps he was in a different country? The Ukraine or Balkan States perhaps? And they were better at emulating an American accent? In the end I just had to ask. He told me that all he could tell me was that he was on the "West coast, in a state that touched the ocean." it's as specific as he would get. But still, American.
And so it was, a prejudice that everyone complains about, proven in sharp contrast:
American Technician = determined, educated, resourceful, initiative, results - Hard hardware issue identified.
Indian Technician = Polite, script reader, Format-C.

Please help me too!!! Tried everything!!! Keep getting "Volume appears to contain one or more unrecoverable problems, corrupt file system etc. Cannot go into safe mode..... Windows will not load....Fixboot cannot find system drive.........windows boot config does not contain valid os entry..Please help!!!!!

Dose the Joystick have a 64 bit driver meant for windows 7? I know some hardware out there still doesnt have 64 bt drivers and that causes problems. If there is no Windows 7 driver did you try the Vista Driver? Sometimes that works too.

Hope it all works out for you.

PS, I also have a joystick set up on my left, throttle on my right, and foot petals on the floor. Gotta Say mechwarrior is awesome with these..lol