Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

0x1000007e BSOD (maybe RAID related?)


  • Please log in to reply
10 replies to this topic

#1 pichogve

pichogve

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 08 February 2012 - 08:50 AM

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

The hardware 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

I have run BlueScreenView and here is the output:

==================================================
Dump File : 020812-21871-01.dmp
Crash Time : 2/8/2012 7:45:25 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`01217e58
Parameter 3 : fffff880`03f567b8
Parameter 4 : fffff880`03f56010
Caused By Driver : iaStor.sys
Caused By Address : iaStor.sys+df9c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : iaStor.sys+de58
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020812-21871-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 293,576
==================================================

==================================================
Dump File : 020712-23290-01.dmp
Crash Time : 2/7/2012 6:43:01 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`05f95aa9
Parameter 3 : fffff880`03b787e8
Parameter 4 : fffff880`03b78040
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+180202
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : usbhub.sys+1aa9
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020712-23290-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 293,544
==================================================

==================================================
Dump File : 020412-24991-01.dmp
Crash Time : 2/4/2012 7:13:55 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`0d493058
Parameter 3 : fffff880`0d4928b0
Parameter 4 : fffff800`032cd04c
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+5a88
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020412-24991-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 290,712
==================================================

Any suggestions?

Thanks

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:56 PM

Posted 08 February 2012 - 09:00 AM

Given the varied nature of the errors and the fact that iastor.sys is one of the targets, I would not be surprised if your problem is caused by malware.

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:56 PM

Posted 08 February 2012 - 11:47 AM

Why is the oldest BSOD reflected in your submission...only 3 days old?

No BSODs prior to that? If not, what changed?

Louis

#4 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 08 February 2012 - 11:50 AM

Hi Allan,

It is possible that I haven't found malware, I am running Norton Internet Security 2012, and I have run full scans with Superantispyware and Malwarebytes Anti-malware (both latest versions and latest updates) , and none of them found anything.

#5 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:56 PM

Posted 08 February 2012 - 12:21 PM

Okay, may not be malware - especially since we're not talking about constant bsod's. But they ARE varied - each is different and each identifies a different file. Luis asks a good question - anything new?

Might as well try the obvious stuff.

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

Then you can run diagnostics on the HD's.

If you were getting the bsod's more frequently - or more consistently - they would be easier to diagnose.

#6 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 08 February 2012 - 03:04 PM

Why is the oldest BSOD reflected in your submission...only 3 days old?

No BSODs prior to that? If not, what changed?

Louis


That was my mistake Louis, I ran CCleaner about 3 days ago and deleted older dumps

#7 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 08 February 2012 - 03:16 PM

Okay, may not be malware - especially since we're not talking about constant bsod's. But they ARE varied - each is different and each identifies a different file. Luis asks a good question - anything new?

Might as well try the obvious stuff.

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

Then you can run diagnostics on the HD's.

If you were getting the bsod's more frequently - or more consistently - they would be easier to diagnose.


I have tried memtest86+, but only one pass, and didn't get any errors. I was thinking on letting it run overnight tonight and see what happens, will post about that in the morning.

I will also try the HD diags.

Thanks

#8 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 08 February 2012 - 03:37 PM

I was able to recover two mure dumps from backups from before I cleaned with CCleaner, here is their BlueScreen View output:

==================================================
Dump File : 012712-19453-01.dmp
Crash Time : 1/27/2012 7:34:34 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02e85f4b
Parameter 3 : fffff880`03bfd7c8
Parameter 4 : fffff880`03bfd020
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f4b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+71f4b
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012712-19453-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 284,808
==================================================

==================================================
Dump File : 012712-20295-01.dmp
Crash Time : 1/27/2012 6:34:20 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`00b99760
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012712-20295-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 293,512
==================================================

#9 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 09 February 2012 - 08:39 AM

Just a quick update, I ran memtest86+ v4.2 last night, 6 completed passes with zero errors.

I will do the hard drives checks today.

#10 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:06:56 PM

Posted 09 February 2012 - 12:44 PM

Run Driver Verifier - see if it flags any 3rd party drivers -

http://sysnative.com/0x1/Driver_Verifier.htm

Also, one bugcheck = 0x24 and listed ntfs.sys

Run HDD diags - SeaTools for DOS, LONG test - http://www.techsupportforum.com/2828431-post7.html

Regards. . .

jcgriff2

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#11 pichogve

pichogve
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:05:56 PM

Posted 10 February 2012 - 08:47 AM

Here is an update, yesterday I enabled Driver Verifier, I have attached the output of the "verifier /query" command.

I also tried to run the latest SeaTools DOS, and the program crashed while I was running the LONG test on my first drive.

And I also had one more crash last night, here is the summary from BlueScreen View (and I attached a copy of the dump file):

==================================================
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
==================================================

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users