BSOD troubleshooting assistance sought

lightair · 08 May 2011

Esteemed Counselors,

This is a new system experiencing repeated and seemingly random bsods. For instance, it will blue screen while sitting idle. I replaced the c: drive, installed win7 64-bit, updated the bios and all drivers to the very latest as far as I can ascertain. I ran memtest86+, dskchk, dcp latency checker and all looked good. The computer is offline so no antivirus. I disabled the network and onboard audio, since they aren't needed, in hopes of clearing up any irq conflicts. IRQs look odd to me with many devices sharing the same number. But I haven't looked at IRQs since back in Win98 days, so it may be normal. I did move my PCI-based sound card to a different slot. I also removed my UAD-1 dsp card (pci). but these adjustments led to no noticeable change in stability.

i also ran WhoCrashed 3.01 which pointed to NT kernel issues, specifically with ntoskrnl.exe and ntkrnlmp.exe. I haven't used this utility before so I'm taking this with a grain of salt.

intel desktop utility indicates that everything is getting enough voltage.

I've attached bsod dump and SHR.

Thanks in advance for any suggestions.

Win7 Home Premium 64bit OEM SP1
Core2 Duo E6750 @ 2.66 GHz
intel DP35DP mobo
gigabyte GeForce 8600GT
4GB Corsair DDR2
RME Hammerfall Multiface

lightair · 08 May 2011

I forgot to mention: a system scan appeared to verify everything except a corrupt OmdBase.dll which couldn't be repaired. I could upload a sfcdetails.txt if that'd be helpful.

Thanks.

usasma · 08 May 2011

Memory dumps usually are caused by these things (in this order):
- 3rd party drivers/malware
- compatibility (on newly released OS's - it is less likely the longer that the OS has been out)
- hardware problems
- Windows problems.

4 memory dumps - all from 07 May 2011
3 different BSOD error codes
3 different causes blamed (FYI - ntkrnlmp.exe and ntoskrnl.exe are the core of the OS. So if they are having problems, it's likely that you'll have many more problems other than the occasional BSOD)
The different codes and causes generally suggest a hardware problem, although it can also be compatibilty/malware/lower level drivers issues.

So, we start with reviewing the reports that you've submitted.

systeminfo.txt shows that you only have 1 update after Service Pack 1. Please visit Windows Update as there are additional updates available after Service Pack 1.

The perfmon.html report and MSINFO32.nfo both show that these 2 devices are disabled:

High Definition Audio Device HDAUDIO\FUNC_01&VEN_8384&DEV_7627&SUBSYS_80863001&REV_1002\4&3415AEAC&0&0201 This device is disabled.

Intel(R) 82566DC-2 Gigabit Network Connection PCI\VEN_8086&DEV_294C&SUBSYS_00018086&REV_02\3&2B8E0B4B&0&C8 This device is disabled.

Are the drivers installed for these devices? Even if disabled, the drivers are necessary.

Next we look at the installed drivers that were present in the memory dumps. Please note the 2 that are marked in RED below. Please follow the instructions below to update/remove the older drivers:
OLDER 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 update these 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:


iaStorV.sys     Thu Jun 10 20:46:19 2010 (4C11875B)
hdsp_64.sys     Thu Aug 05 08:36:53 2010 (4C5AB065)
iaStor.sys      Wed Mar 03 21:51:31 2010 (4B8F2033)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA) - Windows Update will handle this if an update is available
osaio.sys       Wed Feb 14 04:20:09 2007 (45D2D449)
dump_iaStor.sys Wed Mar 03 21:51:31 2010 (4B8F2033) - Windows will update this after you update iaStor.sys
synusb64.sys    Fri Jun 26 09:30:11 2009 (4A44CD63)
HECIx64.sys     Fri May 11 22:00:20 2007 (46451FB4)
nvlddmkm.sys    Sat Oct 16 13:12:46 2010 (4CB9DD0E)
nvBridge.kmd    Sat Oct 16 13:06:16 2010 (4CB9DB88)

http://www.carrona.org/dvrref.html#iaStorV.sys
http://www.carrona.org/dvrref.html#iaStor.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#osaio.sys
http://www.carrona.org/dvrref.html#dump_iaStor.sys
http://www.carrona.org/dvrref.html#synusb64.sys
http://www.carrona.org/dvrref.html#HECIx64.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#nvBridge.kmd

