BSOD

[jushendrix]

well i built my computer around mid june and every week or so i would get a bsod every once in a while usually i never noticed ti because it would happen while i went to be watching media center and it would just be sitting their and id wake up to the your computer has shutdown message box on my desktop. well after a month or so i have just started looking into my event log and such and trying to figure out whats going wrong well about a week ago i have started to get bsod more often and more frequent like this morning in the hour i had before work i got 4 bsod while searching the net looking for other forum of people having the same errors as me.. i will post a few that i can remember but once i get home i will try to post more


Kernal-power 41 (63)
until last night i was gettting a Tages driver error but i had re installed it and didnt see that in my event log this morning so i assume that is fixed
as welll as the kernal power error i am also gettting the bugcheck 109 bluescreen error along with a blue screen that shows just 000000000 so im just at a loss as what the next step would be to do in finding a solution

i have already updated my MB drivers as well as my video card and a few other ones that i have read in other forums that could cause this problem but to avail i am still gettting bsod and more frequent then ever now....


please help...

 

[Tews]

Blue Screen of Death (BSOD) Posting Instructions

 

[jushendrix]

thanks like i said im at work so once i get home i will try to do that

 

[Dzomlija]

This comes directly from Microsoft: I have highlighted the relevant data for you

Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION

Cause


There are generally three different causes for this bug check:

1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
2. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.

 

[jushendrix]

here is my Bsod required files

also i am running Windows 7 64 bit enterprise edition
biostar MB
8 gb g-skill ram ( took 3 sticks out) to see if maybe my ram is bad
intel i5 dual core cpu
hd 4870 hd radeon grAphics card
and im using a zonet wireless network adapter
HEC 1080W psply

 

[reventon]

Hi,

No clear cause here.

Several possiblities - we will see what we can do about them.

STPD.sys is known to cause BSODs; remove Daemon Tools, then use this SPTD installer to remove it (pick the uninstall option when you run the installer): DuplexSecure - Downloads

Tages - this has been known to cause BSODs before. Remove this. From their website:

Alternatively, the drivers can be installed/un-installed through our software, TagesSetup; it acts as a toggle, installing the drivers if they were not installed, and un-installing them if they were installed.

So download the installer and use it to uninstall - TAGES, the AAA Copy Protection System

If you are still getting problems after that then run a Memtest

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: ISO Recorder v3 Download (How to use IsoRecorder)

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.

