Windows 7: New build, AMD based, almost daily BSOD

TSDAdam · 17 Mar 2011

Hi all, I've read as much as I can to try and solve my BSODs but no joy so far so I thought I'd post here.

I'm getting them at random times, often when I'm not putting the computer under load or doing any one thing I can find to trigger it. Here are my specs.

AMD Phenom II X4 965 BE (quad core @ 3.4GHz)
4GB Corsair RAM
Asus Mobo
EVGA GFX460 1GB (Nvidia)
Samsung Spinpoint 1TB HDD (sata)

I built the computer and installed windows myself.

I'm running Windows 7 Home Premium x64 Full OEM. I've attached what's asked for, so hopefully someone can point me in the right direction. Here's hoping!

Thanks in advance

Jonathan_King · 17 Mar 2011

Hello,

See if you can uninstall the nVidia Stereoscopic driver:

Code:

Event[1923]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-03-12T14:47:10.670
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Adam-PC
  Description: 
The NVIDIA Stereoscopic 3D Driver Service service failed to start due to the following error: 
NVIDIA Stereoscopic 3D Driver Service is not a valid Win32 application.

Install SP1: Learn how to install Windows 7 Service Pack 1 (SP1)

I notice the clock is (or was) seriously off:

Code:

Original Install Date:     08/02/2011, 22:55:19

See this log:

Code:

Event[1723]:
  Log Name: System
  Source: Microsoft-Windows-Time-Service
  Date: 2011-03-13T01:00:18.006
  Event ID: 34
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Adam-PC
  Description: 
The time service has detected that the system time needs to be  changed by -86294 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123) is working properly.

Do as the report says; make sure the time is correct in the BIOS as well as in Windows.

Also, some hardware diagnostics are in order. Start with the three Prime95 tests: http://www.sevenforums.com/tutorials...t-prime95.html

Run Memtest86 for 7 passes: RAM - Test with Memtest86+

...Summary of the dumps:

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Mar 18 15:04:01.959 2011 (UTC - 4:00)
System Uptime: 0 days 1:12:53.676
Probably caused by : win32k.sys ( win32k!RFONTOBJ::vDeleteRFONT+33 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!RFONTOBJ::vDeleteRFONT+33
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Mar 18 13:50:06.782 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:08.124
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar 14 08:22:40.439 2011 (UTC - 4:00)
System Uptime: 0 days 0:31:09.171
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 16:00:12.366 2011 (UTC - 4:00)
System Uptime: 0 days 0:41:25.083
Probably caused by : ntkrnlmp.exe ( nt!ExDeleteResourceLite+b8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExDeleteResourceLite+b8
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 26 03:49:20.753 2011 (UTC - 4:00)
System Uptime: 0 days 11:32:11.095
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+96 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!RtlDeleteNoSplay+96
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 16:57:42.713 2011 (UTC - 4:00)
System Uptime: 1 days 4:03:46.056
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 13:48:39.200 2011 (UTC - 4:00)
System Uptime: 0 days 0:23:48.542
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+3b90a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+3b90a
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 14:36:30.037 2011 (UTC - 4:00)
System Uptime: 0 days 1:28:26.769
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+ca0
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 15:01:56.624 2011 (UTC - 4:00)
System Uptime: 0 days 3:36:09.356
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+53d
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 10 19:40:10.502 2011 (UTC - 4:00)
System Uptime: 0 days 6:20:43.860
Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownStructures+18e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownStructures+18e
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

TSDAdam · 18 Mar 2011

Thanks for that. I saw that ntkrnlmp.exe is very low level, and can point to a problem with hardware. I might have a look at the PSU, as I think I'm borderline having a 450W PSU and a graphics card which claims to need a 450W supply.

Jonathan_King · 18 Mar 2011

If the PSU is a lower quality, chances are very good it is not providing even 450W.

ntkrnlmp.exe blamed in dumps can mean either hardware or software, so it's tough to go on that. I do believe this may be hardware related, though.

TSDAdam · 18 Mar 2011

It's a decent PSU, Corsair case builder series, but I've got a sneaking, horrible suspicion it's only 430W.

If this is the case, does it sound feasible, or would I be more likely to be looking at RAM/Motherboard?

I'll be running memtest and prime95 tonight with a bit of luck.

Jonathan_King · 18 Mar 2011

Corsair is a highly respected and reliable brand, so aside from those occasional defective ones, you can expect that PSU to output what it claims. However, I wouldn't rule out power problems quite yet, because if you're pushing it so close to the line, you very well may see problems. I'd recommend you try out a higher wattage PSU, say at least 550W.

Carry on with the other tests as well.

TSDAdam · 18 Mar 2011

I've run the tests suggested. Prime95 and it didn't bat an eyelid, CPU temp didn't get above 48 degrees. I've just finished running 7 passes of memtest too, without a single error.

Jonathan_King · 19 Mar 2011

Could you try a higher wattage PSU?

Windows 7: New build, AMD based, almost daily BSOD

New build, AMD based, almost daily BSOD problems?