Yet another BSOD thread

[Xab]

My current machine is running Windows 7 Pro x64. It's a downloaded version from the student $30 deal from a while back.

It was originally a Dell XPS710 but I have since upgraded its memory, video cards, and hard drives, and it originally had Vista x86. As such, I did a custom install to Windows 7.

As for the age of the system, it is roughly 3 years. The parts I upgraded are about a year old.

I have only installed Windows 7 once on this machine, and it was installed right when Windows 7 came out.

Thanks for all the help, who ever is on the other side there!

 

[zigzag3143]

My current machine is running Windows 7 Pro x64. It's a downloaded version from the student $30 deal from a while back.

It was originally a Dell XPS710 but I have since upgraded its memory, video cards, and hard drives, and it originally had Vista x86. As such, I did a custom install to Windows 7.

As for the age of the system, it is roughly 3 years. The parts I upgraded are about a year old.

I have only installed Windows 7 once on this machine, and it was installed right when Windows 7 came out.

Thanks for all the help, who ever is on the other side there!

You have easily 10 causes for these crashes. Most of them point to Hardware and steam.

Since they cover such a long time frame and have so many causes we should concentrate on the most recent ones as they are probably the most likely to still exist

I would do the following
The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do>

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-Download a 3rd party app called memtestx86, burn it so cd, and run memtest for 5-6 passes.

3-Event viewer
There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
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[/quote


Ken


Old drivers that need updating

secdrv.SYS        fffff880`0676f000    fffff880`0677a000    0x0000b000    0x4508052e    9/13/2006 09:18:38                        
RecFltr.sys        fffff880`053a4000    fffff880`053af180    0x0000b180    0x45aecbfd    1/17/2007 21:23:09                        
VSTCNXT6.SYS        fffff880`04e0f000    fffff880`04eda000    0x000cb000    0x48f69046    10/15/2008 20:52:22                        
VSTBS26.SYS        fffff880`04200000    fffff880`04270000    0x00070000    0x48f690ae    10/15/2008 20:54:06                        
VSTDPV6.SYS        fffff880`04c4c000    fffff880`04dc0000    0x00174000    0x48f69189    10/15/2008 20:57:45                        
adfs.SYS        fffff880`05e9e000    fffff880`05eb6000    0x00018000    0x490f2b4e    11/3/2008 12:48:14                        
b57nd60a.sys        fffff880`04800000    fffff880`04848000    0x00048000    0x49f4422f    4/26/2009 07:14:55                        
spldr.sys        fffff880`017f0000    fffff880`017f8000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`04870000    fffff880`0487d000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`0113d000    fffff880`01148000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
nvstor.sys        fffff880`010b0000    fffff880`010db000    0x0002b000    0x4a13a711    5/20/2009 02:45:37                        
dump_nvstor.sys        fffff880`05349000    fffff880`05374000    0x0002b000    0x4a13a711    5/20/2009 02:45:37

 

[Xab]

1) I let sfc /scannow run, but it did not find any integrity violations.

2) I let memtest do 6 passes. No errors were found.

3) Event logging - Application Log: Going back a little ways, I seem to have errors from only two sources: the spoolsv executable and this related to Windows Update: "Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file."

I'm not sure what this means; my copy of Windows is confirmed as genuine. As for the print spooler, I've had a printer connected to my machine, but it's printer drivers aren't compatible with Win 7. I've only been using it as a memory card reader and scanner. I'll unplug it anyways and see how that affects it.

For spoolsv.exe, the system gives this message:


spoolsv.exe


6.1.7600.16385


4a5bd3d1


unknown


0.0.0.0


00000000


c0000005


0000000000000000


10f8


01cb3e20730eabc0


C:\Windows\System32\spoolsv.exe


unknown


fa7ddf90-aa13-11df-a9bf-0019b9054511

Security Log: No errors.

Setup Log: No errors.

System Log: Again, there are MANY errors referencing spoolsv.exe. Other than my ISP jumping around DNS servers and entries related to BSODs, the log is entirely filled with errors regarding spoolsv going back at least 3 months.

The entries for this all look like:

The Print Spooler service terminated unexpectedly. It has done this 3 time(s). The event ID is either 7034 or 7031.

There is nothing at all under the main "Applications and Services Log."

4) There are no malfunctioning drivers in my device manager. They all show as normal.

5) I will start the verifier and report when something comes of it.

Thanks a ton for your help, this is great!