A lot of Blue Screen with different error messages.

[rajishunk]

Hi all,
I am suffering from a lot of frequent Blue Screens of Deaths.
I have uploaded a recent mini-dump file in a zip archive. As I use Ccleaner a lot, it keeps removing the previous mini-dump files.
Also the screenshots of all tabs in CPU-Z have been attached to the post.
Please help me with this issue, or guide me what can I do so to prevent this from happening.

P.S. I am new here, so I am sorry if I have violated some of the forums rules or regulations. Keep me posted.

At my best.

Thanks & Regards.

 

[zigzag3143]

Hi all,
I am suffering from a lot of frequent Blue Screens of Deaths.
I have uploaded a recent mini-dump file in a zip archive. As I use Ccleaner a lot, it keeps removing the previous mini-dump files.
Also the screenshots of all tabs in CPU-Z have been attached to the post.
Please help me with this issue, or guide me what can I do so to prevent this from happening.

P.S. I am new here, so I am sorry if I have violated some of the forums rules or regulations. Keep me posted.

At my best.

Thanks & Regards.

These crashes were caused by memory corruption (probably a driver). 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.

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

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[rajishunk]

Memtest86+ done with no errors, had a crash & a system restore, now running Verifier!

I ran the Memtest 86+ test for all 100 passes, took a little time, but it encountered no errors!
Then I configured the verifier as mentioned in the "sevenforums" link & as I rebooted it for the verifier to begin, the windows crashed & took me to the process of System Recovery & recovered to a previous phase, & I can see that it uninstalled the Counter Strike 1.6 from my PC.

I have also attached the .zip dump file. Hope it helps. Will run the verifier for 24 hours, and will keep you posted!

Regards & Thanks.
-------------------------------------------------------------------------------------------------------------------------------

These crashes were caused by memory corruption (probably a driver). 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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[rajishunk]

Verifier won't begin!

After successfully completing all the passes of Memtest86+, I configured the Verifier for all non-Microsoft Corporation drivers, but as I restarted, the windows crashed & put me through a system restore. After the system restore I again configured the Verifier & rebooted. Again the windows crashed & attempted for a System Restore again, but failed to complete this time.

So I am not able to run the Verifier. Let me know what I can do now!

Thanks & Regards.

These crashes were caused by memory corruption (probably a driver). 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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[rajishunk]

BlueScreenView screenshot of the latest crash when Verifier was tried to be started!

A screenshot of the latest Minidump of the crash when I tried to reboot after configuring the Verifier for it to detect the guilty driver.

These crashes were caused by memory corruption (probably a driver). 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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Elmer BeFuddled]

Just For Info!

Open CCleaner, click the Clean button, select the Windows tab. Under the sub-heading System make sure Memory dumps is un-ticked. You should now find your dump files are available when you need them.

 

[rajishunk]

Thanks for the tip!
Although there has not been a blue screen appearance since the last system restore this morning after the Verifier crashed & didn't work, but may be the frequency just lowered down. Will let you know. Please tell me if a cure exists, even if it is a hit-or-trial method, works for me! As, Verifier does not help!

Thanks & Regards.

Just For Info!

Open CCleaner, click the Clean button, select the Windows tab. Under the sub-heading System make sure Memory dumps is un-ticked. You should now find your dump files are available when you need them.

 

[rajishunk]

Another Blue Screen - DRIVER_IRQL_NOT_LESS_OR_EQUAL

Another Blue Screen of Death.

Minidump file as zip archive included!

Solution Needed!

 

[zigzag3143]

Another Blue Screen of Death.

Minidump file as zip archive included!

Solution Needed!

This one was related to your igdkmd32.sys (Intel video driver). Yours dated 5/2009. I would re-install newest version available.

I would do what Elmer Be Fuddled suggested first as I am just trying to save you (and him) some time by posting this


Co-incident factors
Old drivers

mdmxsdk.sys    6/19/2006 4:26:59 PM            0x9aab3000    0x9aab6180    0x00003180    0x449716a3                    
xaudio.sys    8/4/2006 7:39:09 PM            0x9abf0000    0x9abf8000    0x00008000    0x44d3e8ad                    
HSX_CNXT.sys    11/2/2006 9:42:05 PM            0x96e2c000    0x96ee0000    0x000b4000    0x454aac7d                    
HSXHWAZL.sys    11/2/2006 9:42:16 PM            0x942ad000    0x942ea000    0x0003d000    0x454aac88                    
HSX_DPV.sys    11/2/2006 9:43:26 PM            0x942ea000    0x943ed000    0x00103000    0x454aacce                    
rimsptsk.sys    1/23/2007 2:40:19 AM            0x92c86000    0x92c9a000    0x00014000    0x45b5bbe3                    
rimmptsk.sys    2/24/2007 12:42:21 AM            0x92c77000    0x92c86000    0x0000f000    0x45dfd03d                    
rixdptsk.sys    3/21/2007 8:02:02 AM            0x92c9a000    0x92ceb000    0x00051000    0x46012cca                    
NETw4v32.sys    8/8/2007 10:26:03 AM            0x92a09000    0x92c32000    0x00229000    0x46b9e08b                    
stwrt.sys    2/15/2008 5:36:49 PM            0x96f85000    0x96fda000    0x00055000    0x47b61401                    
ElbyCDIO.sys    2/17/2009 12:11:28 PM            0x8bc27000    0x8bc2b200    0x00004200    0x499aefc0                    
yk62x86.sys    2/23/2009 9:44:18 AM            0x90d8b000    0x90ddb000    0x00050000    0x49a2b642                    
igdkmd32.sys    5/6/2009 1:13:40 PM        igdkmd32.sys+f374    0x9141d000    0x9191a000    0x004fd000    0x4a01d354                    
VClone.sys    5/22/2009 6:08:32 PM            0x919eb000    0x919f6000    0x0000b000    0x4a173070

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



