My build is an AW9D-Max mobo, Intel e6600 cpu, 2x1gig Curcial Ballistix Ram, WD Raptor X 150gig HD (non-raid) used for Windows XP Pro SP2 and programs, 2x Samsung Spinpoint P 250gig drives in Raid 0 array, Evga geForce 7900 GTO, 2x samsung dvd-ram r/w drives, Abit uguru panel and digital doc5+ panel. Built about one month ago, been adding software, programs, periphs and generally getting things tidy since then.
However, since I reinstalled Windows (about 2 weeks ago) in order to install Intel Matrix drivers using F6 method, my system has been hanging after the BIOS loads and Windows boots (after the windows splash screen with the progress bar) but before Windows actually loads and can be used. The "hang" time lasts between 10 and 30 seconds, but usually at 15 secs or so. This has been after I reinstalled Windows to install the Intel Matrix drivers so as to use RAID (but not for my Raptor boot harddrive, which is NOT part of my RAID array). I did not get this problem before initialising RAID and installing these drivers (although I had other problems resulting from not having proper drivers installed, which I resolved through OS reinstall with F6 process).
What happened was two days ago I installed a Canon MP printer driver. Since then, I've had one Blue Screen Of Death per day (e.g., 2 BSOD's total). So, trying to figure this out (looking strongly like bad Canon drivers) with an Stop Code of 100000d1 (DRV-IRQ), I read to check my Event Log for clues.
So, I went into Event Log and looked under system errors and saw the once daily System Error for BSOD, but also saw a recurring error for an "iaStor" error, logged with event id of 9. These errors occurred each and every time I booted the computer, with between 2 and 5 errors each time (must time out, then retry). When clicking on the errors, it says "The device, \Device\Ide\iaStor0, did not respond within the timeout period." I assume iaStor meant the Intel Matrix drivers since I became familiar with this driver when had problems with my F6 driver install upon Windows reinstall. My raptor is plugged into SATA 1, while the Samsungs are plugged into SATA 3 and 4, but not sure if the system treats them like 0, 2 and 3, respectively, but likely since iaStor is a Intel driver, no?
Well, anyway, is this the problem - with the intel drivers? I thought so, but I rolled back the drivers all the way to version 5.0.0.1032 (which matches the Intel Option ROM version burned into BIOS). The current, updated driver is 6.2.0.2002, and the mobo shipped with disks for driver 6.0.0.1022. Each of these resulted in the same multiple iaStor errors upon boot, as did interim drivers 5.7.0.1011 and 5.1.0.1022, I've now tried them all, each with 3 or 4 boots for consistency and always get the hang time at windows load and iaStor error in the Event Log. So I've gone back through the 5 most recent drivers and still have this iaStor error problem.
So now I think maybe it wasn't the drivers but something else? But these iaStor errors are the only errors I'm seeing in the log (other than rare system error), so it doesn't look like anything else is triggering them. These iaStor errors also predate my system erros/BSOD's and occur even without any other errors. Any ideas? The hang time at windwos load is irritating at up to 30 seconds AFTER the windows splash/scroll screen finishes.
I was also thinking maybe a cable malfunction, but this wouldn't be limited only to boot, would it? Meaning I would still have these errors while running the system, say web surfing or opening and using photo editing programs, gaming, etc., correct? But my event log doesn't show these errors other than at boot.
BTW, the computer works once past the windows load, but I'm angry since my new PC with fancy conroe e6600 and ddr2 ram is officially slower to boot than my dell with p4 socket 478 chip dinosaur, each with windows xp pro. Help!
Curt J.
However, since I reinstalled Windows (about 2 weeks ago) in order to install Intel Matrix drivers using F6 method, my system has been hanging after the BIOS loads and Windows boots (after the windows splash screen with the progress bar) but before Windows actually loads and can be used. The "hang" time lasts between 10 and 30 seconds, but usually at 15 secs or so. This has been after I reinstalled Windows to install the Intel Matrix drivers so as to use RAID (but not for my Raptor boot harddrive, which is NOT part of my RAID array). I did not get this problem before initialising RAID and installing these drivers (although I had other problems resulting from not having proper drivers installed, which I resolved through OS reinstall with F6 process).
What happened was two days ago I installed a Canon MP printer driver. Since then, I've had one Blue Screen Of Death per day (e.g., 2 BSOD's total). So, trying to figure this out (looking strongly like bad Canon drivers) with an Stop Code of 100000d1 (DRV-IRQ), I read to check my Event Log for clues.
So, I went into Event Log and looked under system errors and saw the once daily System Error for BSOD, but also saw a recurring error for an "iaStor" error, logged with event id of 9. These errors occurred each and every time I booted the computer, with between 2 and 5 errors each time (must time out, then retry). When clicking on the errors, it says "The device, \Device\Ide\iaStor0, did not respond within the timeout period." I assume iaStor meant the Intel Matrix drivers since I became familiar with this driver when had problems with my F6 driver install upon Windows reinstall. My raptor is plugged into SATA 1, while the Samsungs are plugged into SATA 3 and 4, but not sure if the system treats them like 0, 2 and 3, respectively, but likely since iaStor is a Intel driver, no?
Well, anyway, is this the problem - with the intel drivers? I thought so, but I rolled back the drivers all the way to version 5.0.0.1032 (which matches the Intel Option ROM version burned into BIOS). The current, updated driver is 6.2.0.2002, and the mobo shipped with disks for driver 6.0.0.1022. Each of these resulted in the same multiple iaStor errors upon boot, as did interim drivers 5.7.0.1011 and 5.1.0.1022, I've now tried them all, each with 3 or 4 boots for consistency and always get the hang time at windows load and iaStor error in the Event Log. So I've gone back through the 5 most recent drivers and still have this iaStor error problem.
So now I think maybe it wasn't the drivers but something else? But these iaStor errors are the only errors I'm seeing in the log (other than rare system error), so it doesn't look like anything else is triggering them. These iaStor errors also predate my system erros/BSOD's and occur even without any other errors. Any ideas? The hang time at windwos load is irritating at up to 30 seconds AFTER the windows splash/scroll screen finishes.
I was also thinking maybe a cable malfunction, but this wouldn't be limited only to boot, would it? Meaning I would still have these errors while running the system, say web surfing or opening and using photo editing programs, gaming, etc., correct? But my event log doesn't show these errors other than at boot.
BTW, the computer works once past the windows load, but I'm angry since my new PC with fancy conroe e6600 and ddr2 ram is officially slower to boot than my dell with p4 socket 478 chip dinosaur, each with windows xp pro. Help!
Curt J.
Facebook
Twitter