BSOD Errors

[sawdust86]

Hi all,

Hoping you could help me out. I am having random BSOD errors ever since upgrading to 7 x64. I think the last one was a stop 1e and there are a few others that I can't quite remember right now but attached are my minidumps. My problem is my RAID 5 setup keeps having to rebuild after most crashes and it takes like 40 hours to do and its driving me crazy as I keep it for storage and have since lost about half the information I had on there (about 1tb of media). If anyone out there is able to tell me what is causing this and how to fix it I would be most appreciated. Keeping in mind everything has already passed extensive hardware tests and is a fresh 7 install.

My system Specs:

6 1TB HDD in Raid 5 on the built in mobo connections (Intel DP55WG) and my main OS on a 500GB HDD attached to a Sil3132 PCI-E raid controller card (my ODD is also attached to that).
Intel i7 860
Kingston 4gb (2x2gb kit) DDR3 (Has passed memory testing)
OCZ 1000W PSU
Nvidia 9600GT

 

[zigzag3143]

Hi all,

Hoping you could help me out. I am having random BSOD errors ever since upgrading to 7 x64. I think the last one was a stop 1e and there are a few others that I can't quite remember right now but attached are my minidumps. My problem is my RAID 5 setup keeps having to rebuild after most crashes and it takes like 40 hours to do and its driving me crazy as I keep it for storage and have since lost about half the information I had on there (about 1tb of media). If anyone out there is able to tell me what is causing this and how to fix it I would be most appreciated. Keeping in mind everything has already passed extensive hardware tests and is a fresh 7 install.

My system Specs:

6 1TB HDD in Raid 5 on the built in mobo connections (Intel DP55WG) and my main OS on a 500GB HDD attached to a Sil3132 PCI-E raid controller card (my ODD is also attached to that).
Intel i7 860
Kingston 4gb (2x2gb kit) DDR3 (Has passed memory testing)
OCZ 1000W PSU
Nvidia 9600GT

Hi and welcome SD

Probable causes

011010-45021-01.dmp    1/10/2010 9:01:58 PM    BUGCODE_USB_DRIVER    0x000000fe    00000000`00000005    fffffa80`0619c1a0    00000000`80863b3c    fffffa80`0664fc50    USBPORT.SYS    USBPORT.SYS+2de4e                    x64        C:\Users\K\Desktop\Minidump\011010-45021-01.dmp    8    15    7600    
011210-29265-01.dmp    1/12/2010 5:52:34 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    00000000`00000000    00000000`00000002    00000000`00000000    fffff800`02e7c625    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011210-29265-01.dmp    8    15    7600    
010510-58344-01.dmp    1/5/2010 10:32:14 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    fffff800`02ca7b74    00000000`00000000    ffffffff`ffffffff    Ntfs.sys    Ntfs.sys+b734                    x64        C:\Users\K\Desktop\Minidump\010510-58344-01.dmp    8    15    7600    
011110-42962-01.dmp    1/11/2010 7:58:30 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    tcpip.sys    tcpip.sys+6304e                    x64        C:\Users\K\Desktop\Minidump\011110-42962-01.dmp    8    15    7600    
011910-39171-01.dmp    1/19/2010 7:40:58 AM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    fffff800`01e9ab74    00000000`00000000    ffffffff`ffffffff    fltmgr.sys    fltmgr.sys+3c6ef                    x64        C:\Users\K\Desktop\Minidump\011910-39171-01.dmp    8    15    7600    
011210-46113-01.dmp    1/12/2010 2:14:58 PM    NTFS_FILE_SYSTEM    0x00000024    00000000`001904fb    fffff880`0a0ccb68    fffff880`0a0cc3c0    fffff800`02e99f14    Ntfs.sys    Ntfs.sys+213d8                    x64        C:\Users\K\Desktop\Minidump\011210-46113-01.dmp    8    15    7600    
011810-55395-01.dmp    1/18/2010 8:20:06 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff800`52ed1880    00000000`00000008    fffff800`52ed1880    00000000`00000005    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011810-55395-01.dmp    8    15    7600    
011410-55302-01.dmp    1/14/2010 9:37:06 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`031b2795    fffff880`06193190    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-55302-01.dmp    8    15    7600    
010810-37767-01.dmp    1/8/2010 5:14:36 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050033    00000000`000006f8    fffff800`96cbae80    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\010810-37767-01.dmp    8    15    7600    
010910-43711-01.dmp    1/9/2010 6:19:14 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050033    00000000`000006f8    fffff800`db59be80    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\010910-43711-01.dmp    8    15    7600    
011010-45131-01.dmp    1/10/2010 4:32:46 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050033    00000000`000006f8    fffff800`02cc8e90    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011010-45131-01.dmp    8    15    7600    
011710-55973-01.dmp    1/17/2010 7:23:48 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050033    00000000`000006f8    fffff800`02ebde90    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-55973-01.dmp    8    15    7600

