Sign in with
Sign up | Sign in
Your question

Raid and BSOD issues.

Last response: in Windows 7
Share
October 24, 2009 11:41:40 PM

Hello.
Well, my Win7 RTM (x64 7600 ultimate) was crashing any time I had my motherboard (Foxconn Bloodrage X58 ICH10R) in RAID mode, though I had it on a independant drive (so I could use some 500GB drives I had for Raid5).
Then it started to BSOD every 15 mins to hour afterwards (startup repair, 3 day rollback etc. tried), and thus I just went to my local shop and picked up Win7 x64 home OEM.
U disconnected my main drive (1TB that had my OS on it), put my mobo in raid mode, created a raid5 array across 4 500gb 7200.10 drives, and installed it without a hitch.
I then start to do my basic security updates etc., and the I BSOD, and after rebooting, I find my raid is destroyed (ICH10R not recognizing the drives were in a RAID anymore)...

Would you think these are HDD related issues, OS related, or a faulty mobo?
If so, do you have any suggestions?

More about : raid bsod issues

a c 215 $ Windows 7
October 25, 2009 1:30:47 AM

I would check out the Intel website for updated RAID drivers. The Intel Matrix Storage controller on my Gigabyte GA-EX58-UD5 has been pretty rock solid, but I never get drivers from Gigabyte for it.... instead always going straight to Intel. See if it continues bluescreening after the new drivers are in place.
m
0
l
October 25, 2009 12:42:57 PM

...
The raid decided to come back, intact, and worked. However, every few minutes, I'd crash. The RAID would either dissolve or two of the drives decided they weren't part of it. A reboot fixed this, but only for a few minutes.

I disabled the RAID, set the mobo to IDE mode, and I am now trying to install Win7 on one of the 500gb drives. A few minutes into the installation, the first time it tells me it failed to install. I try again, and I BSOD while installing...
I'm going to try another drive to see if the issue still prevails.
m
0
l
Related resources
October 25, 2009 1:58:36 PM

I've successfully installed Win7 on the 2nd 500GB HDD, let's see how long it takes to fail...

EDIT:
The OS is on the second 500GB, then I reconnected my 1TB and started to transfer files from the 1TB to the 3rd 500GB, and I BSOD.I then tried moving the info from the 1TB to the 4th 500GB, and I BSOD again...
I am using the P09 BIOS. Foxconn Bloodrage GTI.

So, either every HDD I have has just bricked, or it's the motherboard...
Let's see how long Foxconn will take to repair it...
I'm trying to post on XTREMESYSTEMS (were all the BR gurus and a few Foxconn employees browse)... but after a couple weeks, my account still hasn't been cleared to post...
m
0
l
a c 215 $ Windows 7
October 25, 2009 5:51:53 PM

What error code are you getting when your system blue screens?
m
0
l
October 25, 2009 6:44:23 PM

Seems to be a different one each time...
m
0
l
a c 215 $ Windows 7
October 25, 2009 6:46:31 PM

Could you post some of them? The content in the brackets (the memory addresses and such) are not what interest me. The error code should be in the form 0x00000XX where the last 2 X's are variable.
m
0
l
October 25, 2009 7:53:26 PM

I'll pay attention to them.

I haven't BSOD on a hour now though. I can only hope that was the last time...
Now to figure out why my laptop all of a sudden thinks there's no wireless networks... and why my raid card on a different comp won't work at all. ^_^
m
0
l
October 26, 2009 2:10:12 AM

BSOD again (after several hours of of seemingly nothing...), but I didn't manage to get the code...
No response from Foxconn either...
m
0
l
a c 215 $ Windows 7
October 26, 2009 2:45:37 AM

Go to the System menu under Control Panel and click Advanced System Settings. Click the Settings button under Startup and Recovery, and uncheck the box called Automatically Restart. This will allow you to capture the error code when the bluescreen occurs.
m
0
l
October 27, 2009 6:18:21 AM

Alright, will do.

Think you have any use for my last system dump? It's only 350 megabytes. =D
m
0
l
October 27, 2009 7:00:05 AM

First crash (just browsing a SLC vs. MLC drives article...):

PAGE_FAULT_IN_NONPAGED_AREA

*** STOP: 0X00000050 (0XFFFFFFFFFBA61949, 0X0000000000000000, 0XFFFFF88004F693F7, 0X0000000000000002)

*** dxdkrnl.sys - ADDRESS FFFFF88004F693F7 BASTE AT FFFFF88004F05000, DATESTAMP 4ac5509e


