Windows 7: Computer keeps on getting random BSODs and ´freezing´

FinDude · 02 Feb 2012

Hey,

I`ve started having very strange and very serious bsod-problems and weird freezes last fall. I tried everything from re-installing all drivers and the whole OS (I even changed it to XP). When I tried driververifier.exe the whole rig went berserk. Finally I could`t even install xp without getting a bsod. Resetting BIOS would´t work either, so I sent the mobo and the processor back to the retailer, but they could´t find any problem with them and they sent the parts back to me. When I reassembled the parts the computer started working again and I haven´t had any problems with it... Untill now..

This time I´ve reinstalled Win 7, updated it, installed all the latest drivers, did a full virusscan with avast! (found Athena2.exe infection in my Acronics backup folder--> deleted the folder and reinstated OS)l. No help... I still keep getting the same old freezes and BSODs, which say something about a fatal error and system protection, but no error code.

System help report said the following (freely translated, because my OS is in Finnish):
"Could´t detect antivirus program... etc. etc. etc...." --> nobrainer with avast!

This was interesting:
"A high stopcount per processor detected. This computer has 4 processor and 6 "webcards" (meaning wlan-card and the integrated ethernet-card I think). Total computer stopcount per second is 31590. Average stopcount per processor is 7898." And the counts from the processor drop-down menu were: "Average = 31,590 ; Smallest value = 14,167 ; Highest value = 376,585."

Please help me solve this! My rig cost me a fortune and I´m a university student so I really can´t afford a new one!

FinDude · 02 Feb 2012

Dump file added

usasma · 02 Feb 2012

Only one memory dump included in the upload.

I believe that the TP-LINK 150Mbps Wireless N Adapter is a USB device. Windows 7 doesn't like wireless USB devices, especially when using older drivers. It will spit out BSOD's rapidly if this is the case.
Here's my rant about these devices:

Quote:

I do not recommend using wireless USB devices. Especially in Windows 7 systems.
These wireless USB devices have many issues with Windows 7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Windows 7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Because of the history that you describe, please run these free hardware diagnostics (start with the Memory Test): Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


jraid.sys        Mon Jan 11 06:28:18 2010 (4B4B0B52)
vsflt53.sys      Tue Apr 12 07:31:35 2011 (4DA43817)
amdsata.sys      Wed Oct 07 16:13:09 2009 (4ACCF655)
amdxata.sys      Wed Oct 07 16:13:10 2009 (4ACCF656)
vididr.sys       Tue Apr 12 07:31:24 2011 (4DA4380C)
timntr.sys       Thu Jul 29 13:29:24 2010 (4C51BA74)
AtiPcie.sys      Tue May 05 11:00:22 2009 (4A005486)
aswMonFlt.sys    Mon Nov 28 12:52:10 2011 (4ED3CA4A)
snapman.sys      Wed Mar 09 08:22:38 2011 (4D777F1E)
aswRdr.SYS       Mon Nov 28 12:52:20 2011 (4ED3CA54)
CLBUDF.SYS       Wed Oct 07 02:42:23 2009 (4ACC384F)
athrx.sys        Tue Nov 23 19:11:58 2010 (4CEC584E)
nusb3hub.sys     Thu Jan 21 22:22:18 2010 (4B5919EA)
aswTdi.SYS       Mon Nov 28 12:52:18 2011 (4ED3CA52)
aswSnx.SYS       Mon Nov 28 12:54:05 2011 (4ED3CABD)
CLBStor.SYS      Wed Oct 07 02:42:27 2009 (4ACC3853)
nusb3xhc.sys     Thu Jan 21 22:22:21 2010 (4B5919ED)
aswSP.SYS        Mon Nov 28 12:53:57 2011 (4ED3CAB5)
AsIO.sys         Thu Apr 22 07:18:03 2010 (4BD0306B)
Rt64win7.sys     Thu Mar 04 08:42:52 2010 (4B8FB8DC)
aswFsBlk.SYS     Mon Nov 28 12:51:52 2011 (4ED3CA38)
nvhda64v.sys     Thu Jul 07 12:21:14 2011 (4E15DCFA)
dump_amdsata.sys Wed Oct 07 16:13:09 2009 (4ACCF655)
000.fcl          Fri Sep 26 09:11:22 2008 (48DCDF7A)
GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
nvlddmkm.sys     Sat Oct 15 02:07:55 2011 (4E99233B)
usbfilter.sys    Wed Oct 07 03:44:08 2009 (4ACC46C8)
ASACPI.sys       Wed Jul 15 23:31:29 2009 (4A5E9F11)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020212-18158-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb  2 06:15:24.795 2012 (UTC - 5:00)
System Uptime: 0 days 0:32:16.356
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46485 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iPodService.ex
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000
BiosVersion = 2301   
BiosReleaseDate = 07/18/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

