Several BSoDs and PC restarts

[mimiron]

Hey guys my pc is crashing constantly and I am not even able to launch it properly. I think it is hardware related. Anyways here is the dump. Thanks in advance.

I have Windows 7 64bit installed at the moment.
When I boot my pc I am offered a launch up repair,resulting in a BSoD.
When I want to choose the "Start Windows Normally" option, W7 either freezes on the boot screen with nothing doing or on the "welcome" screen it is like 10seconds, then freeze, and thats about everything.

Atm I am on Safe Mode w/ networking waiting for the next freeze.
I appreciate every help guys. Thank you for your responses.

Today I have had like 5 BSoDs. one saying something about watchdog.sys, the other was nvlddmkm.sys or something similar, then there was a system exception as well.

A week ago, this 'freezing & restarting problem' made its appearance. I firstly formated my drive and installed 64bit XP and then again Windows 7. Although I installed XP, the problem persisted.

None of my hardware is overclocked.

 

[mimiron]

Adding another crashdump from 2mins ago :/

 

[usasma]

3 memory dump files, all dated from today.
3 different STOP errors, 3 different causes

Along with that, the reinstallation of several OS's - and the problems still occurring - suggests that this is a hardware problem (as you suspected).

So, please try these free, bootable hardware diagnostics to start with:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

The dump files suggest software causes (despite the hardware evidence), so let's run Driver Verifier just to be sure. Please run it 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"
- 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

If you have another video card handy, you may want to try swapping if for the current card (but don't buy a new card, this is just a suspicion at this point).
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 13 09:35:33.027 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:33.978
BugCheck FC, {fffff88002aeff88, 800000012854e121, fffff88003a20940, 2}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitRenderCommand+8ad )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 13 09:13:24.310 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:44.666
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88010072d47, fffff880031a7e58, fffff880031a76b0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c6d47 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 13 03:43:22.435 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.776
BugCheck DA, {504, fffff6fc40054578, 1, a8af}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b47b )
BUGCHECK_STR:  0xDA
PROCESS_NAME:  System

 

[usasma]

The last STOP error was a STOP 0xD1 that blamed mouclass.sys (a Windows file)
So that makes 4 different STOP errors with 4 different causes - this tends to reinforce the idea that it's a hardware problem.

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 13 10:03:15.400 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:42.994
BugCheck D1, {1, 2, 8, 1}
Probably caused by : mouclass.sys ( mouclass!MouseClassRead+f1 )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xD1

 

[mimiron]

Firstly I want to thank you for your response.

So as you advised, I have run a HDD check with HD Tune.

so that is not causing problems I guess.

Well as for the driver check... I am afraid to do that, because I do not have another computer at my disposal.

Isn't there another way to check which driver/harware may cause problem within safe-mode ?

Thanks.

 

[usasma]

In that case, I'd backup all your stuff and be prepared to reinstall Windows if everything goes wrong and you can't get in contact with us.

Then run the Driver Verifier. Most people are able to get into normal or Safe Mode - and it's only a couple that can't. I haven't had to coach anyone through mounting the registry since I first gave out these instructions a couple of years ago (I do recall one person who formatted their computer and reinstalled Windows because they didn't want to go through the hassle).