Please let me know why my system makes bsod frequently.
I could not enter into sleep mode, that is when push wake-up button system shows bsod.
These sleep problem and bsod may have one reason.
I attahed miidump file.
Any help would be appreciated.
The crash occurred in the Memory Manager's internal routines. It was trying to adjust the working set for a process (the amount of its VM that's resident in RAM) when it encountered bad data. The cause of the corruption is not immediately obvious from the crash pattern. It likely happened some time before the actual crash, by which point the evidence was gone.
If this happens exclusively after power state transitions, try updating your BIOS if you haven't done so recently. You also seem to have everything including the kitchen sink when it comes to drivers, and you may wish to go through this list to update those which can be updated, and remove (uninstall) those you don't really need:
start end module name
fffff880`00deb000 fffff880`00df6d00 PxHlpa64 Thu Mar 13 12:58:17 2008 (47D88A39)
fffff880`01000000 fffff880`0101d000 jraid Thu Jun 25 18:10:04 2009 (4A4330DC)
fffff880`0104c000 fffff880`01057000 amdxata Wed May 20 03:56:59 2009 (4A12F2EB)
fffff880`0145e000 fffff880`01489140 VBoxDrv Thu Sep 10 03:56:40 2009 (4AA7EC58)
fffff880`01a07000 fffff880`01aec000 timntr Fri Jul 31 01:05:53 2009 (4A71B6D1)
fffff880`02c23000 fffff880`02c3b000 adfs Tue Nov 04 03:48:14 2008 (490F2B4E)
fffff880`0422a000 fffff880`04256000 MpFilter Thu Jun 11 12:33:21 2009 (4A306CF1)
fffff880`04402000 fffff880`044bc000 Ext2Fsd Sun Jul 26 18:21:47 2009 (4A6C121B)
fffff880`045ea000 fffff880`045f5500 VBoxUSBMon Thu Sep 10 03:56:41 2009 (4AA7EC59)
fffff880`04600000 fffff880`04663000 yk62x64 Tue Feb 24 02:02:27 2009 (49A2BA83)
fffff880`046dd000 fffff880`04bff000 atikmdag Fri Apr 24 20:51:57 2009 (49F199CD)
fffff880`04de5000 fffff880`04df0000 snxpcamd Thu Dec 20 13:56:29 2007 (4769D9DD)
fffff880`05043000 fffff880`0507e000 ctoss2k Tue Jun 23 14:46:15 2009 (4A405E17)
fffff880`0507e000 fffff880`05086000 ctprxy2k Tue Jun 23 14:46:48 2009 (4A405E38)
fffff880`05098000 fffff880`050a0000 ASACPI Mon Mar 28 13:30:36 2005 (42476C4C)
fffff880`050ad000 fffff880`0517ed80 ctaud2k Tue Jun 23 14:46:46 2009 (4A405E36)
fffff880`0565a000 fffff880`05680000 snxppamd Thu Dec 20 13:56:42 2007 (4769D9EA)
fffff880`05680000 fffff880`056c2000 hap16v2k Tue Jun 23 14:46:20 2009 (4A405E1C)
fffff880`0574a000 fffff880`05768640 VBoxNetAdp Thu Sep 10 03:56:43 2009 (4AA7EC5B)
fffff880`05792000 fffff880`057b4200 VBoxNetFlt Thu Sep 10 03:56:40 2009 (4AA7EC58)
fffff880`06425000 fffff880`065de000 ha10kx2k Tue Jun 23 14:46:17 2009 (4A405E19)
fffff880`06615000 fffff880`06667000 emupia2k Tue Jun 23 14:46:08 2009 (4A405E10)
fffff880`06667000 fffff880`066b1000 ctsfm2k Tue Jun 23 14:46:10 2009 (4A405E12)
fffff880`066b1000 fffff880`0675f000 ctac32k Tue Jun 23 14:49:35 2009 (4A405EDF)
fffff880`06774000 fffff880`0679f000 COMMONFX Tue Jun 23 14:47:02 2009 (4A405E46)
fffff880`06800000 fffff880`068ab000 CTSBLFX Tue Jun 23 14:47:08 2009 (4A405E4C)
fffff880`068f6000 fffff880`069a6000 CTAUDFX Tue Jun 23 14:47:04 2009 (4A405E48)
fffff880`069e2000 fffff880`06a00000 ISODrv64 Tue Feb 10 20:22:18 2009 (4991474A)
fffff880`06e22000 fffff880`06e99000 ADIHdAud Fri Jan 04 01:57:39 2008 (477CF7E3)
fffff880`06e99000 fffff880`06f0f580 MarvinAVS64 Wed May 09 17:33:33 2007 (4641794D)
fffff880`06fd3000 fffff880`06ffee80 skyhd6mc Wed Sep 10 18:26:39 2008 (48C784BF)
fffff880`07128000 fffff880`0716ee80 atinavt2 Wed Apr 01 12:22:34 2009 (49D2C1DA)
fffff880`071b3000 fffff880`071ca000 tifsfilt Wed Aug 29 22:37:29 2007 (46D56889)
fffff880`07924000 fffff880`07936000 WMDrive Mon May 04 03:52:17 2009 (49FDD9D1)
fffff880`0798a000 fffff880`0799a000 MpNWMon Thu Jun 11 12:33:23 2009 (4A306CF3)
Last edited by H2SO4; 03 Oct 2009 at 05:53. Reason: Driver names now in red.
H2SO4/ Thank you for your kind reply and advise.
But your advise is so difficult for me, so I'll study and post following.
Sorry. I am not good at keeping things simple.
What I suggest you do is to check the (now in red) names of the drivers in that list I posted (they're from your machine), update each of them if updates are available, and uninstall the ones you don't absolutely need. A web search for each driver name is a good place to start. Your aim should be to find out exactly what each driver does, how it came to be on your machine (is it video, audio,...?), and whether there are any newer versions of that driver.
By doing that, you may fix your BSOD problem.
H2SO4/
I appreciate for your detailed explanation of your advise.
I'll try to fix my problem according to your advise, and post here the result.
Quote