FinDude · 03 Feb 2012

[QUOTE=usasma;1776781]Only one memory dump included in the upload.

What do you mean? Did I fail to upload something from the dump file?

I believe that the TP-LINK 150Mbps Wireless N Adapter is a USB device. Windows 7 doesn't like wireless USB devices, especially when using older drivers. It will spit out BSOD's rapidly if this is the case.
Here's my rant about these devices:

Quote:

I do not recommend using wireless USB devices. Especially in Windows 7 systems.
These wireless USB devices have many issues with Windows 7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Windows 7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

As I wrote it down on my system specs: It is a PCI-device (the box says adaptor, but it´s a PCI-card

Because of the history that you describe, please run these free hardware diagnostics (start with the Memory Test): Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Can you tell me which driver? Is it the nVidia driver or something else, coz it´s kinda hard to know which driver to update or downgrade, if I don´t whats causing the problem?

- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


jraid.sys        Mon Jan 11 06:28:18 2010 (4B4B0B52)
vsflt53.sys      Tue Apr 12 07:31:35 2011 (4DA43817)
amdsata.sys      Wed Oct 07 16:13:09 2009 (4ACCF655)
amdxata.sys      Wed Oct 07 16:13:10 2009 (4ACCF656)
vididr.sys       Tue Apr 12 07:31:24 2011 (4DA4380C)
timntr.sys       Thu Jul 29 13:29:24 2010 (4C51BA74)
AtiPcie.sys      Tue May 05 11:00:22 2009 (4A005486)
aswMonFlt.sys    Mon Nov 28 12:52:10 2011 (4ED3CA4A)
snapman.sys      Wed Mar 09 08:22:38 2011 (4D777F1E)
aswRdr.SYS       Mon Nov 28 12:52:20 2011 (4ED3CA54)
CLBUDF.SYS       Wed Oct 07 02:42:23 2009 (4ACC384F)
athrx.sys        Tue Nov 23 19:11:58 2010 (4CEC584E)
nusb3hub.sys     Thu Jan 21 22:22:18 2010 (4B5919EA)
aswTdi.SYS       Mon Nov 28 12:52:18 2011 (4ED3CA52)
aswSnx.SYS       Mon Nov 28 12:54:05 2011 (4ED3CABD)
CLBStor.SYS      Wed Oct 07 02:42:27 2009 (4ACC3853)
nusb3xhc.sys     Thu Jan 21 22:22:21 2010 (4B5919ED)
aswSP.SYS        Mon Nov 28 12:53:57 2011 (4ED3CAB5)
AsIO.sys         Thu Apr 22 07:18:03 2010 (4BD0306B)
Rt64win7.sys     Thu Mar 04 08:42:52 2010 (4B8FB8DC)
aswFsBlk.SYS     Mon Nov 28 12:51:52 2011 (4ED3CA38)
nvhda64v.sys     Thu Jul 07 12:21:14 2011 (4E15DCFA)
dump_amdsata.sys Wed Oct 07 16:13:09 2009 (4ACCF655)
000.fcl          Fri Sep 26 09:11:22 2008 (48DCDF7A)
GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
nvlddmkm.sys     Sat Oct 15 02:07:55 2011 (4E99233B)
usbfilter.sys    Wed Oct 07 03:44:08 2009 (4ACC46C8)
ASACPI.sys       Wed Jul 15 23:31:29 2009 (4A5E9F11)

usasma · 03 Feb 2012

No, you didn't forget to upload something.
Only 1 memory dump may indicate several things - such as the crashes happening at a low-level that Windows doesn't recognize, that you're using a disk cleaning application that's removing the memory dumps, that the settings for creating the minidumps have changed, that other corruptions have occurred which prevent Windows from capturing the memory dumps, or several other reasons.

I understand that the TP-Link adapter is a PCI device and not a USB device

The ntkrnlmp.exe file did crash - but that doesn't tell us what actually caused it to crash. This file is the kernel (core) of the operating system. If it were the problem there would be many problems with your system, not just the occasional BSOD.

The history that you describe, the lack of memory dumps (which may suggest a hardware problem), and the error itself (which can be caused by hardware problem) all tend to suggest a hardware problem to me.

Then, this latest memory dump is different from the previous one. When this happens a lot (different memory dumps), it's suggestive of a hardware problem (also can be caused by compatibility issues, low-level driver problems, or even malware).

I'm unable to locate information on the stopcount stuff that you cited in your first post. I suspect that it's due to differences in wording of the translation. Most references that I've found to stopcounts relate to hard drives - so that seems to make hardware diagnostics a reasonable suggestion.

Where did you get the information on the stopcount stuff? If it was in the perfmon /report, please save that report, zip it up, and upload it with your next post.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020312-15100-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 01:19:29.929 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:19.505
BugCheck D1, {0, 2, 8, 0}
*** 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+33c803 )
PROCESS_NAME:  System
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+33c803
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
BiosVersion = 2301   
BiosReleaseDate = 07/18/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

