Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

random bsod: intel rst-e drivers and ssds on x79

This is a discussion on random bsod: intel rst-e drivers and ssds on x79 within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Getting weekly or so bsods, each with a different message, on an x79 windows 7 x64 sp1 system with two


Closed Thread
 
Thread Tools Search this Thread
Old 02-01-2012, 08:42 PM   #1
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



Getting weekly or so bsods, each with a different message, on an x79 windows 7 x64 sp1 system with two samsung 830 ssds in a raid 1 config using the latest version of the intel rst-e (RST enterprise) drivers. memtest86+ shows no errors in 64gb after several passes. So: it looks like I have almost exactly the same issue described in this thread:
http://www.techsupportforum.com/forums/f299/solved-first-bsod-625822.html

--BUT I'd like to know
1) if analysis of my minidump files (attached) is consistent with buggy Intel rst-e drivers, and if there are any other suggestions or comments. (fwiw, the intel rst-e team will NOT speak to customers directly or accept bug reports from them, although the rst team will--odd. so i'm my own for debugging this.)

2) if I switch to native microsoft 7 software raid 1, is there any problem with setting that up on the system drive (C drive), or are there any "surprises" compared to using the intel raid system?

Thanks.
Attached Files
File Type: zip Minidump.zip (80.9 KB, 5 views)

__________________
techuser2 is offline  
Old 02-02-2012, 12:29 AM   #2
Team Manager, Microsoft Support
Microsoft MVP
BSOD Kernel Dump Expert
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 30,681
OS: Windows 10, 8.1, 7 + Windbg :)



Hi -

3 BSODs; 3 different bugchecks = indicative of hardware failure

Results were inconclusive at best.

See if Driver Verifier flags any 3rd party drivers -

Driver Verifier - Windows 7 & Vista (BSOD-related)

Driver Verifier needs to run 24 hours minimum or until it BSODs your system, whichever is less. Then . . .

Provide full system info - Blue Screen of Death (BSOD) Posting Instructions - Windows 7 & Vista

Also, run Speccy - http://www.filehippo.com/download_speccy
- "File" | "Publish Snapshot" | Paste URL into your next post

Regards. . .

jcgriff2

