BSOD random, 0x00000024 raid 0 system

[ieatchickens]

Good evening folks, I have a Raid 0 system that would freeze randomly.

I updated to the latest motherboard BIOS(2.00), installed latest intel RST drivers, and even switched my HD's from sata 2 ports to sata 3 ports, as my samsung HD's firmware(1AJ10001) were optimised for sata 3 ports. But the problem persists and escalated to BSOD's.

Before i installed all those updates listed above, it used to be that a hard reset was all thats needed for the Raid 0 to be recognised and bootable. These days I require a CMOS reset, for a HD to be detected in BIOS, before setting up the sata controller to Raid, and finally setting up Boot sequence.

i5-2500k
ASRock p67 pro3
2 x 2g GSkill Ripjaws 1600mhz 7-8-7-24
2 x 500g samsung f3 onboard fake/Intel RST raid 0 (
1 tera samsung f3 storage
Windows 7 64 bit Home Basic OEM
Intel RST 10.6.0.1002
< 1 year usage

attached are :- a.)perfmon report
b.)Windows NT6 BSOD

 

[Maguscreed]

Your system is overclocked, noticeably so.
I would remove the clock before seeking to blame all these other things.

 

[ieatchickens]

it also happens on stock speed settings .. and just recently had a 0x000000f4

Edit:0x000000f4 error should be because i disabled c1 c3 halt state/ sleep in BIOS.

im beginning to think its a hd

I could try removing them and using HDDscan on them from my work computer tomorrow, if its possible to smart scan without removing them from my array(my os is on the array) i could even scan them now, though i doubt a capable program exists.

Edit 2: ok, now running on stock settings, through experience, i predict this will last less than 10 days before it BSOD's on me.

Thanks for the reply. I'll report back if there's anything else

 

[Maguscreed]

I could be more specific if there were actual dump files to work with here, that's how I get a clear picture of the nature of the failure.
None were included in your attached file.
could you navigate to c:\windows\minidump and ensure that no files are located within?
(zip and attach if you find any)

You could also try this to try and make sure a dump file is created on the next crash.
To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header
Select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[ieatchickens]

Thanks again for the prompt reply, I'm sure that automatic restart is unchecked. But under Write Debugging Information header, the option is NOT set to small memory dump (256kB) as it wasn't by default. Also, c:\windows\minidump is empty and default directory is set to %systemroot%\MEMORYDUMP. I've only got MEMORY.DMP files but i will make those changes you suggested when i get home and gather what you requested. I've currently got the disks with me and will do a s.m.a.r.t scan.

Edit : Seems my worst fears are realised, s.m.a.r.t status on both HD's are o.k, green light on all. I tested with HD sentinel,HDDscan and Crystaldisk. I find this extremely peculiar, as it was that same HD that would always disappear on that sata2 port.

Course of action :-

a.) wait till a bsod or

b.) reinstall windows, now that i think about it, i WAS stress testing/overclocking on this array/win install. Should i reset the array as well ? And, although win7 comes with built in raid drivers, I recall preloading (f6) them during this install, i wonder if there could be a driver conflict and if i should skip this part.

 

[ieatchickens]

I just got a BSOD again(0x0000001A), although minidumps are enabled, no dump files were found. In line with information provided in the above posts, I'd like to add that 50% of these hard-locks I'm experiencing results in the same hard drive not detected in BIOS. This same hard drive also falls out from my array, on the intel RapidStorageTechnology screen making volumeX(array name) not bootable. CMOS reset fixes that, though this time i get "Reboot and select proper boot media" although volumeX is detected and "Bootable" on the intelRST ROM.


I'll describe today's BSOD, while playing team fortress2 a hard lockup occurs, then a second of activity where I see "Windows is not responding", then a black screen, BSOD and finally dumping cache to physical memory.

I'll add "Windows_NT6_BSOD_jcgriff2" and "perfmon report" again. This is running on stock, no overclock of any sort.

 

[Maguscreed]

okay well from what you are describing we've kind of jumped outside of windows and software problems, into the realm of bios or hardware problems.

Have you updated the bios to the latest version?

 

[ieatchickens]

glad to hear from you
Yes latest bios and latest intel RST driver, although RST ROM is 1 version behind.
I'm currently verifying the array through RST to see if any errors, although it wont be able to repair(only raid 1,5,10 has rebuild option).

At 95% now, Ill attach the files after the scan. Im also thinking of running sfc /scannow and am runing out of ideas.
I did Windows memory Diagnostics and passed basic(or was it advanced). The extended memory test couldn't complete and got stuck for an hour.

 

[ieatchickens]

Array verified with no errors. Come to think about it, I had to switch back to sata3 ports to get it to boot again. Im secretly hoping it to be down to a hard drive with problems not detectable by s.m.a.r.t scans. I'll go ahead and run sfc scannow if its good ya.

Edit: sfc /scannow returns no file integrity errors.

 

[ieatchickens]

just received a 0x0000007a Kernel_inpage_data_error midway through a team fortress 2 game edit : minidump folder is empty, though it is set to save. Why isn't there anything ..?