Infrequent but persistent BSOD problem

[Horazon]

Hi all,

I'm having an annoying bsod problem on my 2 month old laptop.
It happens infrequently (once every 2-3 days) but i can get unlucky streaks.
The first bsod happened when i was installing windows for the first time, which leads me to believe it is a hardware issue.
Can you help me pinpoint the faulty component?
If it is something easy to replace i'd prefer to do it myself rather than losing weeks on sending it back.


system info:

Clevo P170HMx
Intel i7-2820-QM CPU
8 Gigs of DDR3 RAM
Win7 Home Premium x64 full retail

 

[marsmimar]

Hello Horazon and welcome to Seven Forums.

Until one of the BSOD experts responds to your log, you might also check the Event Viewer to see if anything significant occurred around the time of your last BSOD.

What information appears in event logs (Event Viewer)?

 

[Horazon]

Hello Horazon and welcome to Seven Forums.

Until one of the BSOD experts responds to your log, you might also check the Event Viewer to see if anything significant occurred around the time of your last BSOD.

What information appears in event logs (Event Viewer)?

Thanks!

Apart from the critical kernel-power error entry at the time of the bsod there is a steam client warning 15 minutes before and some dns client warnings half an hour before , nothing related to the bsod i think.

 

[Horazon]

I still have this issue, please help.

 

[zigzag3143]

Hi all,

I'm having an annoying bsod problem on my 2 month old laptop.
It happens infrequently (once every 2-3 days) but i can get unlucky streaks.
The first bsod happened when i was installing windows for the first time, which leads me to believe it is a hardware issue.
Can you help me pinpoint the faulty component?
If it is something easy to replace i'd prefer to do it myself rather than losing weeks on sending it back.


system info:

Clevo P170HMx
Intel i7-2820-QM CPU
8 Gigs of DDR3 RAM
Win7 Home Premium x64 full retail

Memory management caused by an unknown driver please run these two tests.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

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

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.

 

[Horazon]

Driver verifier bsods the machine before i can get into windows sadly, i had to start in safe mode. Running memtest atm

update:
memtest gives about 90 errors in total in test #6 and #7
I didnt have time to test each ramstick individually yet