After all this is done, please test for further BSOD's. If they still continue, I'd first suggest removing and reconnecting all parts in the system (connection problems are the biggest problems that I have when assembling computers). Once that's done, post back and we'll suggest some other hardware tests.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 22:53:45.201 2011 (UTC - 4:00)
System Uptime: 0 days 1:35:06.654
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
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02895565 00000000`00000000 ffffffff`ffffffff
BiosVersion = DPP3510J.86A.0572.2009.0715.2346
BiosReleaseDate = 07/15/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 21:04:39.726 2011 (UTC - 4:00)
System Uptime: 0 days 2:00:07.179
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
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`028ce565 00000000`00000000 ffffffff`ffffffff
BiosVersion = DPP3510J.86A.0572.2009.0715.2346
BiosReleaseDate = 07/15/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 19:00:52.608 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:20.061
BugCheck D1, {fffffa8103b6d1a0, 2, 0, fffff880014523f7}
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+c7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeProcessCompletedRequests+c7
Bugcheck code 000000D1
Arguments fffffa81`03b6d1a0 00000000`00000002 00000000`00000000 fffff880`014523f7
BiosVersion = DPP3510J.86A.0572.2009.0715.2346
BiosReleaseDate = 07/15/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 18:52:04.556 2011 (UTC - 4:00)
System Uptime: 0 days 0:30:36.009
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiRestoreTransitionPte+c8
Bugcheck code 0000000A
Arguments ffffea80`03f1f090 00000000`00000002 00000000`00000000 fffff800`02885f88
BiosVersion = DPP3510J.86A.0572.2009.0715.2346
BiosReleaseDate = 07/15/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

lightair · 08 May 2011

Ouch, my reply from six hours ago has disappeared.

I greatly appreciate your help. Yes, both drivers were updated before the devices were disabled. I wasn't able to locate more recent drivers for the two red drivers (Intel utilities) and synusb64.sys (for a webcam -- completely unnecessary). What method should I use to uninstall/get rid of these? The two nvidia drivers and the hdsp_64 are the latest available. I completely trust the RME driver; it's not causing the problems. But if the nvidia drivers are causing problems I would likely need to replace the graphics card.

Also, your warning about the driver directory came after I replaced the OmdBase.dll instances with one from the installation disc.

Thanks again.

lightair · 08 May 2011

I've installed the drivers indicated to replace the iastor and iastorv. I also got the machine online and ran windows update, checked all the physical connections and reseated everything except the cpu. At this point, the crashes are so persistent that it's become impossible to accomplish anything. And they're all over the map.

I'm not particularly knowledgeable, but it is now feeling like an intermittent hardware failure that's becoming increasingly less intermittent.

I'd be most grateful for further thoughts and advice.

usasma · 09 May 2011

Hardware problems are likely, but the lower level Intel drivers (such as the HECIx64.sys) can also cause this.
Try this package to update the HECIx64.sys driver: http://downloadcenter.intel.com/Deta...ce%22&lang=eng

As for the osaio.sys - uninstall the Intel Desktop Utility(ies) and test. Here's a link for the latest version if you decide to reinstall it: http://downloadcenter.intel.com/Deta...ility&lang=eng

Please upload the latest memory dumps. They're located in C:\Windows\Minidump

Here's a list of a bunch of hardware testing utilties - just start at the top and work your way down:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - ÐœÐ˜Ð NVIDIA / Ð£Ñ‚Ð¸Ð»Ð¸Ñ‚Ñ‹ / VMT
Artifact Locator - ÐœÐ˜Ð NVIDIA / Ð£Ñ‚Ð¸Ð»Ð¸Ñ‚Ñ‹ / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

Good luck!

lightair · 09 May 2011

Thank you so much!

I'd love your opinion on the following. I ran memtest86+ last week with 2 and 4 memory modules with no errors. I'm running it again now but I'm beginning to think that it is moot whether this is a hardware or a driver problem. The two intel links you listed won't solve the problem. The Management Engine I already tried to install last week and got the message "This operating system is not supported. the installer will now close." And the Utilities package is the very place the out-of-date utility drivers came from in the first place. This and the fact that hecix64 could cause these issues makes me conclude that Intel is not supporting Windows 7 on this three year old motherboard.

Thanks for the list of stress tests! If the system passed these tests do you think it might be stable in WinXP? I had the same problems previously in XP but I was missing important drivers. Unfortunately I'm attempting to rebuild my audio system around software that requires win7 but I would sadly sacrifice the new software to have a running system.

Please advise as I'm not able to purchase a new cpu, motherboard, graphics card, and memory right now.

usasma · 09 May 2011

The most likely problem here is a hardware problem. Run the stress tests and we'll have a better idea of what's what with the system. Unfortunately the only sure "test" for a bad mobo is to try another one.

The tests that we suggest will test your hard drive, RAM, video card, and some other memory and controllers - but that's nowhere near all of your hardware. So, you could pass all of the stress tests/diagnostics and still have problems.

My best guess is that XP wouldn't be stable either (since I think this is a hardware problem) - but there is a chance that XP could be more stable just because it doesn't use as many advanced features as Win7. You're going to have to try it to see.

Good luck!

lightair · 12 May 2011

Passed memtest86+ and the HD diagnostics. Can't run any of the others as the computer can't run Windows for any length of time without crashing. In addition, FurMark doesn't support 64-bit environment.

So, it would appear to be the motherboard, graphics card, or related drivers. I'm prepared to leave it at that unless you know of a means of troubleshooting the graphics card that doesn't require windows. Knoppix perhaps?

usasma · 14 May 2011

Although FurMark doesn't support the 64 bit environment, it still stresses your video card.

Get a video card from a place that will refund your money if you don't need it. Then try the new card and see if it helps - if it doesn't, return the card and get your money back.