Windows 7: BSOD after leaving computer unattended. Sometimes win32.sys error

nzdreamer55 · 23 Dec 2011

Hello everyone,

I have read the instruction for posting to this forum and hopefully have done it correctly. I have a home built computer (built about Mid 2010) that is our HTPC. When I first set it up I would get the BSOD every once in a while (3-4 months), but since this computer was not critical, would just restart and things would be fine. Now it is happening a lot and I need to get to the bottom of why. This computer will do a lot of work as it acts as a storage for files that are served to other computers in the house and to the internet (torrents). I use media portal for viewing my media and listening to music. The errors that I have had are various so it is hard to tell you what I have right now (I think a non-page fault error most recently).

I can get you more info, but as of now have just posted per the instructions hoping to get a kind soul to help me. One thing about this motherboard is that there are a lot of things that can be changed. I tried to set it on the most automatic of the settings so as not to create more problems.

Thanks
-S

mgorman87 · 23 Dec 2011

Your crashes are all over the place but it seems like you either have bad hardware or possible OS corruption. I would like you to start off by running some hardware diagnostic tests and report back the results

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec 23 01:20:21.593 2011 (UTC - 5:00)
System Uptime: 0 days 3:44:51.811
Probably caused by : memory_corruption ( nt!MiTrimWorkingSet+c0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiTrimWorkingSet+c0
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Dec 22 21:32:53.740 2011 (UTC - 5:00)
System Uptime: 1 days 5:10:03.332
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware ( win32k+cc64a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  consent.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec 21 16:09:48.200 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:31.746
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
BUGCHECK_STR:  0x1E_c000001d
PROCESS_NAME:  LogonUI.exe
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec 21 03:42:37.369 2011 (UTC - 5:00)
System Uptime: 0 days 0:46:44.915
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware ( win32k+8cfca )
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec 21 02:54:33.370 2011 (UTC - 5:00)
System Uptime: 0 days 14:47:05.915
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+883bd )
BUGCHECK_STR:  0xc2_7_TNbl
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_TNbl_tcpip+883bd
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Dec 18 23:14:19.715 2011 (UTC - 5:00)
System Uptime: 0 days 2:46:43.260
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+88e86 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  autounpack.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+88e86
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec  3 08:22:31.775 2011 (UTC - 5:00)
System Uptime: 0 days 9:22:31.320
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+762 )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+762
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Nov 28 02:06:37.712 2011 (UTC - 5:00)
System Uptime: 0 days 13:29:32.258
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleasePagingResource+5 )
PROCESS_NAME:  MsMpEng.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsReleasePagingResource+5
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Nov 26 19:53:22.695 2011 (UTC - 5:00)
System Uptime: 0 days 1:01:32.287
*** ERROR: Module load completed but symbols could not be loaded for srv2.sys
Probably caused by : srv2.sys ( srv2+306d5 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_srv2+306d5
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Nov 25 15:50:48.070 2011 (UTC - 5:00)
System Uptime: 0 days 15:08:12.662
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteScb+108
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Nov 25 00:39:22.361 2011 (UTC - 5:00)
System Uptime: 0 days 0:52:26.953
Probably caused by : ntkrnlmp.exe ( nt!CmpFlushNotify+ca )
BUGCHECK_STR:  0xc2_d
PROCESS_NAME:  MediaPortal.ex
FAILURE_BUCKET_ID:  X64_0xc2_d_nt!CmpFlushNotify+ca
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Nov 24 23:45:02.472 2011 (UTC - 5:00)
System Uptime: 2 days 23:25:50.064
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c96
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct 22 00:13:23.291 2011 (UTC - 5:00)
System Uptime: 3 days 1:41:34.883
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::~DXGCONTEXT+eb )
BUGCHECK_STR:  0xc2_d
PROCESS_NAME:  MediaPortal.ex
FAILURE_BUCKET_ID:  X64_0xc2_d_dxgkrnl!DXGCONTEXT::_DXGCONTEXT+eb
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 26 12:56:34.787 2011 (UTC - 5:00)
System Uptime: 0 days 16:12:01.004
Probably caused by : memory_corruption ( nt!MmDeleteTeb+78 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmDeleteTeb+78
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug  8 02:57:23.231 2011 (UTC - 5:00)
System Uptime: 0 days 12:14:22.823
Probably caused by : Ntfs.sys ( Ntfs!ExAllocateFromNPagedLookasideList+12 )
PROCESS_NAME:  svchost.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!ExAllocateFromNPagedLookasideList+12
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Aug  6 00:37:50.459 2011 (UTC - 5:00)
System Uptime: 5 days 10:47:53.051
Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupAllocation+e7 )
PROCESS_NAME:  MsMpEng.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsLookupAllocation+e7
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 21:53:49.408 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:29.047
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+4d773 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  smss.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::NNGAKEGL::_string_+4d773
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 15:04:05.732 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:31.371
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExFreePoolWithTag+43
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 14:40:00.339 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:54.619
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  MediaPortal.ex
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 11:18:49.940 2011 (UTC - 5:00)
System Uptime: 1 days 0:58:03.220
Probably caused by : win32k.sys ( win32k!memset+b0 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_win32k!memset+b0
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 01:48:05.116 2011 (UTC - 5:00)
System Uptime: 0 days 1:43:39.396
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+f47f )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!_??_::NNGAKEGL::_string_+f47f
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 16 08:15:27.050 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:04.704
*** ERROR: Module load completed but symbols could not be loaded for srv2.sys
Probably caused by : srv2.sys ( srv2+306d5 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_srv2+306d5
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 16 07:56:28.633 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:52.288
*** ERROR: Module load completed but symbols could not be loaded for srv2.sys
Probably caused by : srv2.sys ( srv2+306d5 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_srv2+306d5
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 16 07:24:50.359 2011 (UTC - 5:00)
System Uptime: 3 days 8:13:42.951
Probably caused by : Ntfs.sys ( Ntfs!ExFreeToNPagedLookasideList+3f )
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_Ntfs!ExFreeToNPagedLookasideList+3f
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jul 12 14:17:19.321 2011 (UTC - 5:00)
System Uptime: 0 days 22:28:50.539
*** ERROR: Module load completed but symbols could not be loaded for srv2.sys
Probably caused by : srv2.sys ( srv2+306d5 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_srv2+306d5
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul  7 15:31:42.594 2011 (UTC - 5:00)
System Uptime: 4 days 16:14:58.186
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c4b70 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  TeamViewer_Des
FAILURE_BUCKET_ID:  X64_0x50_win32k+c4b70
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 28 23:28:08.329 2011 (UTC - 5:00)
System Uptime: 1 days 2:27:22.921
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c54d8 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  TeamViewer.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+c54d8
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jun 22 16:36:39.186 2011 (UTC - 5:00)
System Uptime: 0 days 17:53:53.778
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+b9baf )
BUGCHECK_STR:  0x50
PROCESS_NAME:  TeamViewer_Des
FAILURE_BUCKET_ID:  X64_0x50_win32k+b9baf
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 20 22:49:02.645 2011 (UTC - 5:00)
System Uptime: 0 days 1:11:42.237
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4700d )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  MediaPortal.ex
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+4700d
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 19 12:35:19.046 2011 (UTC - 5:00)
System Uptime: 0 days 15:32:32.638
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aa69 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2aa69
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jun 15 11:28:18.650 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:50.242
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+25e )
BUGCHECK_STR:  0x50
PROCESS_NAME:  ForTheRecord.R
FAILURE_BUCKET_ID:  X64_0x50_nt!SeAccessCheckWithHint+25e
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 23:03:54.436 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:37.028
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 15 01:41:45.324 2011 (UTC - 5:00)
System Uptime: 0 days 7:21:40.916
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  9 03:05:10.285 2011 (UTC - 5:00)
System Uptime: 0 days 9:13:25.877
Probably caused by : hardware ( win32k!NtUserfnINLPCREATESTRUCT+190 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  1 23:33:16.331 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:56.923
Probably caused by : win32k.sys ( win32k!HmgIncrementShareReferenceCount+a )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgIncrementShareReferenceCount+a
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  1 23:24:42.505 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:48.723
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  1 20:41:20.281 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:25.873
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  MediaPortal.ex
FAILURE_BUCKET_ID:  X64_TRAP_FRAME_RECURSION
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr 30 22:14:50.999 2011 (UTC - 5:00)
System Uptime: 0 days 0:41:40.217
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+22c )
PROCESS_NAME:  uTorrent.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+22c
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr 21 05:06:26.404 2011 (UTC - 5:00)
System Uptime: 0 days 11:16:30.996
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Apr 20 17:48:11.918 2011 (UTC - 5:00)
System Uptime: 0 days 14:52:33.510
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+22c )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+22c
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Apr 20 02:53:03.087 2011 (UTC - 5:00)
System Uptime: 0 days 7:59:42.679
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Apr 17 12:00:58.994 2011 (UTC - 5:00)
System Uptime: 0 days 12:58:58.212
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryUsingHash+ac )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  autounpack.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpLookupDirectoryUsingHash+ac
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr 16 20:32:37.576 2011 (UTC - 5:00)
System Uptime: 0 days 15:12:11.168
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aa69 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2aa69
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Apr  6 20:56:33.440 2011 (UTC - 5:00)
System Uptime: 0 days 3:53:15.032
Probably caused by : Ntfs.sys ( Ntfs!NtfsCleanupIrpContext+239 )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCleanupIrpContext+239
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr  2 21:04:44.048 2011 (UTC - 5:00)
System Uptime: 3 days 3:06:19.265
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
BUGCHECK_STR:  0xc2_99
PROCESS_NAME:  ForTheRecord.U
FAILURE_BUCKET_ID:  X64_0xc2_99_win32k!FreeObject+58
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 29 00:04:01.007 2011 (UTC - 5:00)
System Uptime: 0 days 1:24:00.225
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+249 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TeamViewer_Des
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+249
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Mar 28 00:52:59.498 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:38.090
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4987d )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4987d
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Feb 27 17:32:01.679 2011 (UTC - 5:00)
System Uptime: 0 days 1:41:42.897
Probably caused by : hardware ( win32k!xxxRestoreCsrssThreadDesktop+a0 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msseces.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Feb 27 01:16:29.577 2011 (UTC - 5:00)
System Uptime: 0 days 4:18:31.795
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindBlockRun+83 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::FindBlockRun+83
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 22:39:05.661 2011 (UTC - 5:00)
System Uptime: 5 days 22:39:57.487
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  WebBrowser.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b
BiosReleaseDate = 06/10/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

nzdreamer55 · 23 Dec 2011

Thanks for the help. I am running the memtest right now and will report back later. I noticed one thing about the instructions that said

"If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings."

Should I check for inadequate settings first or just wait if there is an error then play with the settings?

Second on the Prime95.exe stress test, it say

"Keep an eye on your temperatures, and stop the test if the machine starts to overheat."

How will I know if my machine is overheating? It also talks about speed fan. Should I install this? Will this tell me if my machine is overheating? Will Prime95 tell me?

Thanks again for the help
-S

mgorman87 · 23 Dec 2011

Just run the tests for now and if they fail then we can look into the settings.

As for Prime95. You need to watch the temps for the first 20 minutes or so using Speedfan or another temperature monitoring program. If the temps stablize then you should be ok to let it run for 3-4 hours without watching it.

As for overheating, your CPU is rated at 71 degrees. If you start running prime95 and the temps shoot way up to 71 or above, stop the test immediately and check your cooling. As long as the temps are below 71 then you shouldn't have problems

nzdreamer55 · 23 Dec 2011

Great thanks. Here is the result from the memtest. 7 passes and no errors. I didn't know how to keep the results so I just took a picture. I also didn't do a lot of bank switching of the memory as there weren't any errors.

The P95 test is going now on it's first test (there are three) and the core and CPU are around 56 degrees Celsius and have been there for about 15 minutes. I have 1 200mm case fan that is always at 100%, 1 120mm fan over the drives except the OS drive which is a SSD. That is reporting a temp of 40 degrees. The other drives are less. And one small case fan 120mm. One large and one small fan is an exhaust, while the other blows air in over the drives. Of course there is the CPU fan that came with the processor.

One funny thing after I exited from the memtest and restarted the computer. I installed speed fan and while I was doing this the computer crashed and rebooted (NO BSOD).

So I'll run it for 2 hours on each of the 3 tests per the instruction. I think I am watching for one of the workers to fail indicating that there is an error or for the temp to climb above 70.

-S

nzdreamer55 · 03 Jan 2012

ok. so I ran all of those tests and no over heating problems and all the drives check out as well. I went so far as to install a new seagate drive as my os drive (Barracuda 7200RPM 1 TB SATA 6 GB/s NCQ 64 MB Cache 3.5-Inch Internal Bare Drive - ST1000DM003) and took the Solid state hard drive out of the picture as I read some info about these leading to BSOD. Still getting the BSOD.

Where should I go from here?
Thanks again for your help.

-S

mgorman87 · 04 Jan 2012

Try enablign driver verifier and see if that catches any misbehaving drivers

Driver Verifier - Enable and Disable

nzdreamer55 · 08 Jan 2012

Ok. So I enabled the driver verifier and I did get some hanging. No BSOD, but one restart and one hanging. Is there a log that I should post? I'm not sure which drivers are the problem. The tutorial only talked about enabling and if no problems after 24 hours then likely not a driver, but it didn't say what to do if you did get a problem.

I tried using the verifier /query command at a command prompt, but stuff flew by too fast to read.

Thanks mgorman87
-S

mgorman87 · 14 Jan 2012

If it was a driver causing problems you would get a BSOD. If you haven't gotten any then you can turn off driver verifier.

Are you still having problems since you first posted?

nzdreamer55 · 14 Jan 2012

You know, after I replaced my OS drive (SSD) to a mechanical drive, I don't seem to be having any problems. It has been a short time, but so far so good. Should I mark this a solved and then repost if I run into a problem?
If it is my SSD, can you recommend trouble shooting steps for this? The drive tests that I ran were all fine and there isn't any firm ware updates. Does windows 7 have problems with SSD? I know that these are relatively new technologies and that maybe there are still kinks to work out.
Thanks again
-S

Windows 7: BSOD after leaving computer unattended. Sometimes win32.sys error

BSOD after leaving computer unattended. Sometimes win32.sys error problems?