As you can see there are several. In a situation like this you have to assume it is hardware. Win 7 doesnt like RAIDS, or 64bit overclocking.

We have 2 choices. the first more cautious but will take longer to diagnose. The second is more extreme and you should have a backup and win 7 dvd just in case.

First cautious
check ram download memtestx86 and run for 5 passes
check HS-- run chkdsk /F
run system file check to verify and repair system files
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP
Update raid driver

Even if it was a clean install you have OLD drivers. Maybe even raid driver is old these need updating

secdrv.SYS        fffff880`06fc1000    fffff880`06fcc000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
Si3132r5.sys        fffff880`01200000    fffff880`01255000    0x00055000    0x4660528c    6/1/2007 12:08:28 PM                        
SiWinAcc.sys        fffff880`01274000    fffff880`0127d000    0x00009000    0x4671d6fa    6/14/2007 7:02:02 PM                        
SiRemFil.sys        fffff880`01b64000    fffff880`01b6c000    0x00008000    0x46798312    6/20/2007 2:42:10 PM                        
SI3132.sys        fffff880`013a5000    fffff880`013bf000    0x0001a000    0x4703e1e1    10/3/2007 1:39:29 PM

If you want to go to the more risky option let me know when you have the backup complete

Ken J+

edit btw you oldest driver secdrv.sys
. One of those drivers is *secdrv.sys*, which is developed by Macrovision as part of SafeDisc. Which I assume is part of your RAID. that in itself might be the problem

pm me if you need help
KJ

 

[sawdust86]

Thanks for the quick response!

-Memtest has passed 10-15 ish times about 2-3 days ago
-Chkdsk has completed on my OS drive and I wasn't sure if it would be safe to run on my Raid 5 setup especially with it being as buggy as it has been.
-SFC checks found no errors
-Not overclocking
-The raid 5 driver was downloaded off of intel's site along with the matrix storage manager and should be the latest available. The Sil 3132 controller card was installed by windows updates and not sure if its the latest or not. (per trying to upate with windows it is)
- The secdrv.sys doesn't make sense to me that it has anything to do with my raid hardware as I though safedisc was for copy protection on games and such. I do have daemon tools installed and maybe it could have came from there?
- My backup is complete which I also did a few days ago just because of all the problems I have been having and I would definitely be interested in the risky option.

Thanks for all your time and efforts!
AB

 

[sawdust86]

Also had another BSOD over the night, here's the Minidump for it.

 

[usasma]

Don't worry overmuch about secdrv.sys. The 2006 version is in nearly every BSOD that I look at - so I presume it's not an issue because of that. I suspect that it's a component that Microsoft purchased from Macrovision - and that it doesn't need updating (which will happen through Windows Update).

Please notice the outdated drivers from this latest memory dump:

SI3132.sys   Wed Oct 03 14:39:29 2007
Si3132r5.sys Fri Jun 01 13:08:28 2007
SiRemFil.sys Wed Jun 20 15:42:10 2007
SiWinAcc.sys Thu Jun 14 20:02:02 2007