FinDude · 03 Feb 2012

Sorry didn `t realize to save the report the first time. Can I retrive it from some kind of archive?
I did a new performance check (attached), but it didn´t give any results about the CPU stops. I attached a sniping tool-image with explanatory text added, about where the stopcount-info came from.
Really do hope you "get the picture" even though it´s in Finnish.

I ran the memtest86 4.0a for two hours and four passes: no errors. Plus I don´t think it´s an memory issue, bacause I´ve ran the test for over six hours in the past and it came out clean.
I wasn't able to run the WD DataRecovery Diagnostics, it just said "no drive found. error code 0120"
I´ll run the rest of the tests and post back with the results.

FinDude · 03 Feb 2012

I ran the FurMark test (15 min at 1080p), Stability test, HotCPU test (all tests for ca. 15min) and the prime95 test (ca. 1,5h) no errors or complains what so ever, so the memory and the cpu don´t seem to be completely rotten. I´m thinking it´s is just a driver/compatibility issue rather than the hardware (cpu and memory had been running for over a year without any problems). Although hard drive problem isn`t ruled out yeat..

I attached the FurMark and HotCpu test results on to this post.

usasma · 03 Feb 2012

You'll have to run a hard drive test. Try the Seagate SeaTools test. If that doesn't recognize the hard drive, then download either the Seagate or the Western Digital diagnostics for Windows and try them from within Windows.

I didn't attach too much importance to the stopcount stuff when I first read it. But as we worked on your issues, it came to concern me - and the majority of the concern comes from Google searches for "stopcount" that mostly relate to hard drive problems.

Computer reports are similar no matter what language they're in (that's how I figured that it came from perfmon /report) - so I can usually puzzle my way through most of them. And, if the online translators let me down, I can always ask you for a translation! :0)

Finally, it's possible that that problem only occurred around the time that you ran the first perfmon /report - so it's not unusual that it didn't show up in this one.

FinDude · 03 Feb 2012

I tried runnig the WesternDigital test, but it didn`t detect my hard drive. Does this have something to do with the AHCI-mode set in BIOS?

usasma · 03 Feb 2012

I've heard of this problem (and some of the other techs where I work use that trick)
I just run the diagnostics within Windows (or in the PE environment).

Windows 7: Computer keeps on getting random BSODs and ´freezing´

Computer keeps on getting random BSODs and ´freezing´ problems?