Windows 7: Seemingly random BSODs

gkl · 20 Mar 2011

For a while I've been having some seemingly random BSODs with my new Windows 7 Hope Premium install. I did have a severe problem with them a while ago but a reformat seemed to help. Unfortunately BSODs seem to have been returned albeit not as bad as with my previous installation (I guess it is a driver or hardware problem). I have to idea how to tackle this problem so any help is appreciated.

Basic info:
Windows 7 Home Premium x64. OEM but bought and installed by myself. Hardware could be approx. 6 months old. Installation age could be about 3 months or so, not sure about this.

I have attached the necessary info files as noted in the sticky.

edit
Hardware specs are as follows:
AMD Phenom II x4 965
ASUS M4A87TD EVO
Kingston 4GB RAM
Nvidia GeForce 460 1GB
Seagate 1TB HDD
Corsair 500W PSU

No overclocks.

Jonathan_King · 20 Mar 2011

Hello,

I wonder if OnlineArmor is the cause here; uninstall it completely and see what happens. Use Microsoft Security Essentials as a temporary or permanent alternative.

Install updated Realtek ethernet drivers from here: Realtek

Code:

Rt64win7.sys    Sun May 30 23:46:43 2010 (4C033123)

I found this error:

Code:

Event[3567]:
  Log Name: System
  Source: Disk
  Date: 2011-03-13T19:42:24.796
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: gLietotajs-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.

While I doubt it has much significance, it won't hurt to run a hard drive diagnostic; do the Short and Long DSTs in SeaTools.

If the BSODs persist, run driver verifier: Driver Verifier - Enable and Disable

...Summary of the dumps:

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Mar 20 06:07:30.782 2011 (UTC - 4:00)
System Uptime: 0 days 0:24:40.374
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_win32k!FreeObject+58
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 16 14:03:05.566 2011 (UTC - 4:00)
System Uptime: 0 days 2:04:19.784
Probably caused by : win32k.sys ( win32k!draw_clrt_nf_ntb_o_to_temp_start+7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  oaui.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!draw_clrt_nf_ntb_o_to_temp_start+7b
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Mar 14 13:00:54.464 2011 (UTC - 4:00)
System Uptime: 0 days 1:38:33.681
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  uTorrent.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar  4 04:24:13.041 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:54.633
Probably caused by : memory_corruption ( nt!MiGetPreviousNode+3c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetPreviousNode+3c
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar  4 04:20:45.787 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:42.379
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar  3 10:55:57.908 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:42.500
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+1f32 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xD1_usbohci+1f32
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Feb 27 07:27:01.517 2011 (UTC - 4:00)
System Uptime: 0 days 2:38:47.109
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+181 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Feb 26 04:21:43.384 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:34.601
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  oasrv.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 16:25:15.638 2011 (UTC - 4:00)
System Uptime: 0 days 5:20:18.402
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 11:03:56.333 2011 (UTC - 4:00)
System Uptime: 0 days 4:09:57.707
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b3
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

gkl · 20 Mar 2011

Thank you for the reply. I will uninstall OnlineArmor. I'm already using MSE though. Will install the Realtek drivers.
Regarding SeaTools, I think I already ran the tests and they found nothing. I'll run them again though.

gkl · 21 Mar 2011

I tried the Driver Verifier and it caused BSODs upon boot so I had to disable it via Safe Mode. How can I find the, I guess, driver causing it?

Jonathan_King · 21 Mar 2011

You might try selecting only about 3 or 4 drivers in Driver Verifier, and if you don't hang on boot, try the next 4, etc.

gkl · 22 Mar 2011

It seems that the BSOD upon booting was caused by usbfilter.sys. Without it being verified but every other 3rd party driver selected Windows boots just fine. I proceeded in removing it using a guide found on this forum. Let's hope this works.

Jonathan_King · 22 Mar 2011

usbfilter.sys is a Windows driver required to run USB devices; removing it is only a Band-Aid fix to a different issue. Do you have any USB devices attached? If so, try removing them, and then run Driver Verifier on that driver.

gkl · 03 Apr 2011

I reinstalled it and will do some testing. So far I removed my external soundcard and it still failed the test, same with my mouse. My external hard drive also seems to have no impact. The situation with BSODs seemed to improve after the uninstall actually, but just now it has become worse and I'm seeing behavior that I haven't experienced before.
First, I get freezes (only solution was hitting reset) and crashes (BSOD) while gaming which so far wasn't common at all - it would crash only after a session. Second, today I got a Red Screen of Death - any significant difference between it and a standard BSOD? Third, after hitting reset, a few times my BIOS settings got cleared which I though was unusual. I'm running almost the latest version of BIOS by the way, and will update it to 1 version later one (it doesn't seem to have anything relevant in its changelog though). And fourth, I've experienced freezes while being in BIOS which required resetting.

Could this be a hardware problem? RAM? Motherboard? CPU? PSU?

I think I will run Memtest. I recall running it before without any specific errors, but maybe I didn't run it long enough.

EDIT
Also, I've been experiencing it for some time but didn't find it too annoying, but sometimes the boot procedure would halt upon displaying "Detecting USB controllers..." message (1st screen), sometimes at a flashing cursor right before the Windows boot animation screen, but sometimes - while displaying Starting Windows but the animation not appearing at all. If I recall correctly, most of the time it happens when booting cold, eg, after being switched off for a night. Reset makes it boot just fine though.

EDIT #2
Actually, now that I think about it again, it think the Memtest performed some time ago did give some errors after approx. 16h. It happened with 1 stick which I suspected to be faulty and I tried other RAM sticks from a different PC, which runs fine, and I still got BSODs. And the supposedly faulty stick didn't cause BSODs on two different PCs either. So after reformatting and reinstalling Windows everything ran very well and for some reason I dismissed thing finding...

Jonathan_King · 04 Apr 2011

If you are having freezes in the BIOS, we can completely rule out software troubles; we are left with hardware and firmware. Go ahead and flash the latest BIOS; even if nothing important was changed, simply writing a fresh copy *sometimes* does the trick.

What happens if you disable the onboard USB controller in the BIOS? That may help us here; be aware that you will not have any USB access unless you have an expansion card.

gkl · 05 Apr 2011

Attached a PS2 keyboard and mouse and disabled at first the USB3 controller - still crashed upon booting Windows - and then the regular USB controller - Windows boots just fine. Also, lately a game that I play frequently has been crashing via a lockup + looping sound (after a couple of minutes of play which has never happened before) followed by numerous booting attempts and disappearing BIOS settings, but after disabling USB I get a regular BSOD and Windows is booting just fine after a reset.

Should I consider getting a new motherboard?

And I did run Memtest86+ - after 12 hours and approx. 12 passes it reported no errors.

Edit
starting to get freezes in windows. After reset PC doesn't boot - monitor in standby, mouse and keyboard are off. But power led and fans are still on.

Windows 7: Seemingly random BSODs

Seemingly random BSODs problems?