BSOD on win7 randomly

#1
Hey there

Getting random BSOD with win7 that i've nv gotten with my old XP SP3.
The only new hardware i added was a very old DDR2 1gb Ram and a samsung hdd which probably isn't the issue.

i've used the SF diag tool v4 to gather all that u guys need to help me :) as well as the rammon html file.
Anw i've ran memtest like twice with no problems.
i'm not an expert so won't won't guess and let you guys perform the magic! :fox:

thanks in advance!
ed
 


Attachments

Last edited:

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#2
Hey there

Getting random BSOD with win7 that i've nv gotten with my old XP SP3.
The only new hardware i added was a very old DDR2 1gb Ram and a samsung hdd which probably isn't the issue.

i've used the SF diag tool v4 to gather all that u guys need to help me :) as well as the rammon html file.
Anw i've ran memtest like twice with no problems.
i'm not an expert so won't won't guess and let you guys perform the magic! :fox:

thanks in advance!
ed
May I recommend you remove that 1GB stick as it won't be doing you any favors and is more than likely the cause of your instabilities. It being PC4200 will also be dragging down the perf of the other faster pc5300 sticks.
 


zigzag3143

Honorable Member
Microsoft MVP
#3
Hey there

Getting random BSOD with win7 that i've nv gotten with my old XP SP3.
The only new hardware i added was a very old DDR2 1gb Ram and a samsung hdd which probably isn't the issue.

i've used the SF diag tool v4 to gather all that u guys need to help me :) as well as the rammon html file.
Anw i've ran memtest like twice with no problems.
i'm not an expert so won't won't guess and let you guys perform the magic! :fox:

thanks in advance!
ed
Hi Ed and welcome

These were caused by the directx driver.


VIDEO_DXGKRNL_FATAL_ERROR (113)

The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.

The following actions might prevent an error like this from happening again:

  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.


I would re-install the newest video driver using this method and update to SP-1. Before you update be sure to run the update readiness tool listed below



When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.




Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [May 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

ISC Diary | Windows 7 / 2008 R2 Service Pack 1 Problems

links courtesy jmh
 


Last edited:
#4
ill try all the stuff u guys mentioned! thanks a lot :)
 


#6
i had another BSOD after only removing the stick of slow RAM. and i've just reinstalled the video driver. hope no more BSODs. the minidump is attached anw.
cheers
 


Attachments

zigzag3143

Honorable Member
Microsoft MVP
#7
i had another BSOD after only removing the stick of slow RAM. and i've just reinstalled the video driver. hope no more BSODs. the minidump is attached anw.
cheers


Memory corruption probably caused by a driver. please run these two tests




1-Memtest.


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

RAM - Test with Memtest86+ - Windows 7 Forums

2-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.
Driver Verifier - Enable and Disable - Windows 7 Forums
 


#8
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.