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: My bsods, do help please!


30 Apr 2011   #1

Windows 7 Home Premium 64bit
 
 
My bsods, do help please!

Hello!
I am a new member and I have had problems with bsods since some time now(over a month). See, I was looking for a cure for those for this whole time. Finally, two days ago, I decided to register at Windows 7 forums (notice I said Windows 7 forums, not sevenforums), where I was told that my bsods are caused by wrongly matched RAM sticks. Is it possible? Can you do your own analysis?

Here are the files, they required from me. Oh and please don't treat this post as a spam or plagiatism, I am just looking for an alternative to getting my 2 gb ram (out of 4 gb) stick out of the PC...
Please help and godspeed, my friends, godspeed.

Ps. It might be worth mentioning that I have bsods when playing online games (FPSs). The same happens, but less frequent, to other games I play.

- x86 (32-bit) or x64 ? x86 (64 bit)
- the original installed OS on the system? Windows 7
- an OEM or full retail version? Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? About 3-4 months(?)
- What is the age of OS installation (have you re-installed the OS?) No and same as the hardware, 3-4 months.

My System SpecsSystem Spec
.

30 Apr 2011   #2

Windows 7 Home Premium 64bit
 
 

Anybody? Hello? Why don't you answer my post, I really need help here!
My System SpecsSystem Spec
30 Apr 2011   #3

Windows 7 Professional x64
 
 

Hi there,

No worries, it was only 30 minutes between your post and your bump. Most forums take hours to reply, and even then, you won't get good support.

Well I see you've got a 1GB stick in Slot 1, and a 2GB stick in Slot 2. That's not an ideal situation, but there isn't enough evidence to determine for sure.

From all appearances, the problem is being caused by hardware; yet one software possibility jumps out at me. SPTD, a driver used by Daemon Tools and Alcohol, is well-known for causing BSODs, including ones that appear to be caused by hardware. Uninstall Daemon Tools, and then remove SPTD itself with the tool found here: DuplexSecure

I see Cybercore mentioned Memtest86, but I couldn't see if it was actually run. Please run it for at least 8 passes: RAM - Test with Memtest86+

Also, run the Small FFTs and Blend Prime95 tests: http://www.sevenforums.com/tutorials...t-prime95.html

In short, hardware does seem to be the likely cause, but I feel the conclusion on the other forum was very premature. There is not nearly enough evidence at this point to determine for sure the problem is with RAM, although it is a significant possibility.