While I've gotten many different ones, I do believe I've had this one before.
On start up I BSOD again. (I may have messed up this one, but I think I wrote it correctly)

*** STOP: 0X00000050 (0XFFFFFA7FF7000045, 0X0000000000000008, 0XFFFFFA7FF7000045, 0X0000000000000007)


For now, I'm going to up my memory and CPU voltage just a bit (though already running CPU at stick voltage/clocks, and can reach 165x21 on default voltages, and memory is a 1600MHz set, currently running at 1066MHz).

No reponse from Froxconn yet. Though my account over at XtremeSystems finally had been given posting rights (after several weeks of waiting).
m
0
l
October 27, 2009 7:12:59 AM

Oops... loaded the Win7 Ulti x64 7600 (torrented) on my 1TB instead of the Win7 Home x64 7600 (bought) on one of the 500GB...

Lets see how long this one also takes to crash...
m
0
l
October 27, 2009 7:43:28 AM

Though both the memory and CPU were overvolted, I BSOD again.

IRQL_NOT_LESS_OR_EQUAL

*** STOP: 0X0000000A (0X0000000014B94710, 0X0000000000000002, 0X0000000000000001, 0XFFFFF80002CDBCE7)


I have also gotten this one before I believe.

I was running a 4GB 64bit 8 thread Linpack (via IntelBurnTest), and completed two runs first.

On my next boot, the BIS only detected 4GB (instead of 6GB) of memory, but after another reboot, it detected all 6GB again.
Could this all be just a bad memory DIMM? (Though I've been running it at 1.60V @ 1066MHz CAS7, though it's rated for 1600MHz?)
I may just start switching DIMMS around to see... but my heat sink is in the way, meaning I may have to take it off... which I need to remove my motherboard from the case to do...
m
0
l
October 27, 2009 10:30:00 AM

SYSTEM_SERVICE_EXCEPTION

*** STOP: 0X0000003B (0X00000000C0000005, 0XFFFFF80002BBA90D, 0XFFFFF88009337EF0, 0X0000000000000000)


It's only crashing every hour or so now, so its calmed down...
Overvolting memory and CPU obviously didn't work...
m
0
l
a c 215 $ Windows 7
October 27, 2009 11:54:58 AM

Go grab Memtest86+ from http://www.memtest.org. Those blue screens seem to be pointing to a RAM issue, not a RAID (or RAID driver) problem.
m
0
l
October 27, 2009 6:22:20 PM

So, the memory may be the issue...
After 5 minutes, over 500 errors (using a .iso of memtest86+).
After 10 minutes, something around 700 errors, and then it crashed a rebooted... nice to see even memtest isn't invulnerable to crashing.

Finished a test this time, with 5 errors.
m
0
l
a c 215 $ Windows 7
October 27, 2009 10:38:14 PM

Time to RMA or replace that ram... oh and I love it when the ram is so messed that even memtest crashes!
m
0
l
October 28, 2009 4:37:07 AM

Ha...

Memtest ran the entire time I was at work...
5 errors and not a single crash since I left.

It's the OS, nope. It's the HDD, nope. It's the MOBO, maybe. It's the CPU, nope. It's the RAM... I haven't a clue...

Anyways...
Are you trying to get the title of Toms Win7 Guru or something (judging by how many Win7 comments you post on)?
m
0
l
a c 215 $ Windows 7
October 28, 2009 10:56:51 AM

Not at all... I just like helping out with Windows 7 issues.
m
0
l
October 31, 2009 4:27:49 AM

I hate the censoring in this... delete a paragraph to censor one word...

As I said, it just passed a 9 hour and 50 minute memtest86+ flawlessly...
m
0
l
November 2, 2009 2:27:18 AM

It failed again... first a program crashed, soon after I BSOD again, I run a 1 hour memtest and get 140 errors...
If I RMA these, I'll be without my computer for weeks. I have others... but... i7/6GB/4870 vs 2.0GHz C2D/2GB/4750... yeah.
m
0
l
a c 215 $ Windows 7
November 2, 2009 3:30:49 AM

Your choice... either way the ram is faulty... either replace it by buying more, or rma what you have and leave the machine down for awhile.
m
0
l
November 2, 2009 5:27:24 AM

Thank you for your help.
Now, I just have the option of spending over $100 now for more RAM, or wait it out...
Being that my pockets are empty, that's hard to choose.
The RMA would take weeks likely...

If I had a 6 DIMM mobo, I'd just suck it up and buy two new sets though. =D
(or sell them locally and blame the buyer for damage due to improper installation)
m
0
l
!