BSOD help, please and thank you

wrecked · 16 Aug 2011

Thank you for your time and help if you respond to this post.

I am running Windows 7 Home Premium in 64bits that a purchased from a retailer. This whole computer is cobbled together from other systems and some parts that I bought separately. Some pieces are a bit less than a year and some are older. The OS was installed within the last 9 months.

I don't have any idea what is happening or why I'm getting BSODs now. Thanks.

Jonathan_King · 17 Aug 2011

Hello,

You might start off by running a hard drive diagnostic on all your hard drives: SeaTools for Windows | Seagate

Code:

Event[2136]:
  Log Name: System
  Source: Disk
  Date: 2011-08-12T14:55:40.430
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rocketship
  Description: 
The driver detected a controller error on \Device\Harddisk2\DR2.

Also run Memtest86 and the three Prime95 tests.

RAM - Test with Memtest86+

https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 16 18:06:03.757 2011 (UTC - 4:00)
System Uptime: 0 days 2:42:46.160
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+433 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+433
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug  8 15:41:42.784 2011 (UTC - 4:00)
System Uptime: 0 days 14:22:27.688
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!memset+7ad7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+7ad7
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 25 16:29:08.211 2011 (UTC - 4:00)
System Uptime: 1 days 13:26:01.225
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 03:01:20.961 2011 (UTC - 4:00)
System Uptime: 2 days 8:20:37.014
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** WARNING: Unable to verify timestamp for storport.sys
*** ERROR: Module load completed but symbols could not be loaded for storport.sys
Probably caused by : usbehci.sys ( usbehci+6901 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WinSAT.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_usbehci+6901
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 15 09:23:50.002 2011 (UTC - 4:00)
System Uptime: 1 days 23:58:27.405
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jul 12 20:30:28.888 2011 (UTC - 4:00)
System Uptime: 2 days 4:29:49.798
Probably caused by : fltmgr.sys ( fltmgr!FltpPassThrough+37c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!FltpPassThrough+37c
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 16 12:44:35.033 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:27.436
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
FAILURE_BUCKET_ID:  X64_0x50_nt!PoIdle+52a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wrecked · 17 Aug 2011

Thank you for the suggestions.

I ran all of the tests available from the Seatools and it didn't find any errors.
I ran several iterations of MemTest86+ and the Windows Memory Diagnostic Tool and it didn't find any errors.
I ran the Prime95 torture tests for an hour on each test, and it didn't return any errors.

To top it all off, it crashed shortly after completing all of those tests. I've attached that specific dmp file, I apologize if this is improper.

Jonathan_King · 19 Aug 2011

What is the make/model of your PSU? Also, is there a chance you have access to another motherboard to test out?

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Aug 17 20:38:49.801 2011 (UTC - 4:00)
System Uptime: 0 days 4:47:38.204
Probably caused by : win32k.sys ( win32k!RawInputThread+9b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!RawInputThread+9b0
BiosReleaseDate = 09/28/2007
SystemProductName = XFX Nforce 680i LT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wrecked · 20 Aug 2011

I have a RocketFish RF-550WPS.

No, I don't have another motherboard to try unless I go buy one.

Jonathan_King · 21 Aug 2011

If you had to buy one piece of electronics to try to resolve this, I would have to recommend a new PSU first. Any chance you could sell your current one and get a little something back at least?

I'd recommend this one: Newegg.com - CORSAIR Enthusiast Series TX650 V2 650W ATX12V v2.31/ EPS12V v2.92 80 PLUS BRONZE Certified Active PFC High Performance Power Supply

Or this one if you don't mind spending $10 extra: Newegg.com - CORSAIR Enthusiast Series TX750 V2 750W ATX12V v2.31/ EPS12V v2.92 80 PLUS BRONZE Certified Active PFC High Performance Power Supply

I can't guarantee that it will solve the problem, I'll be straight up. We're at a stage where all our diagnostics have failed, and the only thing left to do is replace components until we find the culprit. The PSU is my first guess, but motherboard and RAM also wouldn't surprise me.

wrecked · 21 Aug 2011

Thank you for the advice.

After your question, I thought I knew what you were getting at. I searched for some PSU calculators and saw that my 550 watts may not be up to the task. I got this CORSAIR Gaming Series GS700 700W ATX12V v2.3 80 PLUS Certified Active PFC High Performance Power Supply PSU yesterday from a local retailer. (I earn my keep on my home PC and can't have it up and down). I've ran a bunch of load tests on it and can't get it to fail. That doesn't prove anything though. I couldn't reliably get it to fail before.

I've also been working with various applications and what not open simultaneously. No failures. I'll consider it solved if it doesn't fail in a week or so. (I was getting a couple of failures a day during my normal operation).

Jonathan_King · 21 Aug 2011

That's a very good PSU; in addition to being of sufficient wattage, it is a reliable brand. With a cheap PSU, even though it may claim to provide a certain wattage, the capacitors are unreliable and may still cause BSODs or even damage hardware.

Let's wait and see, hopefully that cures the problem!