Windows 7 BSOD on Dell XPS 730 and windows 7

[dprill]

Hi I have been trying for a couple of days now to figure out the source of some BSODs that have occurred over the last week or so. It started when I was playing Dungeon Siege III, so I attributed it to the game being new, and just tolerated them. Now I ham getting them when i try and do some HD rendering with Sony Vegas Movie Studio. It doesn't happen all the time, but randomly on different clips and different parts of clips.

Any help would be appreciated. Below are the CPU-Z screen shots, and the minidumps from my system. There doesn't seem to be any driver issue that I can see, blue screen view points to the ntoskrnl.exe, which is very generic. Not having any other symptoms of an ntoskrnl.exe issue..

Thanks, Darin

View attachment dumps.zip

 

[zigzag3143]

Hi I have been trying for a couple of days now to figure out the source of some BSODs that have occurred over the last week or so. It started when I was playing Dungeon Siege III, so I attributed it to the game being new, and just tolerated them. Now I ham getting them when i try and do some HD rendering with Sony Vegas Movie Studio. It doesn't happen all the time, but randomly on different clips and different parts of clips.

Any help would be appreciated. Below are the CPU-Z screen shots, and the minidumps from my system. There doesn't seem to be any driver issue that I can see, blue screen view points to the ntoskrnl.exe, which is very generic. Not having any other symptoms of an ntoskrnl.exe issue..

Thanks, Darin

View attachment 15170View attachment 15169View attachment 15171View attachment 15172View attachment 15173

Memory corruption caused by a driver (vegasmoviestudio?) Please run these two tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

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

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.