Tech Support Forum banner
Status
Not open for further replies.
1 - 8 of 8 Posts

·
Registered
Joined
·
6 Posts
Discussion Starter · #1 ·
Vista Home Premium - SP2 - x64
This is the original OS - full retail version
System is a little over a year old
OS installation is about 3 months old
Intel Core 2 Duo E8500 @ 3.16Ghz
ATI Radeon HD 3600 Series
Asus P5QL motherboard
power supply - unsure, believe it is 500 watts

BSOD's like crazy in the last day - my external HDD failed 4/5 days ago, bought a new one and installed it 2 days ago + also signed up for CrashPlan backup software... those are the only 2 changes in the last couple of days...

Now the system is very unstable - sometimes can get to the desktop on normal boot and fuction for 5-10 minutes, other times it BSOD's before I even log in... Same with safemode...

Actually typing this up from safemode - was lucky enough to run the utilities for this post on a normal boot and that was about all I got done before it crashed again...

Thanks in advance for any help...
 

Attachments

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
Hi -

Update this Asus ATK0110 driver ASAP -
Code:
[font=lucida console]ASACPI.sys    Mon Oct 30 22:09:12 [color=red]2006[/color] (4546B048)[/font]
Asus Support --> ASUSTeK Computer Inc.-Support-

Slideshow is for Asus Cool 'n Quiet asio.sys update; scroll down at Asus site and look for ATK0110 -

Asus mobo utility driver updates - Windows Live - jcgriff2 MVP


These drivers need to be updated:
Code:
[font=lucida console]
RtHDMIVX.sys  Sun May 13 22:10:27 2007 (4647C513) - Realtek HD Audio
L1E60x64.sys  Wed Aug 05 01:50:35 2009 (4A791DAB) - Atheros NIC
atikmpag.sys  Tue Jan 04 21:19:38 2011 (4D23D53A) - ATI video
[/font]
http://sysnative.com/0x1/DriverReference.html#RtHDMIVX.sys
http://sysnative.com/0x1/DriverReference.html#atikmpag.sys

I know ATI = Jan 2011; but see if there is an update.

Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller driver - http://partner.atheros.com/Drivers.aspx


Windbg Logs
--> http://sysnative.com/bsod2011/jcgrif..._jcgriff2_.txt
--> http://sysnative.com/bsod2011/jcgrif...riff2_.txt.zip


Regards. . .

jcgriff2