If that passes and you are still getting problems then run Driver Verifier.

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

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 14 01:05:38.425 2010 (GMT+12)
System Uptime: 0 days 0:01:59.566
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98a2f525 b3b7465e`eb1fc71b fffff800`02e1f890 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 14 01:03:00.694 2010 (GMT+12)
System Uptime: 0 days 0:04:06.834
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98a51532 b3b7465e`eb21e728 fffff800`02e8f7f4 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 14 00:58:02.931 2010 (GMT+12)
System Uptime: 0 days 0:07:00.072
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02f6bb1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 17:38:01.089 2010 (GMT+12)
System Uptime: 0 days 0:01:59.246
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98a4084b b3b7465e`eb20da41 fffff800`02e1f8a0 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 17:35:05.858 2010 (GMT+12)
System Uptime: 0 days 0:04:00.952
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9c4bf8bb b3b7465e`eec8cab1 fffff800`02f177ea 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 17:21:40.057 2010 (GMT+12)
System Uptime: 0 days 0:01:18.198
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MOM.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`02f17965 fffff880`07587eb0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 17:18:34.505 2010 (GMT+12)
System Uptime: 0 days 0:11:27.646
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonWrite+da0 )
PROCESS_NAME:  MsMpEng.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0592d128 fffff880`0592c990 fffff800`02eaf2b7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 17:06:03.973 2010 (GMT+12)
System Uptime: 0 days 0:42:18.067
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00208d7b 00000000`00000002 00000000`00000001 fffff800`02f2bb1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 14:59:41.860 2010 (GMT+12)
System Uptime: 0 days 0:30:00.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`990eba1b b3b7465e`eb8c8a01 fffff800`02e1f90c 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 16:05:09.952 2010 (GMT+12)
System Uptime: 0 days 0:08:28.092
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98c629e2 b3b7465e`eb42fbe8 fffff800`02f87570 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 15:46:20.915 2010 (GMT+12)
System Uptime: 0 days 0:11:06.055
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02f26b1f fffff880`07dfecb0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 15:34:16.329 2010 (GMT+12)
System Uptime: 0 days 0:12:11.469
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02f78b1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 14:28:45.572 2010 (GMT+12)
System Uptime: 0 days 0:03:14.666
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`737cd048 00000000`00000002 00000000`00000001 fffff800`02f3db1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 14:24:54.109 2010 (GMT+12)
System Uptime: 0 days 0:00:16.250
Probably caused by : memory_corruption
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02f17963 fffff880`031c3ff8 fffff880`031c3860
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 14:06:40.875 2010 (GMT+12)
System Uptime: 0 days 0:02:00.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98a14774 b3b7465e`eb1e196a fffff800`02f177f1 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 12 18:36:16.042 2010 (GMT+12)
System Uptime: 0 days 0:32:11.183
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+21c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d7c94c fffff880`05ee2fb0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 12 18:03:06.861 2010 (GMT+12)
System Uptime: 0 days 4:13:01.017
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02d6eb1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 12 13:43:06.614 2010 (GMT+12)
System Uptime: 0 days 0:12:00.676
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+317 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000018 00000000`00000002 00000000`00000000 fffff800`02d7dbc7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 11 12:07:05.008 2010 (GMT+12)
System Uptime: 0 days 0:10:29.118
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`0020473f 00000000`00000002 00000000`00000001 fffff800`02d2bb1f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 11:19:48.998 2010 (GMT+12)
System Uptime: 2 days 7:02:35.123
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02d2ba5f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 03:48:47.490 2010 (GMT+12)
System Uptime: 0 days 11:28:00.000
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9d8844f9 b3b7465e`f00516ef fffff800`02f1795e 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug  4 21:03:22.335 2010 (GMT+12)
System Uptime: 0 days 10:42:30.398
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02d7da5f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 21:27:44.688 2010 (GMT+12)
System Uptime: 3 days 9:12:30.257
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`02d89a5f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[jushendrix]

mmm also in my event log is the error
Error 8/13/2010 7:30:39 PM Service Control Manager 7009 None

A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 9 service to connect.



and i have no idea what or how roxio hard drive watcher 9 got on my machine..

 

[reventon]

mmm also in my event log is the error
Error 8/13/2010 7:30:39 PM Service Control Manager 7009 None

A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 9 service to connect.



and i have no idea what or how roxio hard drive watcher 9 got on my machine..

Deal with the things I mentioned in my above post first - I have a feeling that error is a symptom rather than a cause.

 

[jushendrix]

alright well like i said i had removed three sticks of ram and i have done the first two things with tages and STPD. and it looks good so far but only time will tell will report back once i have run memtest a few times

 

[jushendrix]

Alright well after running memtest a few times i found that one of my sticks of ram was giving me errors so im hoping that is all of what is causeing my bsod but once i get rdy for bed i willl run memtest while i sleep with the other 3 sticks in to see if i need to run more times on each indivdual one.

 

[reventon]

Alright well after running memtest a few times i found that one of my sticks of ram was giving me errors so im hoping that is all of what is causeing my bsod but once i get rdy for bed i willl run memtest while i sleep with the other 3 sticks in to see if i need to run more times on each indivdual one.

Once you get errors - take a photo of them as proof and then RMA the set back to the manufacturer.

 

[jushendrix]

Alright well after running memtest a few times i found that one of my sticks of ram was giving me errors so im hoping that is all of what is causeing my bsod but once i get rdy for bed i willl run memtest while i sleep with the other 3 sticks in to see if i need to run more times on each indivdual one.

Once you get errors - take a photo of them as proof and then RMA the set back to the manufacturer.

well i already looked at g-skills website i dont think they require a picture so im gonna try it without and we'll see