Windows 7 Persistent PFN List Corruption Causing BSOD: Need Help Analyzing Dump File

[venax]

Keep having this damn BSOD!!!!!! already checked my ram with memtest all night and 0 errors !
i leave you my dump hoping that you can help me

 

[venax]

could it be a ram problem even thought i ran memtest for 8 hours? maybe rams are trolling me or something :v ! i mean first i removed msi afterburner when you said " The only sure thing that I see here is MSI Afterburner" but problem still here now i don t want to remove all the drivers randomly and then find out that wasn t the problem . Oh and another problem i noticed , now i currently have 8.68 gb free primary disk , if i rebot my system , the free space drops to 1.50 gb or something is this normal ? maybe the ssd is the problem .

 

[usasma]

All I can do is report the errors that I see. I see the error with the virtual audio cable in the latest memory dump. If you'd like to test your memory, please run the memory diagnostics: Link Removed - and to stress the memory run Prime95: Link Removed

 

[usasma]

BTW - if this is a hardware problem, then we'll need several more BSOD's to see if it is. This is done in combination with these hardware diagnostics: http;//www.carrona.org/hwdiag.html
Also, the only certain test to rule out an SSD is to install a known-good platter based hard drive and see if that stops the errors.

 

[venax]

ok so i removed VIRTUAL audio cable but as i assumed bsod still here
and just to be sure that ram are not failing , i ran memtest, one stick at the time for 7 hours 0 errors ..

i guess something to do with USB maybe

 

[usasma]

OK, these are Driver Verifier enabled memory dumps and they blame Windows drivers. As such this is either a hardware problem (most likely) or a Windows problem (less likely, but still a possibility).

Check in Device Manager for any items listed under "Human Interface Devices" as this is what the Windows driver points to (but this can also be other attached devices that you use to input data/information/keystrokes/mouse movements/etc). Remove them one at a time to see if you can rule them out.

Run all of these hardware diagnostics: Link Removed
Then perform this procedure to rule out as much hardware as is possible: Link Removed

If everything there passes, then try this for a clean install of Windows: Link Removed

