Multiple Win7 Pro BSOD's (0x1000007e, 0x00000024, 0x0000001e, ...)

[pichogve]

I have a custom build desktop that has been crashing (BSOD) almost every night for a while now.

The hardware and OS I have is this:

MB: ASUS P8Z68-V Pro (with latest BIOS v1101)
CPU: Intel i7-2600K (not overclocked)
RAM: 16GB (4 x Corsair 4Gx4 CMZ16GX3M4A1600C9)
Graphics: NVIDIA GeForce GTX470
HDD's: 2 x 1TB WD WD1002FAEX-00Y9A0 and 2 x 1TB Hitachi HDS721010KLA330)
RAID: all four 1TB HDD's are configured as RAID 10 using the integrated Intel RAID controller, using Intel RST v 10.8.0.1003

OS: Windows 7 Pro x64 OEM

The system is about 6 months old, and the OS install is only a few weeks old (I re-installed OS from scratch then).

A few other things I have done are:

1. Ran memtest86+ (only one pass, no errors).
2. I have Norton Internet Security 2012, SUPERAntiSpyware and MalwareBytes Anti-Malware installed, have run full scans with all 3 of them, no malware/virus found.
3. I use Norton Ghost 15.0 for daily backups to a NAS device.

I have attached info files as per "BSOD - Posting Instructions".

Any help is appreciated.

 

[zigzag3143]

Two issues

1- Symantec. Remove and replace

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows


2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

Re-install newest version

 

[pichogve]

Two issues

1- Symantec. Remove and replace

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows


2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

Re-install newest version

Thanks for the reply. I have uninstalled all Norton products I had installed (NIS 2012 and Ghost 15.0). I installed MSE and re-instaled the Intel RST (iaStor.sys) latest driver version 10.8.0.1003.

 

[zigzag3143]

Two issues

1- Symantec. Remove and replace

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows


2-Iastor.sys Related to iaStor.sys Intel Matrix Storage Manager driver - ia32.

Re-install newest version

Thanks for the reply. I have uninstalled all Norton products I had installed (NIS 2012 and Ghost 15.0). I installed MSE and re-instaled the Intel RST (iaStor.sys) latest driver version 10.8.0.1003.

Good luck

 

[pichogve]

Had one more crash last night, here is the output from BlueScreen View:

==================================================
Dump File : 021012-14476-01.dmp
Crash Time : 2/10/2012 3:43:16 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`04e6a9c9
Parameter 3 : fffff880`04107e88
Parameter 4 : fffff880`041076e0
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+21f21
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : USBPORT.SYS+249c9
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021012-14476-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 303,794
==================================================

and I have also attached the dump file.

Another thing I have done since the last time I posted is, I ran memtest86+ v4.2 and it completed 6 passes with no errors.

 

[JMH]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have raid > update its Driver.


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[pichogve]

Here is an update.

I ran memtest86+ v4.2 (booting from CD) for about 13 hours or so, it completed 6 passes and there where no errors reported.

I am going to try verifier as you suggested.

Thanks again for the help.

 

[pichogve]

I forgot to mention before, I am not overclocking.

And during the weekend I also ran diagnostics to all my hard drives just to make sure they were OK. For my Hitachi drives I ran the long test using Hitachi's Drive Fitness Test v4.16 and for my WD drives I ran the long test using Seagate's SeaTools v2.23. All tests ran with no errors.

 

[JMH]

Thank you for reporting back.
Good luck!

 

[zigzag3143]

Good news on Memtest. Driver verifier?

 

[pichogve]

Good news on Memtest. Driver verifier?

Hi zigzag, I have my system running with driver verifier enabled as per the instructions right now, I am just waiting for the next crash, I will report then.

 

[JMH]

Thank you.
We wait patiently...

 

[pichogve]

My system crashed again this evening, here is the new dump file (attached).

I also think I can reproduce the crash, following this steps:

1. Start "Beyond Compare" program.
2. Run a folder sync copy from NAS device to D: drive (system crashes as soon as copy starts).

My "D:" partition is a partition located in a RAID 1 volume (Intel RAID), that RAID 1 volume consists of my two WD drives.

 

[pichogve]

I spoke too soon, the steps I listed before don't reproduce the crash after all.

 

[zigzag3143]

My system crashed again this evening, here is the new dump file (attached).

I also think I can reproduce the crash, following this steps:

1. Start "Beyond Compare" program.
2. Run a folder sync copy from NAS device to D: drive (system crashes as soon as copy starts).

My "D:" partition is a partition located in a RAID 1 volume (Intel RAID), that RAID 1 volume consists of my two WD drives.

The most recent crash was Related to athur.sys CB42/CB43/MB42/MB43 Network Adapter from Atheros Communications, Inc.


I would re-install the newest version available.

 

[pichogve]

I have reinstalled athur.sys driver as suggested (and actually that driver is for a USB wireless card that I don't use, so I even disconnected the adapter for now).

I also had two more crashes (see attached files).

The first one happened at the same time I opened Intel Rapid Store Technology software, and the second crash happened right after the system rebooted from the first crash (as soon as a logged in to Windows). Both crashes happened before I was able to update the athur.sys driver and disconnect my USB wireless card).

 

[JMH]

> Your most recent crash log is fairly inconclusive pointing vaguely to hardware.
{ ie your CD-rom, perhaps a driver?}

> Please run SFC {Option 2 }

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

> I would also suggest this driver be updated or removed.
sxuptp.sys (from 2007)

{Related to sxuptp.sys SXUPTP Driver for Windows XP from silex technology, Inc.}

 

[pichogve]

Hello again,

sfc /scannow ran with no errors ("Windows Resource Protection did not find any integrity violations.").

I uninstalled the sxuptp.sys, you are correct that is an old driver for a Belkin network print server (they never released Win 7 specific drivers for it). I am pretty sure my system was crashing even before I installed that driver.

I am with you in your comment about this being a hardware issue, I am just not sure which hardware. So far I have tested RAM and disk drives and no issues there. I have also tested the processor with Intel's Processor Diagnostic Tool and no problems there either. I don't know of any good programs to run motherboard tests. Right now I have decided to run my system, just with my boot disk (SSD), I have disconnected my four HDD's and my DVD drive, to try and eliminate some of the hardware.

By the way, I had two more crashes this morning (see attached files). The two crashes were before I removed the sxuptp.sys driver and before I removed my HDD's and DVD drive.

Thanks again for the help.

 

[zigzag3143]

Driver verified and Related to sxuptp.sys SXUPTP Driver for Windows XP from silex technology, Inc.. Yours is from 2007.

Now that it is verified it needs to be updated or removed.

As to why it didnt crash before and does now....

Crashes are always a combination of things. That driver might have gotten along with everything else on your system for months, but then something changed (could have been anything you installed, removed, or changed) and not that driver is mis-behaving.

 

[pichogve]

Hi zigzag, yes I agree with you ... like I mentioned on my previous post, I have removed the sxuptp.sys driver from my system.