...Summary of the dumps:
Code:

Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 29 12:28:52.531 2011 (UTC - 4:00)
System Uptime: 0 days 2:08:45.872
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 29 10:18:58.769 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:22.094
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  RedOrchestra.e
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 29 10:00:21.089 2011 (UTC - 4:00)
System Uptime: 0 days 6:10:02.430
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  fsav32.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 14:53:13.114 2011 (UTC - 4:00)
System Uptime: 0 days 0:20:11.236
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  RedOrchestra.e
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 14:31:48.053 2011 (UTC - 4:00)
System Uptime: 0 days 7:01:15.394
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  RedOrchestra.e
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 07:29:17.155 2011 (UTC - 4:00)
System Uptime: 0 days 5:07:49.480
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 02:20:02.822 2011 (UTC - 4:00)
System Uptime: 0 days 15:05:20.163
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 26 11:13:27.533 2011 (UTC - 4:00)
System Uptime: 0 days 0:32:01.858
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 26 10:40:17.760 2011 (UTC - 4:00)
System Uptime: 0 days 0:56:39.101
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+422bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_atikmdag+422bf2
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 15 11:55:38.262 2011 (UTC - 4:00)
System Uptime: 0 days 1:27:48.602
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 15 10:26:12.632 2011 (UTC - 4:00)
System Uptime: 0 days 17:34:34.957
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 14 16:49:49.307 2011 (UTC - 4:00)
System Uptime: 0 days 19:06:03.633
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 13 21:42:20.952 2011 (UTC - 4:00)
System Uptime: 0 days 2:04:17.293
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 12 16:52:24.712 2011 (UTC - 4:00)
System Uptime: 0 days 0:31:48.053
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  java.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 12 16:19:20.267 2011 (UTC - 4:00)
System Uptime: 0 days 3:51:13.608
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 12 12:26:21.839 2011 (UTC - 4:00)
System Uptime: 13 days 2:03:05.572
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 07:39:17.144 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:25.469
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 07:24:26.634 2011 (UTC - 4:00)
System Uptime: 0 days 4:58:09.960
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SetPoint.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 02:25:03.909 2011 (UTC - 4:00)
System Uptime: 0 days 17:26:31.409
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar 28 08:55:54.097 2011 (UTC - 4:00)
System Uptime: 0 days 18:02:12.438
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Crysis2.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 14:52:29.558 2011 (UTC - 4:00)
System Uptime: 0 days 2:40:55.899
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Crysis2.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 12:10:27.552 2011 (UTC - 4:00)
System Uptime: 0 days 0:29:01.877
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Crysis2.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 11:40:20.720 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:07.045
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1a621 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xE3
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xE3_nt!_??_::FNODOBFM::_string_+1a621
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 10:22:07.663 2011 (UTC - 4:00)
System Uptime: 0 days 0:37:30.989
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
Probably caused by : Npfs.SYS ( Npfs+c16a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  fsorsp.exe
FAILURE_BUCKET_ID:  X64_0xA_Npfs+c16a
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 09:43:30.509 2011 (UTC - 4:00)
System Uptime: 0 days 7:24:02.849
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3fbac0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+3fbac0
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 02:18:19.086 2011 (UTC - 4:00)
System Uptime: 0 days 0:54:33.427
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  fssm32.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 27 01:22:39.093 2011 (UTC - 4:00)
System Uptime: 0 days 2:58:36.434
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*** 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+73bc )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 26 22:22:51.701 2011 (UTC - 4:00)
System Uptime: 3 days 12:01:41.061
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Crysis2.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 23 10:19:11.910 2011 (UTC - 4:00)
System Uptime: 6 days 17:46:58.172
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 16 16:30:07.797 2011 (UTC - 4:00)
System Uptime: 4 days 5:26:55.277
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mow_assault_sq
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 26 05:27:15.311 2011 (UTC - 4:00)
System Uptime: 0 days 1:19:33.636
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 26 04:06:19.264 2011 (UTC - 4:00)
System Uptime: 0 days 12:31:50.589
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 15:33:23.091 2011 (UTC - 4:00)
System Uptime: 0 days 0:25:38.416
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  fssm32.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 15:06:22.276 2011 (UTC - 4:00)
System Uptime: 0 days 1:03:25.602
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 14:01:43.885 2011 (UTC - 4:00)
System Uptime: 0 days 0:39:33.277
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 25 13:20:15.934 2011 (UTC - 4:00)
System Uptime: 4 days 19:35:15.389
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  RedOrchestra.e
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 10 00:35:29.007 2011 (UTC - 4:00)
System Uptime: 0 days 13:15:41.348
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Release+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Sins of a Sola
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGFASTMUTEX::Release+12
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 16:23:41.438 2011 (UTC - 4:00)
System Uptime: 0 days 2:01:49.779
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  FalloutNV.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 14:19:50.960 2011 (UTC - 4:00)
System Uptime: 2 days 16:53:00.182
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Feb  4 21:24:56.284 2011 (UTC - 4:00)
System Uptime: 3 days 2:48:34.735
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!memset+181a )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Anno4.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_win32k!memset+181a
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 16:59:42.372 2011 (UTC - 4:00)
System Uptime: 0 days 0:45:28.908
Probably caused by : dxgkrnl.sys ( dxgkrnl+25f6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl+25f6
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 16:12:42.498 2011 (UTC - 4:00)
System Uptime: 0 days 22:54:13.824
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 23 17:17:17.567 2011 (UTC - 4:00)
System Uptime: 0 days 1:09:41.662
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 23 16:05:57.774 2011 (UTC - 4:00)
System Uptime: 0 days 14:50:45.099
Probably caused by : dxgkrnl.sys ( dxgkrnl+25f6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WorldOfTanks.e
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl+25f6
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 23 01:13:49.402 2011 (UTC - 4:00)
System Uptime: 1 days 21:55:37.293
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Jan 21 03:15:55.491 2011 (UTC - 4:00)
System Uptime: 0 days 3:57:17.832
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 20 23:16:58.890 2011 (UTC - 4:00)
System Uptime: 1 days 13:08:56.230
Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+f7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TS3.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCleanProcessAddressSpace+f7
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 19 10:06:52.722 2011 (UTC - 4:00)
System Uptime: 0 days 0:26:33.169
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 16 16:35:16.559 2011 (UTC - 4:00)
System Uptime: 0 days 5:42:06.312
Probably caused by : memory_corruption ( nt!MiMakeProtoAddressValid+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  RelicCOHOWW.ex
FAILURE_BUCKET_ID:  X64_0x50_nt!MiMakeProtoAddressValid+4d
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 16 10:51:51.037 2011 (UTC - 4:00)
System Uptime: 3 days 17:00:27.110
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::UnmapViewOfAllocation+78 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  RelicCOHOWW.ex
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_PROCESS_HEAP::UnmapViewOfAllocation+78
BiosReleaseDate = 06/18/2009
SystemProductName = P35C-DS3R
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
.


30 Apr 2011   #4

Windows 7 Home Premium 64bit
 
 

Well, it said there was a hardware error. I am going to bed now, though. I hope you subscribe this thread so we can talk later on, when I do full check. How do I upload results if I even can do so? and as mentioned on the windows 7 forums, I am not a techie, thus I have no idea how to install mem-test 86, furthermore, I am freaked out that I might not be able to restart my computer once I put in my PC.

Ps. Oh and I've read that sometimes the blend prime 95 can cause some problems without a reason (yes I did set it to the point where it tests the RAM thing the most), thus I am not certain about this problem I mentioned earlier. How do I upload? If you tell me, the first thing I wake up tomorrow is going to send you guys the results!
My System SpecsSystem Spec
01 May 2011   #5

Windows 7 Professional x64
 
 

Hi there,

I wrote up a guide to using Memtest86; I tried to make it simple enough anyone could follow it step-by-step and get it to work. See here: RAM - Test with Memtest86+

No worries, it shouldn't affect your ability to boot at all.

Those tests have nothing to be uploaded; just tell us if it shows any errors.
My System SpecsSystem Spec
01 May 2011   #6

Windows 7 Home Premium 64bit
 
 

Ok, I only have one question. Do I need keyboard for memtest86? Because mine doesn't work unless the computer is already after the windows loading bar and logo....
Oh yes, and as I said, please do subscribe the topic as I like to use my computer at day and it will probably take me another night to test the computer. What I mean is, I don't want to leave the topic like it is and then wait until it is on 15th page and no replies because nobody looks that far!
My System SpecsSystem Spec
01 May 2011   #7

Windows 7 Professional x64
 
 

You'll need the keyboard to close out of Memtest86, but you could just hit the power button. Of more concern is how you're going to select what boot device without a keyboard. Stick the USB drive/CD, whichever you created in the drive, and then reboot.

See here: How to Boot From a CD/DVD/USB Device - Sysnative.com

If it doesn't boot up Memtest86 automatically, you'll need to find a different keyboard in able to follow that guide.
My System SpecsSystem Spec
01 May 2011   #8

Windows 7 Home Premium 64bit
 
 

Err, umm, hmmmm. Do you have any guides or ideas how to make G-510 keyboard work while booting, by any chance? Finding replacement keyboard can be a b**ch, you know.
My System SpecsSystem Spec
Reply

 My bsods, do help please!




Thread Tools



Similar help and support threads for2: My bsods, do help please!
Thread Forum
Solved Many BSODs while doing anything! BSOD Help and Support
BSODs, lots of BSODS BSOD Help and Support
A few different BSODs.. BSOD Help and Support
Bsods help BSOD Help and Support
BSODs every day... need help BSOD Help and Support
BSODs - need help! 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 06:42 AM.
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