If that doesn't fix it, then the problem lies in the pieces of hardware that weren't tested (PSU, mobo, etc)

Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Fri Mar  1 12:04:40.133 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030113-20326-02.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 0:00:45.084[/B]
Probably caused by :[B]HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )[/B]
BugCheck [B]C9, {23b, fffff88001682710, fffff98006fdee50, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88001682710, The address in the driver's code where the error was detected.
Arg3: fffff98006fdee50, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR:  0xc9_23b
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc9_23b_HIDCLASS!HidpMajorHandler+0[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar  1 11:59:43.758 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030113-20326-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 0:00:45.819[/B]
Probably caused by :[B]HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )[/B]
BugCheck [B]C9, {23b, fffff88001648710, fffff98013498dc0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88001648710, The address in the driver's code where the error was detected.
Arg3: fffff98013498dc0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR:  0xc9_23b
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc9_23b_HIDCLASS!HidpMajorHandler+0[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Fri Mar  1 12:04:40.133 2013 (UTC - 5:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
ISODrv64.sys       Thu Jan 28 22:39:02 2010 (4B625856)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmVirHid.sys       Tue Apr 27 16:08:53 2010 (4BD74455)
WmXlCore.sys       Tue Apr 27 16:09:26 2010 (4BD74476)
WmBEnum.sys        Tue Apr 27 16:10:19 2010 (4BD744AB)
Rt64win7.sys       Tue Aug 23 09:55:41 2011 (4E53B15D)
cpuz135_x64.sys    Wed Sep 21 04:23:41 2011 (4E799F0D)
MFWCtwl.sys        Fri Dec 23 08:13:58 2011 (4EF47E96)
GEARAspiWDM.sys    Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys        Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys       Tue Jul  3 11:25:04 2012 (4FF30ED0)
EtronXHCI.sys      Fri Jul 20 03:15:46 2012 (500905A2)
EtronHub3.sys      Fri Jul 20 03:15:52 2012 (500905A8)
nvlddmkm.sys       Fri Nov 30 22:24:02 2012 (50B97852)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
MFWCtwl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[venax]

so i need to remove them one at the time and then run driver verifier everytime ?

update: so i removed everything from HID and the first time i got bsod , then i tryed second time i removed everything again but i also unplugged everything from the back ( mouse keyboard external hdd , audio cable ) and no BSOD :O. So is it about the device or one of the USB port is failing?

 

[usasma]

OK, you know that removing the mouse, keyboard, ext HDD, and Audio cable stops the BSOD.
Now plug them back in (one at a time) to see which one gets the BSOD.
Then try the one that gets the BSOD in the front USB and see if it still BSOD's

 

[venax]

so i removed them one by one , and no bsod , nothing was causing BSOD anymore . So maybe it was because of a bad driver installed, and when i plugged them again they installed correctly...

 

[venax]

Can you check me this last dump ? it s probably msi afterburner but i just want to be sure ? and if it s msi AB again do you know any other program to controll fan speed ? evga precision and riva tuner are using the same rtcore right?

 

[usasma]

All I know of for fan speed is SpeedFan: Download SpeedFan - Access temperature sensor in your computer

The BSOD doesn't blame anything in particular. I'd suggest trying Driver Verifier according to these instructions: Link Removed

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Fri Mar 15 09:02:58.181 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031513-17487-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 0:13:41.024[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ce77 )[/B]
BugCheck [B]4E, {7, 14b9a5, 14cd74, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000014b9a5, page frame number
Arg3: 000000000014cd74, current share count
Arg4: 0000000000000000, 0
BUGCHECK_STR:  0x4E_7
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID: [B]X64_0x4E_7_nt!_??_::FNODOBFM::_string_+1ce77[/B]
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3410[/B]
  BIOS Version                  F10
  BIOS Release Date             02/21/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68X-UD4-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Fri Mar 15 09:02:58.181 2013 (UTC - 4:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
ISODrv64.sys       Thu Jan 28 22:39:02 2010 (4B625856)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmBEnum.sys        Tue Apr 27 16:10:19 2010 (4BD744AB)
Rt64win7.sys       Tue Aug 23 09:55:41 2011 (4E53B15D)
cpuz135_x64.sys    Wed Sep 21 04:23:41 2011 (4E799F0D)
MFWCtwl.sys        Fri Dec 23 08:13:58 2011 (4EF47E96)
GEARAspiWDM.sys    Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys        Mon Jul  2 18:14:58 2012 (4FF21D62)
EtronXHCI.sys      Fri Jul 20 03:15:46 2012 (500905A2)
EtronHub3.sys      Fri Jul 20 03:15:52 2012 (500905A8)
nvhda64v.sys       Wed Dec 19 00:41:41 2012 (50D15395)
nvlddmkm.sys       Thu Feb 28 01:43:51 2013 (512EFCA7)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
MFWCtwl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[venax]

this one was with driver verifier on


oh and another one this time different cache_manager :s

 

[usasma]

Still says low-level problems.
Have you run all of the hardware diagnostics listed here: Link Removed
If so, what were the results of each test?


Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Tue Mar 19 11:37:35.382 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031913-21652-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 1:46:58.256[/B]
Probably caused by :[B]memory_corruption ( nt!MmCheckCachedPageStates+3f0 )[/B]
BugCheck [B]34, {50853, fffff880033384b8, fffff88003337d10, fffff800030aaa10}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000050853
Arg2: fffff880033384b8
Arg3: fffff88003337d10
Arg4: fffff800030aaa10
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0x34_nt!MmCheckCachedPageStates+3f0[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 15:34:18.092 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-24133-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 8:08:28.935[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ce77 )[/B]
BugCheck [B]4E, {7, ab3a5, 164b11, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000000ab3a5, page frame number
Arg3: 0000000000164b11, current share count
Arg4: 0000000000000000, 0
BUGCHECK_STR:  0x4E_7
PROCESS_NAME:  bf3.exe
FAILURE_BUCKET_ID: [B]X64_0x4E_7_nt!_??_::FNODOBFM::_string_+1ce77[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Tue Mar 19 11:37:35.382 2013 (UTC - 4:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
ISODrv64.sys       Thu Jan 28 22:39:02 2010 (4B625856)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys       Tue Apr 27 16:09:26 2010 (4BD74476)
WmBEnum.sys        Tue Apr 27 16:10:19 2010 (4BD744AB)
Rt64win7.sys       Tue Aug 23 09:55:41 2011 (4E53B15D)
cpuz135_x64.sys    Wed Sep 21 04:23:41 2011 (4E799F0D)
MFWCtwl.sys        Fri Dec 23 08:13:58 2011 (4EF47E96)
GEARAspiWDM.sys    Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys        Mon Jul  2 18:14:58 2012 (4FF21D62)
EtronXHCI.sys      Fri Jul 20 03:15:46 2012 (500905A2)
EtronHub3.sys      Fri Jul 20 03:15:52 2012 (500905A8)
usbaapl64.sys      Fri Sep 28 13:32:37 2012 (5065DF35)
nvhda64v.sys       Wed Dec 19 00:41:41 2012 (50D15395)
nvlddmkm.sys       Thu Feb 28 01:43:51 2013 (512EFCA7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 15:34:18.092 2013 (UTC - 4:00)**************************
[B]RTCore64.sys       Tue Sep  6 08:24:50 2011 (4E661112)[/B]
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
MFWCtwl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[venax]

yes i did the hardware tests , and nothing wrong , cpu and gpu temps are right and no errors on cpu with prime95 , i have hitachi hard disk so i downloaded the file and i run it AND again nothinggg ..this is really annoying


Edit: i just did CHKDSK and it found like 5 corrupt things that it fixed o.o . Now i m gonna wait couple of days

 

[usasma]

I'm not a big fan of the Hitachi DFT anymore. Try running the Seatools Long Test to see what it says.

CHKDSK errors are indicative of a problem with the file system on the hard drive - it can be caused by software or hardware.
With the history of problems that you've had, I'd suspect hardware - the only problem is figuring out which piece is at fault.

 

[venax]

after 10 days of no bsod today i got a really strange bsod , while on desktop audio started to do strange sound (the sound that it makes when you have bsod at least for me ) but i was still on desktop and i could do whatever i wanted, so i suspended the session and i turned on the pc again and the blue screen appeared :s

driver verifier was on

 

[usasma]

This one is caused by your Logitech WingMan software/drivers. Please un-install it.

I suspect that the Driver Verifier tests will continue to cause BSOD's. Please check to make sure that it's turned off.

To do this, open up verifier.exe and select "Delete existing settings", click on the "Finish" button and then reboot the system.

There's a possibility that MSI Afterburner could be contributing to these errors, please un-install it also (as I had requested earlier).

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
Intel IDE storage driver
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sat Mar 30 17:22:28.854 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\033013-17846-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17857.amd64fre.win7sp1_gdr.120605-1503
System Uptime:[B]0 days 8:19:25.071[/B]
*** WARNING: Unable to verify timestamp for WmBEnum.sys
*** ERROR: Module load completed but symbols could not be loaded for WmBEnum.sys
Probably caused by :[B]WmBEnum.sys ( WmBEnum+37f8 )[/B]
BugCheck [B]C9, {24c, fffff880053fd7f8, fffff9804382cd30, 103}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
    call to IoMarkIrpPending.
Arg2: fffff880053fd7f8, The address in the driver's code where the error was detected.
Arg3: fffff9804382cd30, IRP address.
Arg4: 0000000000000103, Status code.
BUGCHECK_STR:  0xc9_24c
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc9_24c_WmBEnum+37f8[/B]
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3410[/B]
  BIOS Version                  F10
  BIOS Release Date             02/21/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68X-UD4-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sat Mar 30 17:22:28.854 2013 (UTC - 4:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[B]intelide.sys       Mon Jul 13 19:19:48 2009 (4A5BC114)[/B]
ISODrv64.sys       Thu Jan 28 22:39:02 2010 (4B625856)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmBEnum.sys        Tue Apr 27 16:10:19 2010 (4BD744AB)
Rt64win7.sys       Tue Aug 23 09:55:41 2011 (4E53B15D)
[B]RTCore64.sys       Tue Sep  6 08:24:50 2011 (4E661112)[/B]
cpuz135_x64.sys    Wed Sep 21 04:23:41 2011 (4E799F0D)
MFWCtwl.sys        Fri Dec 23 08:13:58 2011 (4EF47E96)
GEARAspiWDM.sys    Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys        Mon Jul  2 18:14:58 2012 (4FF21D62)
EtronXHCI.sys      Fri Jul 20 03:15:46 2012 (500905A2)
EtronHub3.sys      Fri Jul 20 03:15:52 2012 (500905A8)
nvlddmkm.sys       Thu Mar 14 21:37:00 2013 (51427B3C)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
MFWCtwl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[venax]

but intelide.sys is signed by microsoft , why driver verifier made it crash when i didn t select it ?

 

[usasma]

1) In the memory dump listed above, Driver Verifier made WmBEnum.sys crash - not intelide.sys
2) intelide.sys is listed because it's older than Win7 SP1
3) intelide.sys is not a Microsoft driver, even if it's signed by Microsoft. It is an Intel driver.
4) If you are stating that it doesn't crash when you select all other 3rd party drivers - then it may be pointing to an error. If you followed the directions that I posted you won't be verifying intelide.sys alone - so you won't be able to tell if it's the cause or not.
5) When you get a BSOD, please zip up the contents of the C:\Windows\Minidump folder and upload it with your next post. That way we can analyze each memory dump as it occurs.
6) Have you removed MSI Afterburner?

 

[GeneralHiningII]

Your Audio Drivers look out of date (RT so and so, or Realtek so and so) - namely,
RTCore64 and RT64win7 .sys

Check realtek's website for any available driver updates, found here: Link Removed
Find any devices on your computer that are also on the list, and download and install the corresponding updates.

 

[venax]

1) In the memory dump listed above, Driver Verifier made WmBEnum.sys crash - not intelide.sys
2) intelide.sys is listed because it's older than Win7 SP1
3) intelide.sys is not a Microsoft driver, even if it's signed by Microsoft. It is an Intel driver.
4) If you are stating that it doesn't crash when you select all other 3rd party drivers - then it may be pointing to an error. If you followed the directions that I posted you won't be verifying intelide.sys alone - so you won't be able to tell if it's the cause or not.
5) When you get a BSOD, please zip up the contents of the C:\Windows\Minidump folder and upload it with your next post. That way we can analyze each memory dump as it occurs.
6) Have you removed MSI Afterburner?

well only the 3rd party drivers were selected when i got that bsod .
and yes i unistalled MSI afterburner once and still got BSOD so now i have it back .

I updated my audio driver