BSOD on a new computer/OS...

[erezh]

Hi.

Windows 7 Ultimate 64 bit installed only once on a brand new three weeks old computer.

Been having BSODs, while also "Display driver amdkmdap stopped responding and has successfully recovered" messages in the events log.

I naturally suspect the graphic drivers- though installed fresh to the latest version: Catalyst 10.8.

Hardware? Drivers?

Please help me find a solution to this problem, as this is a brand new computer and I can't even start to enjoy it...

Thanks!

Erez

 

[zigzag3143]

Hi.

Windows 7 Ultimate 64 bit installed only once on a brand new three weeks old computer.

Been having BSODs, while also "Display driver amdkmdap stopped responding and has successfully recovered" messages in the events log.

I naturally suspect the graphic drivers- though installed fresh to the latest version: Catalyst 10.8.

Hardware? Drivers?

Please help me find a solution to this problem, as this is a brand new computer and I can't even start to enjoy it...

Thanks!

Erez

Hi Erez and welcome


4 of 8 crashes are directly caused by memory management, and several others may be as well. There is also one caused by a registry error

I would do this

1-run a memory test

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.

If your memory passes I would then

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.


If you still have problems we can run a driver verifier to see which driver is causing the crashes

Beyond that, please run Verifier with these settings:

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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Let us know the results

Ken

 

[erezh]

Hi Ken;

First, thanks for the quick reply!

I did not run the memtest86+, but yet tested the memory using the Windows 7's "Windows Memeory Diagnostics" (finding no problems). Isn't that good enough?

You also wrote the same for stage 1 and 2- I assume you meant to suggest something else if memtest86+ passes?

Theretheless, I will run the verifyer as you suggested and return here with results.

Thank you!

Erez

 

[zigzag3143]

Hi Ken;

First, thanks for the quick reply!

I did not run the memtest86+, but yet tested the memory using the Windows 7's "Windows Memeory Diagnostics" (finding no problems). Isn't that good enough?

You also wrote the same for stage 1 and 2- I assume you meant to suggest something else if memtest86+ passes?

Theretheless, I will run the verifyer as you suggested and return here with results.

Thank you!

Erez

hi Erez

1-nope. win 7 memory test doesnt stress the memory enough. Memtest, or others like it do. memtest needs to run for a long time overnight at least.

2-Ugh, my bad. I am stretched too thin. I will go back and fix the post..

3-Verifier is as stated an ify proposition. It usually will tell you the errant driver, probably crash your system, and sometimes be no help at all. Leave it for last unless nothing else fixes it



Good Luck

ken J


edit second part of previous post changed from memtest to system file check, thanks Erez.

 

[erezh]

Thanks Ken,

I will do as you suggested and return with result.

Erez

 

[zigzag3143]

Thanks Ken,

I will do as you suggested and return with result.

Erez

Blackviper has several levels or mods. try the safe one first

K

 

[erezh]

Hi Ken.

Update so far- memtest86+ found no problems, as expected.

Same goes to SFC.

A friend offered to see if the CPU cooler is installed correctly, and suggested that the PSU might not be enough causing "brown-outs".
I'm about to check the hardware installation, but what about my PSU capability? Should it be enough for my specification (Please see complete spec in my profile)?

Thanks!

Erez