Other factors


I do notice Kaspersky which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO EEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

http://www.microsoft.com/security_essentials/

 

[rajishunk]

Thank you zigzag!

Thanks a lot for the update! I will look out for the updated drivers & will keep you posted with the progress!

Thanks & Regards.

This one was related to your igdkmd32.sys (Intel video driver). Yours dated 5/2009. I would re-install newest version available.

I would do what Elmer Be Fuddled suggested first as I am just trying to save you (and him) some time by posting this


Co-incident factors
Old drivers

mdmxsdk.sys    6/19/2006 4:26:59 PM            0x9aab3000    0x9aab6180    0x00003180    0x449716a3                    
xaudio.sys    8/4/2006 7:39:09 PM            0x9abf0000    0x9abf8000    0x00008000    0x44d3e8ad                    
HSX_CNXT.sys    11/2/2006 9:42:05 PM            0x96e2c000    0x96ee0000    0x000b4000    0x454aac7d                    
HSXHWAZL.sys    11/2/2006 9:42:16 PM            0x942ad000    0x942ea000    0x0003d000    0x454aac88                    
HSX_DPV.sys    11/2/2006 9:43:26 PM            0x942ea000    0x943ed000    0x00103000    0x454aacce                    
rimsptsk.sys    1/23/2007 2:40:19 AM            0x92c86000    0x92c9a000    0x00014000    0x45b5bbe3                    
rimmptsk.sys    2/24/2007 12:42:21 AM            0x92c77000    0x92c86000    0x0000f000    0x45dfd03d                    
rixdptsk.sys    3/21/2007 8:02:02 AM            0x92c9a000    0x92ceb000    0x00051000    0x46012cca                    
NETw4v32.sys    8/8/2007 10:26:03 AM            0x92a09000    0x92c32000    0x00229000    0x46b9e08b                    
stwrt.sys    2/15/2008 5:36:49 PM            0x96f85000    0x96fda000    0x00055000    0x47b61401                    
ElbyCDIO.sys    2/17/2009 12:11:28 PM            0x8bc27000    0x8bc2b200    0x00004200    0x499aefc0                    
yk62x86.sys    2/23/2009 9:44:18 AM            0x90d8b000    0x90ddb000    0x00050000    0x49a2b642                    
igdkmd32.sys    5/6/2009 1:13:40 PM        igdkmd32.sys+f374    0x9141d000    0x9191a000    0x004fd000    0x4a01d354                    
VClone.sys    5/22/2009 6:08:32 PM            0x919eb000    0x919f6000    0x0000b000    0x4a173070

How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



Other factors


I do notice Kaspersky which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO EEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

http://www.microsoft.com/security_essentials/

 

[rajishunk]

Another Blue Screen!

Another blue screen while watching a video in VLC player.

I feel devastated!

Kindly help!

Minidump file in zip archive included!

Thanks & Regards.

This one was related to your igdkmd32.sys (Intel video driver). Yours dated 5/2009. I would re-install newest version available.

I would do what Elmer Be Fuddled suggested first as I am just trying to save you (and him) some time by posting this


Co-incident factors
Old drivers

mdmxsdk.sys    6/19/2006 4:26:59 PM            0x9aab3000    0x9aab6180    0x00003180    0x449716a3                    
xaudio.sys    8/4/2006 7:39:09 PM            0x9abf0000    0x9abf8000    0x00008000    0x44d3e8ad                    
HSX_CNXT.sys    11/2/2006 9:42:05 PM            0x96e2c000    0x96ee0000    0x000b4000    0x454aac7d                    
HSXHWAZL.sys    11/2/2006 9:42:16 PM            0x942ad000    0x942ea000    0x0003d000    0x454aac88                    
HSX_DPV.sys    11/2/2006 9:43:26 PM            0x942ea000    0x943ed000    0x00103000    0x454aacce                    
rimsptsk.sys    1/23/2007 2:40:19 AM            0x92c86000    0x92c9a000    0x00014000    0x45b5bbe3                    
rimmptsk.sys    2/24/2007 12:42:21 AM            0x92c77000    0x92c86000    0x0000f000    0x45dfd03d                    
rixdptsk.sys    3/21/2007 8:02:02 AM            0x92c9a000    0x92ceb000    0x00051000    0x46012cca                    
NETw4v32.sys    8/8/2007 10:26:03 AM            0x92a09000    0x92c32000    0x00229000    0x46b9e08b                    
stwrt.sys    2/15/2008 5:36:49 PM            0x96f85000    0x96fda000    0x00055000    0x47b61401                    
ElbyCDIO.sys    2/17/2009 12:11:28 PM            0x8bc27000    0x8bc2b200    0x00004200    0x499aefc0                    
yk62x86.sys    2/23/2009 9:44:18 AM            0x90d8b000    0x90ddb000    0x00050000    0x49a2b642                    
igdkmd32.sys    5/6/2009 1:13:40 PM        igdkmd32.sys+f374    0x9141d000    0x9191a000    0x004fd000    0x4a01d354                    
VClone.sys    5/22/2009 6:08:32 PM            0x919eb000    0x919f6000    0x0000b000    0x4a173070

How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



Other factors


I do notice Kaspersky which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO EEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

http://www.microsoft.com/security_essentials/

 

[zigzag3143]

Another blue screen while watching a video in VLC player.

I feel devastated!

Kindly help!

Minidump file in zip archive included!

Thanks & Regards.

Related to klif.sys Klif Mini-Filter fre_wnet_x86 from Kaspersky Lab. As I suggested I would remove and replace it.