Another BSOD!

[George1]

I'm glad to find this forum, maybe someone can help.
Background:
I built a new computer about 3 weeks ago, then loaded all software but was not connected to the internet at the time. There were no blue screens at this time, about 2 weeks.
Then connected to the internet and still no blue screens for a few days.
I did quite a bit of personal configuring at this time only using windows 7 menus.
About 10 days ago the blue screens started.
If the computer is off all night they will appear about 15 minutes after starting the computer, I'll restart again and all will be fine for the rest of the day.
It happens when checking various websites, no websites in particular.

I think I found the file but wanted to be sure, it's called ntoskrnl.exe.
I have only 2 dmp files because I got a program called ccleaner but didn't know it erases dmp files also.

This is a strange file as I have windows 7, not NT. I want to delete this file but I'm not sure so I am here.

I ran memory tests at startup with no problem, and also scannow /sfc with no problem.

I've attached a zip file with the 2 dumps.

A good clue may be that it happens after about 15 minutes after starting up at various times in the day but after long shutdowns.

 

[usasma]

STOP 0x19: BSOD Index
STOP 0x109: BSOD Index

Both errors tend to have memory in common. Have you run this memory test: Memory Diagnostics (read the details at the link) If not, please do so (I don't trust the inbuilt Windows memory diagnostic on every occasion) - and please post back with the results (# passes and roughly the amount of time it took)

Then, I'd suggest running Driver Verifier according to these directions:

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

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 10:54:19.243 2010 (UTC - 4:00)
System Uptime: 0 days 0:19:55.759
BugCheck 109, {a3a039d8959d9b47, 0, af147ab91a0f4212, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 11 12:41:20.074 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:33.589
BugCheck 19, {22, fffff8a002876000, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[George1]

Thanks for replying.
I have another problem before I can start on the tests.
My computer froze so I hit the restart, the computer shut down but as soon as it started it shut down again.
It would start for just about 1 second, I could hear the fans on high which they never do that and then shut down again, cycling.
I could see the motherboard lighting up for maybe 1 second also before shutting down.
Well, finally I tried to start it again and there was nothing, no motherboard lights, no fans. Just dead.

Any ideas would be appreciated, thanks.

 

[usasma]

Not much in the way of ideas other than replacing parts.
Try the steps here (as far as you can): Hardware Troubleshooting Via System Stripdown