`


BSOD SUMMARY
Code:
[font=lucida console]
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 02:24:02.450 2011 (GMT-4)
System Uptime: 0 days 0:15:15.248
Probably caused by : win32k.sys ( win32k!DEVLOCKOBJ::bDisposeTrgDco+24 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  verclsid.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!DEVLOCKOBJ::bDisposeTrgDco+24
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0018d854 fffffa60`07a7be50 00000000`00000000
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:55:52.503 2011 (GMT-4)
System Uptime: 0 days 0:02:55.157
Probably caused by : win32k.sys ( win32k!HmgNextOwned+7d )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  wow_helper.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_win32k!HmgNextOwned+7d
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff960`001b9cf5
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:41:33.248 2011 (GMT-4)
System Uptime: 0 days 0:04:14.902
BugCheck D3, {fffff960002bb16c, c, 0, fffff80001e88b6e}
Probably caused by : win32k.sys ( win32k!HmgNextOwned+6a )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD3
PROCESS_NAME:  wow_helper.exe
FAILURE_BUCKET_ID:  X64_0xD3_win32k!HmgNextOwned+6a
Bugcheck code 000000D3
Arguments fffff960`002bb16c 00000000`0000000c 00000000`00000000 fffff800`01e88b6e
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:35:21.796 2011 (GMT-4)
System Uptime: 0 days 0:06:14.421
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29117 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  verclsid.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:27:17.426 2011 (GMT-4)
System Uptime: 0 days 0:03:49.223
BugCheck D3, {fffff9600038b16c, c, 0, fffff80001ed3b6e}
Probably caused by : win32k.sys ( win32k!FreeView+9f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD3
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0xD3_win32k!FreeView+9f
Bugcheck code 000000D3
Arguments fffff960`0038b16c 00000000`0000000c 00000000`00000000 fffff800`01ed3b6e
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:21:15.207 2011 (GMT-4)
System Uptime: 0 days 0:02:46.832
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29117 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  verclsid.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000200 00000000`00000008 00000000`00000200
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 01:12:39.911 2011 (GMT-4)
System Uptime: 0 days 0:42:36.569
BugCheck D3, {fffff9600032b16c, c, 0, fffff80001eddb6e}
Probably caused by : win32k.sys ( win32k!HmgNextOwned+66 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD3
PROCESS_NAME:  wow_helper.exe
FAILURE_BUCKET_ID:  X64_0xD3_win32k!HmgNextOwned+66
Bugcheck code 000000D3
Arguments fffff960`0032b16c 00000000`0000000c 00000000`00000000 fffff800`01eddb6e
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 00:28:06.444 2011 (GMT-4)
System Uptime: 0 days 0:01:14.068
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29117 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 00:24:11.636 2011 (GMT-4)
System Uptime: 0 days 0:03:21.261
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29117 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  verclsid.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 00:19:10.579 2011 (GMT-4)
System Uptime: 0 days 0:13:04.243
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+20b )
PROCESS_NAME:  wow_helper.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+20b
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sun Mar 13 23:04:17.691 2011 (GMT-4)
System Uptime: 0 days 0:01:52.487
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+20b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+20b
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`0000000c 00000000`00000000 fffff800`01ec4194
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sun Mar 13 21:06:03.069 2011 (GMT-4)
System Uptime: 0 days 0:01:46.694
BugCheck D3, {fffff9600030b16c, c, 0, fffff80001e90b6e}
Probably caused by : win32k.sys ( win32k!HmgNextOwned+56 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD3
PROCESS_NAME:  MpCmdRun.exe
FAILURE_BUCKET_ID:  X64_0xD3_win32k!HmgNextOwned+56
Bugcheck code 000000D3
Arguments fffff960`0030b16c 00000000`0000000c 00000000`00000000 fffff800`01e90b6e
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]
 

·
Registered
Joined
·
6 Posts
Discussion Starter · #4 ·
First of all - thank you for your help...

I've updated the driver's per your direction... ATI did have a newer release in on FEB 15 as well...

I have faced the same system instability issues though throughout - even when trying to get these drivers installed I had 4/5 BSOD's in the process...

I ran a Memtest last night before I got some sleep - it ran about 6 hours and DID find 3 errors after 8 passes... so there's most certainly an issue there... the BSOD's are so random/sudden and seem like they are all over the place in terms of their description...

Do you have a suggestion on the best way to pinpoint the memory problem? I have 4 sticks of Kingston dual-channel memory installed... Should I run the test individually on each stick? If so, how long do you think should be efficient? If I find an error then I guess I should maybe try to move it to another slot to check the dimm slot?

Thanks again for all your help...
 

·
Registered
Joined
·
6 Posts
Discussion Starter · #5 ·
Update:

So I ran Memtest all day long on the 4 separate modules and came up with 0 errors in each module... ran 4-6 passes... so that is a little confusing considering I had 3 errors on a 6 hour test with all modules installed over last night...

system will not boot normally at all with Verifier started... immediatly reboots on the windows loading bar... even locked up a couple times in safe mode but finally loaded (where I'm at now typing this up)...

i've attached some new minidumps (hopefully verifier enabled, should be)...

thanks again for your time.
 

Attachments

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
Uninstall Acronis - drivers are named in some BSODs.

Test RAM again.

Regards. . .

jcgriff2

`


BSOD SUMMARY
Code:
[font=lucida console]
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 22:18:31.671 2011 (GMT-4)
System Uptime: 0 days 0:00:51.343
Probably caused by : ntkrnlmp.exe ( nt!KiUnwaitThread+2d )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiUnwaitThread+2d
Bugcheck code 0000000A
Arguments 00000cdb`00000008 00000000`0000000c 00000000`00000000 fffff800`01eb2ef1
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 12:07:22.580 2011 (GMT-4)
System Uptime: 0 days 0:00:41.376
Probably caused by : ntkrnlmp.exe ( nt!ObpDecrementHandleCount+81 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  MpCmdRun.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!ObpDecrementHandleCount+81
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`021091b1 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 12:04:57.578 2011 (GMT-4)
System Uptime: 0 days 0:06:57.375
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ataport.SYS - 
Probably caused by : ataport.SYS ( ataport!AtaPortInitialize+1ef0 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!AtaPortInitialize+1ef0
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`0000000c 00000000`00000000 fffff800`01ebd026
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 11:56:19.749 2011 (GMT-4)
System Uptime: 0 days 0:01:19.421
*** ERROR: Module load completed but symbols could not be loaded for ecache.sys
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : ecache.sys ( ecache+23c2 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  acrodist.exe
FAILURE_BUCKET_ID:  X64_0xC5_2_ecache+23c2
Bugcheck code 000000C5
Arguments 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`01f8416b
BiosVersion = 0807   
BiosReleaseDate = 10/31/2008
SystemManufacturer = System manufacturer
SystemProductName = P5QL PRO
MaxSpeed:     3160
CurrentSpeed: 3163
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]
 

·
Registered
Joined
·
6 Posts
Discussion Starter · #8 ·
Update:

so i've ran Seatools (short + long test) - everything came back good...

ran Memtest again over night with all 4 modules installed - 14 hours - 9 passes - everything came back good this time...

prime95 tests BSOD'ed after a few minutes anytime I tried to run them, didn't put much stock into it considering I wasn't exactly running it on a system I thought to be stable...

constant stop errors still continued throughout - even in safemode - sometimes I could get to the desktop (safemode or normal) for up to 10 minutes, most times would BSOD before loading login screen... decided to install Malewarebytes + run a scan on whim while waiting to hear back from someone over here yesterday... found 671 instances of a some whitesmoke toolbar virus? - removed...

same crap continued... I think I have 30+ minidumps by now...

today I looking through the Autoruns program and noticed a file still getting loaded on startup for whitesmoke... so I researched it further since apparently it was a bit more stubborn in nature than typical malware... ran TDSSKiller along with Malwarebytes again...

THE SYSTEM HAS BEEN ROCK SOLID FOR OVER 2 HOURS NOW

this is blowing my mind... kinda goes against alot of what I thought I knew about windows operating systems + safemode... I'm a graphic designer by trade now but got my degree in systems administration + networking about 4 years ago so some of this stuff has stuck around in the old brain... my neighbor who has been a manager at a techshop in town for around 10 years was also pretty convinced it was a hardware issue somewhere in the system given the constant BSOD's in safemode...

wierd? not so weird? expected with microsoft? I'd love your input on this...

so, I'm still very skeptical (or should I say scared given the way the past 4 days have went, I'm waiting for things to instantly lock up again) but it feels like I'm back to normal - I've been running multiple instances of chrome along with 64bit photoshop, illustrator, running virus scans all at the same time - basically putting a workload on the system + everything seems good now...

Thanks again for all your time - you guys are doing a GREAT thing here donating your time/expertise to help others...
 
1 - 8 of 8 Posts
Status
Not open for further replies.
Top