Major BSOD, unsure of cause, possibly Intel SATA Controller? Please help!

G

GamEmpire

Hi All,

Bear with me, had this post go missing as I clicked submit before, so
retyping it to the best of my ability.

Up until last friday, my Shuttle SB75G2 was running fine.

Specs were:

3.0C Pentium 4
1024mb Corsair PC3200 XMS
SB75G2 will SFF Motherboard
(http://us.shuttle.com/specs2.asp?pro_id=388)
Built by ATI Radeon x800 Pro
NEC 3500A DVD+RW/-RW
2x 200gb Seagate 7200.7 SATA Drives in a RAID 1 Configuration

The SB75G2 is an 875 based motherboard. My issue last friday was a
trojan and a worm slipped onto my computer through our campus network,
and had a field day wiping things off my computer. I was running
Norton IS 2004, but...well...norton is crap and doesn't protect very
well. I backup regularly to Dual Layer DVD's, and also have a spare
Seagate 200gb 7200.7 to backup too, so I figured it was time for a
clean format anyway.

Rather then reset to RAID 1, I just decided to have 400gb of Hard
Drive space. I went into my system's bios, and set the SATA to
combined mode, meaning it would take on the characteristics of an IDE
drive, thereby not needing the Intel SATA RAID Drivers. The first few
installs, I was having issues and it was BSODing towards then end of
setup (I use a slipstreamed WinXP Pro with SP2 installation disc which
has worked numerous times in the past for other computers). I finally
got the Seagate Drive Setup program, and partitioned the boot drive
and other drive into 100gb partitions, which fixed any possible issue
with the 137gb barrier. It should have worked without needing to
partition into 4 parts with a Slipstreamed Copy of XP2, but I figured
I could always use partition magic to merge them later.

Finally got it installed, picked up NIS 2005 online on my other
computer, and installed it before connecting it to the net. Hooked
onto net, and installed updates.

I then proceeded to gather my 4 main backup discs to start moving
files over to the drive. After several BSOD's of DRIVER_IRQL_NOT_LESS
OR EQUAL

STOP Error code 100000d1, parameter1 00000002, parameter2 000000ff,
parameter3 00000001, parameter4 824dd15f

I finally booted into safe mode to transfer the files. Safe mode
worked fine.

I continue to get BSOD's whenever I transfer large amounts of files or
try installing something like World of Warcraft while in normal
windows. It is the same one, over and over and over.

Currently, in the Device Manager, the following is listed under IDE
ATA/ATAPI Controllers

Intel 82801EB Ultra ATA Storage Controllers
Primary IDE Channel
Secondary IDE Channel

The only other error code I'm getting in a BSOD, which has only
happened twice, is a PAGE_FAULT_IN_NON_PAGED_AREA.

Error code 1000007f, parameter1 0000000d, parameter2 00000000,
parameter3 00000000, parameter4 00000000.

That prompted me to run memtest86, and after 2 hours it found no
errors. I swapped out the memory for my brother's 2x 256 Corsair XMS
PC3200 from his AMD64 box, ran memtest again, and didn't find an
issues.

My understanding of how the BIOS gets the SATA to run is that it
spoofs it as a Third and Fourth IDE Channel for each SATA Device
added. It doesn't do this if it is in RAID Mode however. I have tried
to update the intel chipset drivers from those that were on my CD to
those on the manufactuer's website to those on Intel's site. None
work. I Figured I would try installing IAA to get a SATA driver from
that, but because it didn't detect a RAID Controller, it refused to
install. And Seagate doesn't make any drivers for their SATA Drives.

I uninstalled and let windows reinstall all the IDE Controllers after
a restart, to no avail. All that happened was I lost one Intel 82801EB
Ultra ATA Storage Controllers listed. I've tried updating the drivers
in Device Manager for the Intel 82801EB Ultra ATA Storage Controller,
and it gave me three options, and I've only chosen the first two,
neither which has worked.

Intel 82801EB Ultra ATA Storage Controllers
Intel 82801EB Ultra ATA Storage Controllers - 24D1
Standard DUal Channel PCI IDE Controller


Any help any of you all could give would be GREATLY appreiciated. If
all else fails, I can try going back to RAID 1, but because I now have
the Dual Layer drive, I don't really require that kind of data
security any longer. I have to get to bed, as I have class in about 6
hours. Thanks very much all!!

I just honestly can't determine which Driver is causing all these
crashes....
 
R

RLAmes

GamEmpire-- I'm a novice with computers and understood little of your post
re: your BSOD ... EXCEPT that you and I are the ONLY folks in Googleland
who have a parameter4 824dd15f error code from a blue screen. I've been
plaqued by that code for about 6 months now. I've done everything
including a complete reinstall of my OS, and still it comes back ... error
824dd15f. Windows Crash Analysis tells me only that a device driver is
causing it.

Did you find out what was causing your error? Does the fact that we both
get this 824dd15f code indicate it's the same driver or just the same
condition? And pieces of evidence you could give me to help isolate this
rascal would be appreciated.

RLAmes
 
J

Joshua Smith [MSFT]

Hello,

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me back. Good Luck,


Joshua Smith
DirectInput and OpenGL Test Labs
Microsoft
 
R

RLAmes

Joshua-- I did as you instructed. Upon reboot in normal mode, my computer
DID indeed crash, so I tried to enter Safe Mode and now the computer
crashes when I ask it to boot into Safe Mode. So I tried to reboot back
into normal mode again, and it doesn't crash, but I get the MS logo screen
for about 10 seconds, and then it returns me BACK to the safe/normal mode
selection screen instead of the Welcome screen, and does this over and
over. That is, it will not enter normal mode now, and it crashes on safe
mode. It did not do this at all before I asked it to Verify while I was in
noraml mode. Any ideas? Thanks. -Richard.
 
J

Joshua Smith [MSFT]

Hi again,

If Windows will not start after enabling Driver Verifier, you can try
"Last Known Good Configuration" in the Advanced Boot menu. Let me know if
that doesn't work.

Joshua Smith
DirectInput and OpenGL Test Labs
Microsoft
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top