Hey there. Just an idea while you are trying to diagnose.
You have a couple PCs without an issue and all are same?
Maybe cloning from a working one with sysprep while keeping drivers would work?
You will have to decide on feasibility of such an act though. Seems a lot of work.
Take care
Thanks, I think the internal IT will run the Memtest at end of day, if not I will head out there monday, and I will send you the drivers list. As much as i don't think its a memory issue, the one like this that pixel-ate make me think it might be on some of them, like this one. Here is the updated driver list.
So I thought maybe that was an issue, they have a Sysprep image that they loaded from. But the machine that I started diagnosing, they gave me with factory HP image, to make sure. So we have tried both, that was one of our first thoughts, a corrupt image, that's a great idea, if we can find one that doesn't crash. Ill ask the guys. At this point the with the amount of BSODs, if it was for sure because of an image, we would re-do it.
Last edited by technaustin; 15 May 2015 at 13:32. Reason: modify wrong text
Almost all the drivers are outdated there. QLogic, Adaptec ... all those.
If memtest86+ comes free of errors, teh best deal for you would be perform a Clean Reinstall - Factory OEM Windows 7
You were correct from the start, my boss found an incompatibility between this model and the CPU_Z driver used in our monitoring software, thanks so much, as soon as he mentioned that I knew what to look for thanks to your expertise. BSOD issue solved, now gotta figure out why they crash /pixelate sometimes. There are still outdated drivers we are working on, but ever since we have removed the sensor feature we haven't had any issues with BSOD.
Quote