All SiS and all from before Win7 came out.
A quick visit to the SiS website (SiS - Welcom to Silicon Integrated Systems Corporation.) shows me that there's not any Win7 drivers for the SiS SATA/RAID controllers

I've seen several of these recently and I suspect that they are not fully compatible with Win7.
I would suggest disabling the SiS drivers to see if this solves your problem (be aware that this has caused boot issues for others).

To help avoid the boot issues, please make a System Restore point.
Then use this free tool to stop the SiS drivers from loading: Autoruns for Windows (select the Drivers tab then remove the checkmarks by the SiS drivers)

If it has difficulty booting, use your Win7 installation DVD to boot to System Repair - and then use RSTRUI.EXE from the Command Prompt to restore your system back to before the changes.

Please post back with your results as this will likely help others who are suffering from issues with the SiS drivers.

Here's a summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 22:53:07.650 2010 (GMT-5)
System Uptime: 0 days 15:12:55.368
BugCheck A, {fffffa0003a3cc10, 2, 0, fffff80001f37a8f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

 

[sawdust86]

Disabling the SiS drivers definitely didn't allow windows to load. It had a stop 7b error. Any other ideas? Know of any sata cards compatible with win 7?

 

[sawdust86]

Also had another BSOD

 

[usasma]

Well, at least you're able to boot back into Windows!

This BSOD is a STOP 0x3B in win32k.sys (from BlueScreenView)

I have a HighPoint RocketRAID 2640x4 that's Win7 compatible (and it cost me $150 US).

I've found Win7 drivers!!! Silicon Image - Support | Search Results

 

[sawdust86]

Thanks for the driver links! I updated the SiS card to the latest base bios and then told windows to install the latest driver for it. We'll see if its fixed or not now. Will post back in a day or so if I don't have any more problems.

Thanks for all your help!

 

[sawdust86]

And another BSOD....

and side note:
I ordered a new board off of newegg just because I'm sick of these problems. The only reason I have the intel board is because I got the board and CPU for really cheap off of intel retail edge. I made sure the new board has enough sata ports to do what I want to do. It would still be nice to know what caused this most recent bsod though.

 

[usasma]

I got a Retail Edge board when Vista first came out.
I'll never participate in the Retail Edge program again because of it.
Just too many problems with it.

This BSOD was a STOP 0x101: BSOD Index
Which means we're narrowing down on the hardware issues (but still don't have it "nailed").

Here's a post that describes the most common reasons for it: http://www.sevenforums.com/crashes-...lock-interrupt-bsod-101-error.html#post356791

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4

Also, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

SI3132.sys   Wed Oct 03 14:39:29 2007 - Silicone Image storage drivers ([URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image - Support[/URL])
Si3132r5.sys Fri Jun 01 13:08:28 2007 - Silicone Image storage drivers ([URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image - Support[/URL])
SiRemFil.sys Wed Jun 20 15:42:10 2007 - Silicone Image storage drivers ([URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image - Support[/URL])
SiWinAcc.sys Thu Jun 14 20:02:02 2007 - Silicone Image storage drivers ([URL="http://www.siliconimage.com/support/index.aspx"]Silicon Image - Support[/URL])

I still suspect these drivers as they claim to support Win7 - but the drivers are still dated previous to the release of Win7.

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 21 14:48:12.657 2010 (GMT-5)
System Uptime: 0 days 1:45:15.828
BugCheck 101, {19, 0, fffff880034fe180, 6}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  vlc.exe

 

[sawdust86]

two more...for anyone who's keeping track.

 

[usasma]

Let's give Driver Verifier a try. I don't know if it's gonna help, but it won't hurt if you run it according to these directions:

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 "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).

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 22 13:05:14.971 2010 (GMT-5)
System Uptime: 0 days 9:44:56.142
BugCheck 3B, {c0000005, fffff80003580627, fffff88007e29100, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  trillian.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 22 19:44:02.554 2010 (GMT-5)
System Uptime: 0 days 6:37:14.614
BugCheck 7F, {8, 80050033, 6f8, fffff80003270fe9}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe