I'm stumped, I've had the problems ever since I installed Windows.
I had VLC running in the background while performing the diagnostics to prevent crashes (for some reason, it seems to work). I hope it won't muddle anything up, if it does I can rerun it with my fingers crossed or another program open.
If you need any more information, please let me know.
> > These crashes were caused by memory exception and sptd.sys.
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
1. Memtest.
RAM - Test with Memtest86+*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
2. Driver verifier
Driver Verifier - Enable and DisableUsing 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.
I'd suggest that you first backup your data 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).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
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).
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.
Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
THEN ...
> > 3. Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ
when you're done you can use this Freeware:
MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place
Using MagicISO to create ISO image files
I ran 8 passes of memtest with no errors. I've disabled sptd.sys and I've tried to let verifier run - but I can only read the dump files in BlueScreenView, which now seems to include hal.dll in "Caused by driver" apart from the perennial win32k.sys, ntsf.sys & ntoskrnl.exe
I've attached the new minidumps, and my fingers are very much crossed. Again, if more information is required, please let me know.
Just a brief mono-black command window which disappears instantly. I have since disabled verifier because I thought plenty of crashes had occurred while it ran. I probably fudged something up.
I'll try to get driver verifier to run again and will report back when I get a decent number of new minidumps (hopefully verified).
Thanks
Hmm. I now got a blue screen after with (hopefully) verifier running. If it helps in any way, it seems that the minor version has changed to 7601 rather than 7600 after I disabled sptd.sys (?).
I've uploaded the latest dump file as it does not contain any information I can readily read in BlueScreenView. I won't disable verifier this time.
Verifier /query still opens a command window which quickly shuts down. This time around, rather than instantly, I can see some text parsing rapidly before it closes.
Addendum: I doubt it is relevant, but a few times it has frozen completely rather than going to a blue screen (i.e., no dumps) - this has happened either after I disabled spst.sys or after I disabled auto-restart in case of crashes. I have no idea whether this is diagnostic of anything, but I figure I'd rather give too much information.
I've crashed a few times with verifier and got the verifier /query to work (apparently, cmd isn't normally using admin priveledges). I've included a transcript of the results, and all dump files from while verifier has been running.
I know Danish looks terrible, especially when it can't reproduce our trusty æ's
I didn't think it would be a problem since the format looked simple, I've translated it now.
Is there any diagnostics I can perform? Or should I just let driver verifier continue until it stumbles upon something useful?
Quote