`



BSOD SUMMARY
Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\013112-25100-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 31 06:39:37.083 2012 (GMT-5)
System Uptime: 7 days 15:22:04.173
Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`010051d1 fffff880`0d6a1d00 00000000`00000000
BiosVersion = 0906
BiosReleaseDate = 12/22/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3200
CurrentSpeed: 3201
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012312-25443-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 15:15:01.476 2012 (GMT-5)
System Uptime: 1 days 17:34:54.319
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTryUnwaitThread+28
Bugcheck code 0000000A
Arguments 00000000`05420040 00000000`00000002 00000000`00000001 fffff800`060d9e38
BiosVersion = 0906
BiosReleaseDate = 12/22/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3200
CurrentSpeed: 3201
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012112-25365-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 21:37:49.184 2012 (GMT-5)
System Uptime: 1 days 17:03:35.416
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`05c8f9a0
BiosVersion = 0906
BiosReleaseDate = 12/22/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3200
CurrentSpeed: 3201
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  

by jcgriff2     
             
         J. C. Griffith, Microsoft MVP   
             
           https://mvp.support.microsoft.com/profile/Griffith   


           www.sysnative.com
             
           www.jcgriff2.com 


จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ


  

jcgriff2 is offline  
Old 02-02-2012, 11:50 AM   #3
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



Thank you for taking the time to analyze those files. I also have the full kernel dump files but they're huge files (gb or two). I can't run driver verifier for a couple of weeks or so (I can't risk causing a bsod on the pc over this time) but promise to post back later after I can run it.

I've run practically every ram test out there and many times, so I think I can exclude memory. I think either the samsung 830 ssds or the intel rste is probably the cause, but I can't say tech support was much help; samsung is inclined to blame intel, and intel is inclined to blame the oem. I'm still waiting to hear back from the motherboard maker (asus); at least they asked for the minidump files. Of course, it's really my fault for buying the cutting edge--that last beta stage, RTM, is always the best and most important one.

In the meantime I've rolled back to a super-old version of intel rste, so if no BSODs appear over the next couple of weeks, that will be significant.
__________________
techuser2 is offline  
Old 02-03-2012, 03:36 AM   #4
Team Manager, Microsoft Support
Microsoft MVP
BSOD Kernel Dump Expert
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 30,681
OS: Windows 10, 8.1, 7 + Windbg :)



I've seen too many BSODs involving SSDs.

Be sure to check for SSD firmware upgrades.
jcgriff2 is offline  
Old 02-05-2012, 10:44 PM   #5
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



thanks, I already had the latest firmware on the ssds (btw, that's an incredible pain to upgrade if you are using raid, since the firmware upgrade only sees non-raid drives). I'm hoping my reversion to a very old intel rste, one closer to the orom date, will solve things (though I can't see why the intel orom date should matter--I thought the orom basically only does things in preboot environment and then gets out of the way).
__________________
techuser2 is offline  
Old 02-05-2012, 11:11 PM   #6
Team Manager, Microsoft Support
Microsoft MVP
BSOD Kernel Dump Expert
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 30,681
OS: Windows 10, 8.1, 7 + Windbg :)



No SSD here yet because of the many BSODs I've worked on, so I honestly can't answer your question.

When SSDs 1st appeared as the cause of BSODs, RMA was the only option. Since then, the SSD manufacturers have recommended firmware upgrades. Some OPs have reported success.
jcgriff2 is offline  
Old 02-19-2012, 03:17 PM   #7
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



Though it's still a bit early to say, it looks like I may have found the cause: the logmein mirror driver. Others have also reported random bsods in windows 7 in January 2012 from the logmein mirror driver. (It's not enough to uninstall the program via control panel, but one must uninstall the mirror driver separately from device manager using right-click uninstall).

I'll update here once I get further confirmation. I had discovered the very old intel rste drivers didn't solve the issue, but so far removing the logmein mirror driver is solving it for me.

However, I note in passing that intel seems to have completely removed the rste 3.0.1.x (3.0.1.7016) drivers from its website, and the newest available are now only the 3.0.0.3020. To be cautious, I'm staying only with the released and unretracted rste drivers.
__________________
techuser2 is offline  
Old 02-20-2012, 04:03 AM   #8
Team Manager, Microsoft Support
Microsoft MVP
BSOD Kernel Dump Expert
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 30,681
OS: Windows 10, 8.1, 7 + Windbg :)



You have the latest version of LogMeIn...?
jcgriff2 is offline  
Old 02-21-2012, 12:25 AM   #9
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



Yes, and it's apparently a problem introduced with an update in 2012.
__________________
techuser2 is offline  
Old 02-25-2012, 12:41 AM   #10
Team Manager, Microsoft Support
Microsoft MVP
BSOD Kernel Dump Expert
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 30,681
OS: Windows 10, 8.1, 7 + Windbg :)



Do you happen to know the name of the driver + timestamp?

I've got several on file -

http://www.sysnative.com/drivers/driver.php?id=lmimirr.dll
http://www.sysnative.com/drivers/driver.php?id=lmimirr2.dll
http://www.sysnative.com/drivers/driver.php?id=lmimirr.sys


And others - CTRL+F logmein - http://www.sysnative.com/drivers/table/

Thanks!

jcgriff2

`
jcgriff2 is offline  
Old 02-26-2012, 07:07 PM   #11
Registered Member
 
Join Date: Feb 2012
Posts: 6
OS: win7 x64 sp1



I don't, as I already removed it, but it was the most recent logmein driver in January through February 19, 2012. One caveat is that it occurred only on the x79 systems, and they, unlike the other pcs, also had nvidia gtx 570 and 580 cards. So the cause may have been an interaction with x79 or with nvidia, but definitely removing the logmein driver solved the problem. If you google bsod and logmein, you'll see a couple of posts from others in Jan 2012.

__________________
techuser2 is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Getting Random BSOD
Hello everyone, Win 7 x64 Ultimate ASUS Crosshair IV formula (latest BOIS Rev 1304, and BIOS defaults loaded) AMD Phenom II X6 1100T @ 3.3GHz G.Skill DDR3 1333 8GB(2x4GB) 2x AMD Radeon 6950's in CF Enermax Revolution 85+ 1020W PSU 2x C300 Crucial SSD's in RAID 0 (OS installed) 1x WD 750GB
4fuzzyID10T BSOD, App Crashes And Hangs 4 05-22-2011 08:37 AM
Intel finds flaw in Sandy Bridge chipsets, halts shipments
Intel finds flaw in Sandy Bridge chipsets, halts shipments - The Tech Report As phenomenal as Intel's new Sandy Bridge processors turned out to be, nothing in this world is truly perfect. Intel announced earlier this morning that it has discovered a flaw in the 6-series chipsets that accompany...
JMPC Motherboards, Bios & CPU 2 01-31-2011 04:17 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2


All times are GMT -7. The time now is 10:56 PM.


Copyright 2001 - 2014, Tech Support Forum

Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts