Windows 7 BSODs, freezing, etc; tried reinstalling Win7, can't fix problems

dpritcht · Oct 6, 2012

I'm experiencing periods of weeks where I won't have a problem and then I can't got 2 mins without my computer going BSOD or freezing/locking up. Tried everything (I can think of) including updating the BIOS, reinstalling Win7, trying to troubleshoot different hardware components, nothing seems to do the trick. It sure seems like it's a driver or hardware issue and I'm ok with replacing parts...I just don't know what it is exactly. Seems like it could be the memory, the graphics card or even the MOBO...just not sure. Hoping that you can help! Attached troubleshooting files...let me know what else I can provide and thanks much in advance.

Dave

dpritcht · Oct 6, 2012

Attaching mini dump files as well.

usasma · Oct 6, 2012

Please run the file collection app again and let it finish.
You'll know it's finished when it tells you to zip up the files and post them on the website.
Your upload is missing several reports that I use when doing BSOD analysis.

Please update your USB 3.0 drivers from the system/motherboard manufacturer's website. The older versions (like yours) are known to cause BSOD's on some systems:
nusb3hub.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous issues w/BSOD's)
Link Removed

nusb3xhc.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous issues w/BSOD's)
Link Removed

Analysis:
The following is for information purposes only.

Code:

[font=lucida console]**************************Sat Oct  6 11:19:46.114 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100612-16083-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:00:17.614[/B]
BugCheck Code: [B]BugCheck 1A, {5002, fffff780c0000000, 461, ff00046afffffffe}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a041 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
BUGCHECK_STR:  0x1a_5002
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2a041[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  6 11:18:44.501 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100612-15740-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:13:20.001[/B]
BugCheck Code: [B]BugCheck 19, {22, 1e00000000000000, 0, 0}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72d6 )[/B]
BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
BUGCHECK_STR:  0x19_22
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x19_22_nt!_??_::FNODOBFM::_string_+72d6[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  5 05:03:42.502 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100512-15490-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 18:44:33.002[/B]
BugCheck Code: [B]BugCheck 19, {3, fffffa80039640e0, fffa80039640e0, fffffa80039640e0}[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+a53 )[/B]
BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]services.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x19_3_nt!ExDeferredFreePool+a53[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct  3 15:52:10.860 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100312-16224-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 5:33:03.000[/B]
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct  2 22:21:59.449 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100212-15475-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:35.949[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff80001dc69bc, fffff8800e8aa8a0, 0}[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+100 )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ExDeferredFreePool+100[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 22:08:22.785 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092712-15537-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:03:21.285[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck Code: [B]BugCheck 24, {1904fb, fffff8800eb2ed38, fffff8800eb2e590, fffff880012c8c04}[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsFindPrefix+114 )[/B]
BugCheck Info: [B]NTFS_FILE_SYSTEM (24)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID: [B]X64_0x24_Ntfs!NtfsFindPrefix+114[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 18:22:27.421 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092712-15584-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:22:15.921[/B]
BugCheck Code: [B]BugCheck 19, {3, fffff80001e51730, fff80001e51730, fffff80001e51730}[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+a53 )[/B]
BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]AnyDVDtray.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x19_3_nt!ExDeferredFreePool+a53[/B]
  BIOS Version                  1202   
  BIOS Release Date             02/17/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 22 18:37:20.327 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092212-15771-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 8:53:23.466[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff80001ce454b, 0, ffffffffffffffff}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+c7 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]GameOverlayUI.[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!SwapContext_PatchXRstor+c7[/B]
  BIOS Version                  1202   
  BIOS Release Date             02/17/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  6 11:19:46.114 2012 (UTC - 4:00)**************************
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Sat Oct  6 11:19:46.114 2012 (UTC - 4:00)**************************
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
viahduaa.sys                Tue Mar  2 06:30:18 2010 (4B8CF6CA)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nusb3hub.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
nusb3xhc.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
ElbyCDIO.sys                Thu Dec 16 17:58:13 2010 (4D0A9985)
point64.sys                 Wed May 18 04:07:20 2011 (4DD37E38)
usbfilter.sys               Fri Mar 30 23:48:56 2012 (4F767EA8)
Rt64win7.sys                Wed Apr 11 12:29:16 2012 (4F85B15C)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
AnyDVD.sys                  Sun Aug 26 08:56:20 2012 (503A1CF4)
nvlddmkm.sys                Thu Aug 30 11:50:16 2012 (503F8BB8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 22:08:22.785 2012 (UTC - 4:00)**************************
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 18:22:27.421 2012 (UTC - 4:00)**************************
AnyDVD.sys                  Tue May  1 19:35:22 2012 (4FA0733A)
[/font]

Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

dpritcht · Oct 6, 2012

Will do on the USB 3.0 driver. Sorry about the files...attached the new zip after I let the thing run entirely.

usasma · Oct 6, 2012

Thanks!

Only 97 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates.

You have 3 drives - what is the make, model and wattage of your power supply?

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

dpritcht · Oct 6, 2012

Thanks a ton John!! I will give all this a look and see what I can figure out. I actually had all these problems prior to the SSD and the more I read online, it sounds like many others have the same symptoms with the motherboard I've got - ASUS M487TD/USB3. The third HDD I have is actually and external that was plugged in when I ran all the diagnostics. I unplugged that external and continue to run into problems. Will review your email and give everything a try. Oh...and the power supply is an OCZ ModXStream 600W.

usasma · Oct 7, 2012

Just FYI - I've heard of memory problems with the M4 series of boards.
The recommendation was to NOT use the Auto setting in the BIOS
Instead it's recommended that you get the settings/timings/voltages from your memory manufacturer
and use those settings in the mobo BIOS.

Good luck!

Search

Navigation section

Windows 7 BSODs, freezing, etc; tried reinstalling Win7, can't fix problems

dpritcht

New Member

Attachments

usasma

dpritcht

New Member

Attachments

usasma

Fantastic Member

dpritcht

New Member

Attachments

usasma

Fantastic Member

dpritcht

New Member

usasma

Fantastic Member

Similar threads