Multiple BSOD, even after system rebuild

airtrons · 26 Apr 2011

I had a computer that was running stable with WXP. I upgraded to W7 x64, and started to have random BSOD. I ran all kinds of tests, and posted on this forum at some point. All pointed to a memory issue. I thus changed the hard drive, memory, motherboard and CPU. I kept the DVD drives, and the power supply.

Still, random BSOD... Ran tests on the memory (24 hrs) and all is well. I had ZoneAlarm; but did a clean removal (installed Kaspersky). All to no avail.

I attached the data dump. Interestingly, I'm unable to run the perfmon test - at some point my desktop just freeze. I'm still able to move the cursor about, but the desktop is unresponsive to any click.

Basic spec:
MSI mobo (using the onboard ATI HD 4250 video card)
AMD Ahtlon II X4 635, 2900 MHz
4Gb RAM
No problem devices in the hardware manager.

Thank you in advance for your time.

Jonathan_King · 27 Apr 2011

Hello,

I guess you're stuck with me again this time!

I'm seeing this error:

Code:

Event[2398]:
  Log Name: System
  Source: BTHUSB
  Date: 2011-04-16T20:41:27.118
  Event ID: 17
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rich-PC
  Description: 
The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

Is the Bluetooth adapter something you can physically remove from your PC, such as a PCI card or USB device? If so, please do. If not, go into the BIOS and disable the adapter.

What PSU do you have?

A good troubleshooting step would be to install XP again, to see if it really is a hardware problem.

...Summary of the dumps:

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr 26 19:14:54.351 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:15.943
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for msrpc.sys - 
*** 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
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wininit.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr 26 04:28:53.903 2011 (UTC - 4:00)
System Uptime: 0 days 5:42:47.495
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Apr 17 22:54:08.904 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:22.106
Probably caused by : ntkrnlmp.exe ( nt!RtlAppendUnicodeToString+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlAppendUnicodeToString+2a
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 10 13:07:06.035 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:53.861
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  9 23:57:34.470 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:58.296
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  wininit.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
SystemProductName = MS-7596
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

airtrons · 27 Apr 2011

Thank you Jonathan. I did remove the Bluetooth, it was a small USB dongle. No joy.

On one of the BSOD that didn't generate a dump, I saw that it was tcpip.sys that was being blamed. I use an ethernet cable to my router. I was previously using a USB WiFi adapter, and just removed it a while back - just to try something.

The PSU is a Corsair 850W, about 18 months old. All seems nominal at this point. I also remove the power and SATA cables to my DVD drives, just in case. Literally, the only thing left from my previous build is the PSU. I'm almost tempted to change it.

Unfortunately, re-installing WXP is not an option at this point for me. I need to get this W7 to work. Please note that at some point in the past few weeks, I ended up formating my new hard drive and re-installing W7 - just in case. No joy.

I attached the latest 2 dumps logged earlier this evening.

Cheers,
Rich

Jonathan_King · 28 Apr 2011

From the time you boot up your computer, how long would you expect it would take for a BSOD to occur?

You may try creating an Ubuntu CD and running off of that live, just to see if the BSODs occur there.

One of the hardest things in computer troubleshooting is when a replacement component is bad. When you replace something, you expect that it's good, and rule it out as a cause. However, it does happen from time to time, and when it does, it's the most hair-pulling situation you'll be in all year.

Let's run some hardware diagnostics with that in mind.

RAM - Test with Memtest86+

Run all three Prime95 tests for 2 hours each: https://www.sevenforums.com/tutorials...t-prime95.html

SeaTools for Windows | Seagate