Random BSOD error 0x1000009f

[corinthianuk]

Hi I could do with a little help as I am out of my depth, I am experiencing random BSOD's with 64 bit windows 7 on a refurbished desktop I bought. I have been having these BSOD's for months, at first suspecting my graphics card, I swapped out the graphics card with one I knew was working but to no avail, I have run various stress tests and cannot force a crash.

I have looked around the internet and see that the motherboard on my Desktop looks a bit iffy but am unsure if it is ultimately the problem and would appreciate any help or constructive comments.

I have tried to follow the procedure for reporting a BSOD, please advise if I have missed something crucial

My PC is an HP Pavilion m9765uk

Windows 7 Home Premium
- x64 ?
-originally it had vista and an OEM version of windows 7 put onto it when I purchased it

- What is the age of system (hardware)? 2 years
- What is the age of OS installation (have you re-installed the OS?) 18 months no reinstall

i7 920 at 2.67 Ghz not overclocked
Nvidia 9600GT graphics again not overclocked
6Gb Ram
integrated sound


I have a TV Card which I have disabled to try and rule it out

I would appreciate any help anyone can provide as its driving me nuts

Steve

 

[Vir Gnarus]

The causes are pretty much scattered all over the place. A good bit are 0x101 bugchecks which can't be debugged without at least access to a kernel dump (minidumps too small). WHEA errors too which consistently tell that there was an internal timer failure in the CPU.

There may be a possibility this is software, despite the symptoms appearing hardware-based in nature. There's some drivers I saw that are rather odd or just plain old. Your RAID controller drivers look pretty stale (Nov 24, 2010) so any updates at all would be good. You will want to go to the HP website and download pretty much any driver updates related to your hardware, as they all look a couple years old. Even if the updates still appear old, you will want to try them as any update at all is better than none.

As for the odd driver, it's called bridge.sys located in \Windows\system32\DRIVERS\ directory. It's quite old (2009) and from googling it and looking at the driver databases the only basic information I can come up with it is it's some MAC Bridge driver. I'm not sure why you would need any bridge connection of any kind for your system. Try renaming it to bridge.BAK and restart the computer and see what happens (like if your PC starts running ok again). I'm worried that this thing may be the product of a viral infection however, so be warned that may be the case. If you personally suspect infection, there's a security forum here at SF with people that will assist you there in detection and removal.

Aside from these, you can also start running some hardware tests as well as log some temp/voltage data for us, as instructed below:


RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.