Multiple BSODs on company computer. Dumps/reports included.

I have a client (company) who I've built and connected multiple computers for--all with the same hardware. All but one out of 8 have been great. This last one is causing me hell. I've analyzed the dumps (but I'm a rookie to crash dump examinations), and I originally thought it was a graphics driver issue. I removed the card from device manager, driver swept the drivers, and installed the newest drivers after the re-install of the card. Still two more BSODs (see the last two dumps for that). Any help would be greatly appreciated since I don't know much about these dumps.

Specs:

Windows 7 Pro x64
Original OS
Full Retail version
System is 4 months old
OS installed when system was built

These crashes were caused by memory corruption/exception (probably a driver).

Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

I didn't include this in the initial post, but I had run driver verifier and the 013112-17456-01.dmp is what happened. The client ran system repair immediately after, because he couldn't boot into Windows.

I have attempted memtest, but that was when I initially stressed the computers It went through just fine after 20 passes (overnight). I can try it again, but that's very difficult since it's a company computer. I can't keep him down during working hours.

Always a good idea to include all troubleshooting methods in your first post thus saving your's & the clients precious time.

Jester5510 said:

I didn't include this in the initial post, but I had run driver verifier and the 013112-17456-01.dmp is what happened. The client ran system repair immediately after, because he couldn't boot into Windows.

I have attempted memtest, but that was when I initially stressed the computers It went through just fine after 20 passes (overnight). I can try it again, but that's very difficult since it's a company computer. I can't keep him down during working hours.

The only verified DMP does indeed point to the video driver. Since the "client" ran a repair it is no longer valid.

You may be running a subset of all the drivers and the errant one isnt included.

You should try "all drivers installed..."

You have to ask the client (I have been there as well) if he would rather be without the machine for 24 hours or live with the crashes and risk losing valuable data.

Did you run memtest on single ram sticks as well? Did you run a known good stick in the mobo slots?

zigzag3143 said:

Jester5510 said:

I didn't include this in the initial post, but I had "all drivers installed" selected. I had run driver verifier and the 013112-17456-01.dmp is what happened. The client ran system repair immediately after, because he couldn't boot into Windows.

I have attempted memtest, but that was when I initially stressed the computers It went through just fine after 20 passes (overnight). I can try it again, but that's very difficult since it's a company computer. I can't keep him down during working hours.

The only verified DMP does indeed point to the video driver. Since the "client" ran a repair it is no longer valid.

You may be running a subset of all the drivers and the errant one isnt included.

You should try "all drivers installed..."

You have to ask the client (I have been there as well) if he would rather be without the machine for 24 hours or live with the crashes and risk losing valuable data.

Did you run memtest on single ram sticks as well? Did you run a known good stick in the mobo slots?

I actually did select all drivers installed. That's when this crash happened. Also, I did uninstall, driver sweep, and reinstall the newest drivers after the driver_verifier crash. That didn't seem to help. Given that, I think your call on the memtest is the best route.

Now, I exchanged his RAM initially when I built the computer, as a couple of BSODs occurred. It cleared it up. Now, a couple of months later, they're appearing again. I can go in on the weekend and run the memtests to minimize downtime for him, or I can just swap out two good sticks of memory and "hope". Suggestions on which is the best approach in your experience?

If that still doesn't work, my last option would be a video card replacement.

Jester5510 said:

zigzag3143 said:

Jester5510 said:

I didn't include this in the initial post, but I had "all drivers installed" selected. I had run driver verifier and the 013112-17456-01.dmp is what happened. The client ran system repair immediately after, because he couldn't boot into Windows.

I have attempted memtest, but that was when I initially stressed the computers It went through just fine after 20 passes (overnight). I can try it again, but that's very difficult since it's a company computer. I can't keep him down during working hours.

The only verified DMP does indeed point to the video driver. Since the "client" ran a repair it is no longer valid.

You may be running a subset of all the drivers and the errant one isnt included.

You should try "all drivers installed..."

You have to ask the client (I have been there as well) if he would rather be without the machine for 24 hours or live with the crashes and risk losing valuable data.

Did you run memtest on single ram sticks as well? Did you run a known good stick in the mobo slots?

I actually did select all drivers installed. That's when this crash happened. Also, I did uninstall, driver sweep, and reinstall the newest drivers after the driver_verifier crash. That didn't seem to help. Given that, I think your call on the memtest is the best route.

Now, I exchanged his RAM initially when I built the computer, as a couple of BSODs occurred. It cleared it up. Now, a couple of months later, they're appearing again. I can go in on the weekend and run the memtests to minimize downtime for him, or I can just swap out two good sticks of memory and "hope". Suggestions on which is the best approach in your experience?

If that still doesn't work, my last option would be a video card replacement.

Memtest first (might be a mobo slot).

Stress tests (in the current configuration)

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 105ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

CPU Stress Tests:
- http://downloadcenter.intel.com/Deta...19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

Verifier for more than one crash since it is an "iffy" proposition.


System specs and network setup would also be helpful.