Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent crashes (BSOD) on the new PC with BSOD Dump attached


26 Jan 2012   #1

Windows 7 Ultimate x64
 
 
Frequent crashes (BSOD) on the new PC with BSOD Dump attached

Hi guys, can anyone please help my problem, I had my PC crashing almost everyday, and several times a day. Please find my attached collection of memory dump & PC Health report.

Thanks very much!

I am on Windows 7 Ultimate x64
- x64
- the original installed OS on the system - Ultimate
- an OEM or full retail version? - OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? - newly bought less than 2 months
- What is the age of OS installation (have you re-installed the OS?) Did reinstalled.


My System SpecsSystem Spec
.

26 Jan 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

95% of the crashes are memory corruption. Let's start off by testing the memory

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

BSOD BUGCHECK SUMMARY
Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 25 15:54:34.955 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:31.782
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 18:14:49.901 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:11.118
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
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!MiGetTopLevelPfn+65
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 18:13:01.962 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:29.179
*** 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
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_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 18:06:06.877 2012 (UTC - 5:00)
System Uptime: 0 days 0:16:10.705
*** 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
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_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 16:41:31.195 2012 (UTC - 5:00)
System Uptime: 0 days 0:44:16.413
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 15:26:46.127 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:49.955
Probably caused by : memory_corruption
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_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 15:25:32.356 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:52.574
Probably caused by : memory_corruption
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:  TrustedInstall
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 15:22:46.832 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:45.034
Probably caused by : memory_corruption
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:  poqexec.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 15:21:26.989 2012 (UTC - 5:00)
System Uptime: 0 days 9:28:07.817
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 20 09:48:00.047 2012 (UTC - 5:00)
System Uptime: 0 days 1:03:25.249
*** 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:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 17 17:32:34.301 2012 (UTC - 5:00)
System Uptime: 0 days 0:10:33.129
Probably caused by : memory_corruption
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:  TrustedInstall
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 17 17:21:36.311 2012 (UTC - 5:00)
System Uptime: 0 days 0:10:38.528
Probably caused by : memory_corruption
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:  TrustedInstall
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 17 17:10:34.433 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:53.261
Probably caused by : memory_corruption
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:  TrustedInstall
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 16 08:38:06.292 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:10.120
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
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!MiGetTopLevelPfn+65
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 15:22:37.786 2012 (UTC - 5:00)
System Uptime: 0 days 0:21:56.613
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : NETIO.SYS ( NETIO!NsiParameterChange+5b )
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_NETIO!NsiParameterChange+5b
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 08:09:46.867 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:36.084
*** 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:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 17:29:09.308 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:23.136
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
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!MiGetTopLevelPfn+65
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 17:27:22.537 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:22.365
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
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!MiGetTopLevelPfn+65
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 15:39:58.845 2012 (UTC - 5:00)
System Uptime: 0 days 0:19:26.062
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+7a1c )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 15:11:04.176 2012 (UTC - 5:00)
System Uptime: 0 days 0:16:08.378
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  PPSAP.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 14:54:29.276 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:17.104
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
BUGCHECK_STR:  0x1a_1236
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 15:16:53.915 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:01.117
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
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!MiGetTopLevelPfn+65
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 15:09:41.878 2012 (UTC - 5:00)
System Uptime: 0 days 0:02:15.706
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  avgcsrva.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  9 15:53:31.464 2012 (UTC - 5:00)
System Uptime: 0 days 0:21:08.681
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+115 )
BUGCHECK_STR:  0x1a_8885
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 10:45:47.293 2012 (UTC - 5:00)
System Uptime: 0 days 0:41:52.120
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 09:56:38.537 2012 (UTC - 5:00)
System Uptime: 0 days 0:49:42.754
Probably caused by : memory_corruption
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:  rundll32.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 16:02:43.335 2012 (UTC - 5:00)
System Uptime: 0 days 0:17:56.162
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 15:41:26.836 2012 (UTC - 5:00)
System Uptime: 0 days 0:12:32.664
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 15:28:26.783 2012 (UTC - 5:00)
System Uptime: 0 days 0:40: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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 14:39:47.369 2012 (UTC - 5:00)
System Uptime: 0 days 0:21:28.197
Probably caused by : hardware ( NETIO!InsertTimerWheelElement+1e )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_NETIO.SYS
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 14:00:11.295 2012 (UTC - 5:00)
System Uptime: 0 days 1:25:38.513
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  1 18:36:12.755 2012 (UTC - 5:00)
System Uptime: 0 days 5:12:48.973
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+36e9 )
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_AVGIDSFilter+36e9
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 05:11:15.309 2012 (UTC - 5:00)
System Uptime: 0 days 0:35:51.518
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 30 09:20:08.192 2011 (UTC - 5:00)
System Uptime: 0 days 0:23:00.487
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 25 18:46:26.010 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:57.305
*** 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
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 25 18:39:53.969 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:36.891
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Maxthon.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+1cc
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
27 Jan 2012   #3

Windows 7 Ultimate x64
 
 

Thanks a lot for reply. I have done MemTest before. But I tested with both 2 DDR3 (each 4GB) in slot.
Do I need to test them separately? Thanks again.
My System SpecsSystem Spec
.


27 Jan 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

If you don't get any errors then no. But if you get errors and want to single out the bad stick or bad mobo slot then yes
My System SpecsSystem Spec
28 Jan 2012   #5

Windows 7 Ultimate x64
 
 

I have done both tests. but no errors reported. Can you please shed some lights on this please? Thank you vm.
My System SpecsSystem Spec
28 Jan 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

You ran all three prime95 tests for 3-4 hours each? And you ran memtest for 7-8 passes? No errors reported?



If that is the case then enable driver verifier
Driver Verifier - Enable and Disable


If it isn't the case, then run the recommended tests.
My System SpecsSystem Spec
29 Jan 2012   #7

Windows 7 Ultimate x64
 
 

No problem of these tests. Again, today another crash, just after I inputed windows 7 password.

from Event Viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000001236, 0xfffffa80082b9a10, 0xfffffa80082b9b08, 0x00000000001cbf1b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012912-13806-01.
My System SpecsSystem Spec
29 Jan 2012   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Enable driver verifier
My System SpecsSystem Spec
30 Jan 2012   #9

Windows 7 Ultimate x64
 
 

It failed to enable verifier. I tried a couple of times, when I followed the instruction and rebooted. Windows failed to start. Have to restore. Any hints from this? or any other ways to try? I am so frustrated about this. Appreciate if indeed you can help. Thanks a lot.
My System SpecsSystem Spec
31 Jan 2012   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Did you get a blue screen when you started or it just didn't start?

Try running half of the drivers and see if you can boot.

We need to get a crash blaming a driver.
My System SpecsSystem Spec
Reply

 Frequent crashes (BSOD) on the new PC with BSOD Dump attached




Thread Tools



Similar help and support threads for2: Frequent crashes (BSOD) on the new PC with BSOD Dump attached
Thread Forum
Explorer frequent crashes (dump file attached) BSOD Help and Support
Very frequent dump memory BSOD crashes BSOD Help and Support
Solved Frequent BSOD's, can't find a clear pattern. dump attached BSOD Help and Support
BSOD (dump attached) BSOD Help and Support
Daily BSOD (dump attached) BSOD Help and Support
Random BSOD... Help please (BSOD dump & system health report attached) BSOD Help and Support
BSOD problem - dump is attached BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 08:41 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33