Repeat Blue Screen during Start-up for New Computer

yuen · 25 Sep 2010

Hi,

I recently purchased a new custom built computer from NCIX. Unfortunately, after installing my OS, my computer has started to blue screen, usually when starting up (sometimes after log in). I have tried reformatting my computer (twice) and nothing has been resolved. What is unusual is that once I've been able to load onto the OS desktop, I'll be able to restart the computer most of the time after that without a bluescreen. However, if I turn off the computer and turn it back on the next day, I will most likely get the blue screen repeatedly on start up again. After around 5-6 blue screen restarts, the computer will normally be able to load onto the OS desktop.

I have done the BSOD Dump and System File Collection step, but am having trouble with the System Health Report step. After running the report, I will get this message "Error: An error occured while attempting to generate the report. The service did not respond to the start or control request in a timely fashion". As a result, I have not been able to get the PERFMON HTML file. I have tried running performance monitor as an Administrator, but I get a completely different screen with different menus.

Regardless, I have attached the Windows_NT6_BSOD_jcgriff2 zip file for reference. Please let me know what I can do to get the System Health Report.

Here are some basic information on my computer:
Operating System: Windows 7 Professional 64 bit(Installed using a Windows 7 Premium 64 bit CD, then did a Windows Anytime Upgrade to professional with an activation key I purchased from Digital River)

Video Card: XFX Radeon HD 5850

- purchased from NCIX in July, 2010
- the OS age is new, and I have reinstalled the OS twice.

Thanks for any assistance, I appreciate the help!

David

Tews · 25 Sep 2010

All of your .dmp files point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. Enable driver verifier using the following procedures ...

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800156f4b0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------

Please update this driver...

Code:

gdrv.sys     Thu Mar 12 23:22:29 2009 (49B9D175) ... gdrv.sys  GIGABYTE Tools

yuen · 25 Sep 2010

Hi Tews,

Thanks for the prompt reply. I have followed your steps and after my first reboot, my computer crashed to the blue screen. The process repeated and the computer crashed 3 more times before I was finally able to load onto the OS desktop.

After loading, I tried to access GIGABYTE Tools to update the driver, however, clicking on the file immediately blue screened my computer, causing it to return to a continuous bluescreen-restart process.

Is there some information that I should have gotten out of the Driver Verifier process? No windows or message opened after I was able to load into the OS desktop.

Thanks again for the help!

David

yuen · 26 Sep 2010

Sorry for another post, but I just discovered a new problem with the computer. I can no longer connect to the internet (PC is connected directly to my router), with the following error: "The Diagnostic Policy Service is not running". I've tried the "Try these repairs as an administrator" option but with no prevail. Just wanted to share this and see if it might be connected to the blue-screening problem.

Thanks,
David

Tews · 26 Sep 2010

Please upload your new .dmp files...

yuen · 26 Sep 2010

Sorry about that! Theyre attached now :)

Thanks,
David

Tews · 26 Sep 2010

Yuen... These are the old .dmp files ... 9-21-10 ... please delete them from the c:/windows/minidump folder, and upload any new ones that are generated...

yuen · 26 Sep 2010

Hey Tews, sorry about that, I assumed that the new dmp files would be generated into the previous folder. Unfortunately, after I deleted the previous dmp files from the minidump folder and ran the BSOD Dump and System File Collection exe file again, this time I didnt get an output folder in my documents (I deleted the previuos folder with the dmp files from 9-21-10).

yuen · 26 Sep 2010

I tried a few more times and finally got an output folder with the new dmp files. It's attached now. Sorry about that!

Tews · 26 Sep 2010

Make sure that driver verifier is still enabled, then just upload the new files as they are generated...