Frequent BSOD's, can't find a clear pattern. dump attached

wikke · 09 Jan 2012

Hi there crash experts.

Have been encountering pretty random BSOD's on a family PC.
Can't find a clear pattern in behavior which would lead to this happening.
Would you mind taking a look?
I'm out of ideas and analyzing BSOD's is definitely not one of my greatests strenghts

This is my first time posting here.
Let me know if there is something not right.
Or if you need more info; I'll comply asap.

Specs

- Desktop PC put together 1,5 years ago (Never was fully stable.. but never came around to research). OS dates from same time.
- Windows 7 x64 Ultimate Retail
- ASUS M4A87TD/USB3 (latest BIOS v2001 [03-08-2011]
- 2 GB GEIL DDR3 Ram 1333mhz (tried first with 2x2GB, crashed as well)
- Radeon HD 5570 (Latest amd vision driver 11.12)
- 60GB Corsair CSSD-F60GB2 SSD (AHCI mode)
- and an internal 1TB Samsung HD
- sweex wifi pci card

Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML attached
Keep in mind driver verifier was enabled in this dump.

I'm actually quite curious what the problem would be

Kind regards,
wikke

zigzag3143 · 09 Jan 2012

Probably caused by : hardware ( hidusb!HumInternalIoctl+70)

Something (human Interface device) USB Does it happen in safe mode?

Can you run a system file check to verify (and/or repair) the OS

Run a system file check to verify and repair your system files.

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end.

Read here for more information SFC /SCANNOW Command - System File Checker

wikke · 09 Jan 2012

Knowing if this happens in safe mode is hard to tell...
It's not my PC and it's not the mode people usually work in.

I have tried SFC /scannow however just the day before this BSOD happened.
File integrity was 100%, no errors found

zigzag3143 · 09 Jan 2012

wikke said:

Knowing if this happens in safe mode is hard to tell...
It's not my PC and it's not the mode people usually work in.

I have tried SFC /scannow however just the day before this BSOD happened.
File integrity was 100%, no errors found

Probably a driver. Run driver verifier to find out which one.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

wikke · 14 Jan 2012

Thanks for your help so far.

Since I enabled driver verifier, I had 2 more BSOD's over a couple of days (the pc isn't used intensively).

I attached the 2 minidumps and 2 jcgriff files I made some time after the PC crashed.

Let me know of you need more info.
Thanks,
wikke

wikke · 15 Jan 2012

2 more BSOD's today, check attachments for dumps.

in these two dumps, windbg !verifier points to atikmdag.sys

Anyone got a clue?

edit: in the previous it also mentioned a realtek wireless driver..I updated the wireless card to the latest driver I found..
Lets see what happens next

mgorman87 · 15 Jan 2012

First thing you need to do is disable driver verifier.

Next, I would like you to update your video card drivers.
Download the driver from here - ATI Radeon

Next, go into device manager and uninstall your video card. If there is an option to delete the drivers then select it.
Reboot the computer and when it boots back up install the new drivers.

Code:

AODDriver2.sys Wed Jun 15 04:38:35 2011 (4DF86F8B)

Remove AMD Overdrive for now to rule out an overclocking issues

Code:

netr28x.sys  Wed Feb 25 22:02:09 2009 (49A60631)

What is the make and model of your wireless LAN card? This driver needs to be updated as it was the cause of one of the crashes.

Once that's done, run some hardware tests

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 14:46:16.017 2012 (UTC - 5:00)
System Uptime: 0 days 0:16:00.765
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3b568e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x50_VRF_atikmdag+3b568e
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 04:15:48.593 2012 (UTC - 5:00)
System Uptime: 0 days 0:08:22.951
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : hardware ( atikmpag+8ecd )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_atikmpag.sys
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 11:29:35.012 2012 (UTC - 5:00)
System Uptime: 0 days 0:25:09.744
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys ( netr28x+17e7b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_netr28x+17e7b
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 11:53:58.927 2012 (UTC - 5:00)
System Uptime: 0 days 2:50:10.660
Probably caused by : ndis.sys ( ndis! ?? ::LNCPHCLB::`string'+67c2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_VRF_ndis!_??_::LNCPHCLB::_string_+67c2
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 07:46:20.145 2012 (UTC - 5:00)
System Uptime: 0 days 2:14:32.503
Probably caused by : hardware ( hidusb!HumInternalIoctl+70 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_hidusb.sys
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wikke · 03 Feb 2012

- I removed overdrive.
- Updated the wireless lan (some sweex card) with latest win7 drivers available on the site.
- Ran driver sweeper and removed the ATI GPU card

Then, I installed a borrowed Nvidia GPU card & installed latest X64 win7 drivers

It ran stable for 13 days, no BSOD's! (where it was elsewhere 1 per day).
So I started to think the original ATI card was borked.

Today, the PC gave a BSOD.. back to square one.

I attached the minidump.
What else can it be?
Next I will post resulsts of the prime and memtest

Seagate HD test is testing as we speak, strangely enough both drives (SSD + HD) are listed twice [edit: seems to be a widely known issue/bug].

mgorman87 · 03 Feb 2012

Disable driver verifier

This one blames your nividia drivers. Since both video cards have caused problems, you might be looking at either a bad motherboard or possibly overheating it the case isn't properly ventilated.

What type of PSU do you have?

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 08:31:38.640 2012 (UTC - 5:00)
System Uptime: 0 days 0:37:10.404
*** 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+2fecb )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_nvlddmkm+2fecb
BiosReleaseDate = 03/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wikke · 06 Feb 2012

I disabled Driver Verifier. Since then it has crashed some more.

PSU = CORSAIR CMPSU-650TX (650 W)
Its a fairly open case (ANTEC Three Hundred) with many fans.
I monitored the idle temps, which were excellent.

Also, the pc is only used lightly, for browsing, office tasks, youtube and so on.
So nothing at all like gaming which could warrant overheating.

I ran prime for about 1 hour today and it BSOD'd.
Probably caused by : netr28x.sys

Tomorrow I will remove this PCI wifi card and replace it with ethernet or a USB dongle.

Any ideas while I'm at it?