Random BSOD, "Unknown Device" error in perfmon

[doggie3]

I'm getting seemingly random blue screens on a regular basis. Blue Screen View blames ntoskrnl.exe, so make of that what you will.

I no good at computer

OS: Windows 7 home premium 64 bit
Installed 3 weeks ago, when the system was built. I didn't build it, the guys I ordered it from did (hardwareversand)

Any help would be greatly appreciated.

 

[zigzag3143]

About 1/3 of these crashes are blamed on memory corruption directly. Some of the others indirectly.

These crashes were caused by memory corruption (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!!!


1-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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-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.

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


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

 

[doggie3]

When you say disable overclocking, does that include intel turbo boost technology? (enabled by default on this mobo)

 

[zigzag3143]

When you say disable overclocking, does that include intel turbo boost technology? (enabled by default on this mobo)

No turbo boost (done by the mfr) is what your components are designed to do. Over clocking traditionally means pushing the cpu/ram faster than they were designed for.

 

[doggie3]

Ok so I think I've discovered the problem but I'd like some input before I spend any money.

I ran the memtest several times on each stick of ram separately. One was clean as a whistle. The other gave me literally hundreds of thousands of errors, regardless of the slot it was plugged into.

So, what are the chances this is the cause of my problem?

 

[zigzag3143]

Ok so I think I've discovered the problem but I'd like some input before I spend any money.

I ran the memtest several times on each stick of ram separately. One was clean as a whistle. The other gave me literally hundreds of thousands of errors, regardless of the slot it was plugged into.

So, what are the chances this is the cause of my problem?

Pretty good. Like anything else RAM does go bad. It may still be under warranty.