Guest RET.SSgt.Haterade=US= Posted January 1, 2011 Share Posted January 1, 2011 So I've updated all my drivers and I've run tests on my RAM, processor, and my hard disks. Everything comes out clean, but I'm still getting blue screens. The blue screens are more or less random, but it seems that I most often get them I'm watching video from my hard disk, although the videos are housed on a different partition than my windows folder; or when I'm simply surfing the web; or sitting in TS without any game running. Sometimes I will experience a general system slowdown and lag which does not end in a blue screen, but the system will not speed back up until I restart my computer. What's most frustrating is that I've never experienced a blue screen when I either render video or play BC2, the two most resource intensive things I put my computer through. Here are the logs for the five most recent blue screens: ================================================== Dump File : 010111-16130-01.dmp Crash Time : 1/1/2011 11:37:44 AM Bug Check String : Bug Check Code : 0x00000101 Parameter 1 : 00000000`00000019 Parameter 2 : 00000000`00000000 Parameter 3 : fffff880`009b2180 Parameter 4 : 00000000`00000004 Caused By Driver : ndis.sys Caused By Address : ndis.sys+a980 File Description : Product Name : Company : File Version : Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\010111-16130-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== ================================================== Dump File : 123110-16130-01.dmp Crash Time : 12/31/2010 11:01:32 PM Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL Bug Check Code : 0x000000d1 Parameter 1 : fffff880`0381ec80 Parameter 2 : 00000000`00000002 Parameter 3 : 00000000`00000001 Parameter 4 : fffff880`014594b3 Caused By Driver : iaStor.sys Caused By Address : iaStor.sys+2b4b3 File Description : Product Name : Company : File Version : Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\123110-16130-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== ================================================== Dump File : 123110-15412-01.dmp Crash Time : 12/31/2010 3:19:40 PM Bug Check String : Bug Check Code : 0x00000124 Parameter 1 : 00000000`00000000 Parameter 2 : fffffa80`062408f8 Parameter 3 : 00000000`00000000 Parameter 4 : 00000000`00000000 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+4a587c File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.1.7600.16617 (win7_gdr.100618-1621) Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\123110-15412-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== ================================================== Dump File : 122910-18532-01.dmp Crash Time : 12/29/2010 10:36:06 AM Bug Check String : MACHINE_CHECK_EXCEPTION Bug Check Code : 0x0000009c Parameter 1 : 00000000`00000000 Parameter 2 : fffff880`03379c70 Parameter 3 : 00000000`00000000 Parameter 4 : 00000000`00000000 Caused By Driver : hal.dll Caused By Address : hal.dll+126e0 File Description : Product Name : Company : File Version : Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\122910-18532-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== ================================================== Dump File : 122510-15880-01.dmp Crash Time : 12/25/2010 7:52:28 PM Bug Check String : Bug Check Code : 0x00000101 Parameter 1 : 00000000`00000019 Parameter 2 : 00000000`00000000 Parameter 3 : fffff880`03164180 Parameter 4 : 00000000`00000002 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+70740 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.1.7600.16617 (win7_gdr.100618-1621) Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\122510-15880-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== This post is a continuation of the following thread: [url]http://clanunknownsoldiers.com/barracks/showthread.php?14659-Driver-download-help[/url]. Link to comment Share on other sites More sharing options...
Guest RastaGanja Posted January 1, 2011 Share Posted January 1, 2011 Alright honestly, i don't know if you would be having the same issue but when i had my cp built they "accidentally" gave me a version of windows 7 that was bad so i had to get another copy. I DO NOT KNOW if this is your situation just a little help from my experience with blue screen. It was really weird though...i wouldn't freak out just keep it in your head as a last resort. Which the bad version of windows..made my entire system unstable but since i got the new version haven't had one blue screen problem since :D Link to comment Share on other sites More sharing options...
Guest RET.CDR.CrAzY_NuTtA=US= Posted January 1, 2011 Share Posted January 1, 2011 You tried anything simple like a system restore back to before the problems started? Link to comment Share on other sites More sharing options...
Guest RET.SSgt.Haterade=US= Posted January 1, 2011 Share Posted January 1, 2011 [quote='SPC.RastaGanja=US=','http://clanunknownsoldiers.com/hq/thread/?postID=79170#post79170']Alright honestly, i don't know if you would be having the same issue but when i had my cp built they "accidentally" gave me a version of windows 7 that was bad so i had to get another copy. I DO NOT KNOW if this is your situation just a little help from my experience with blue screen. It was really weird though...i wouldn't freak out just keep it in your head as a last resort. Which the bad version of windows..made my entire system unstable but since i got the new version haven't had one blue screen problem since :D[/QUOTE] I'm using Windows 7 Ultimate Edition. [quote='RET.CrAzY_NuTtA=US=','http://clanunknownsoldiers.com/hq/thread/?postID=79171#post79171']You tried anything simple like a system restore back to before the problems started?[/QUOTE] Unfortunately, I bought the computer after market, so it doesn't have a restore disk. In a last-ditch effort, I may buy one from HP (the maker of my computer). I would normally roll it back to a previous date, but somehow the system restore got turned off. By the time I realized this and reengaged the system restore, I had already begun to have the issues. Link to comment Share on other sites More sharing options...
Guest RastaGanja Posted January 1, 2011 Share Posted January 1, 2011 strange haterade mine was windows 7 ultimate !!!! might wanna check it out...hmm ill look up some winds7 issues if i can and ill get back to you. Link to comment Share on other sites More sharing options...
Guest MAJ.Kaossilator=US= Posted January 1, 2011 Share Posted January 1, 2011 I know Iastor.sys is tied to the Intel raid drivers, which can get a bit borked even when you aren't using a raid setup. The [URL='http://downloadmirror.intel.com/19607/eng/iata_enu.exe']latest x58 chipset drivers are here[/URL]. Beyond that, this is starting to sound like it could also be a temperature issue. Do you have any software you use to monitor cpu temp? If not, [URL='http://www.alcpu.com/CoreTemp/Core-Temp-setup.exe']THIS[/URL] is a pretty quick 'n dirty monitoring app that'll get you a good bead on where your cpu is during these problems. I know it sounds silly in the face of not having these issues during game-play or rendering, but have you dusted out your machine? In general, most 0x00000101 STOP errors are due to a processor issue of some sort. I'm sorta confused why it isn't specifically calling it a WATCHDOG timeout since that's usually what a 101 stop is so it could still be something else and it's confounding Windows. The long and short is you have a multi-core cpu where one core is trying to get another core to execute some command and it gets deadlocked or hung. Potentially that deadlock occurred before Windows could capture the source of the conflict, which is why I'm thinking there is no WATCHDOG being called. **EDIT: In addition, basically all of those events are pointing to a hardware issue. 101 as I said is typically cpu related either with temp, voltage issues, overclocking conflicts, or drivers. 9c on hal.dll (hal.dll is basically windows generic driver managing layer) is very directly a hardware issue. 9c is hardware, and hal.dll is drivers, which is where iastor.sys comes in... intel rapid storage drivers could be at the root of all of this. Just to do full disclosure here... [URL='http://carrona.org/bsod.html']carrona.org[/URL] is a fantastic resource for anyone wishing to perform diagnoses. It takes your troubleshooting game up a few notches once you get used to their site :) Can't recommend it enough, but then again I'm sort of a Windows tier 1/2 junky.... might help me find a job if I actually got my MCITP though. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.