0

Since Monday, my PC hangs for like two minutes on the RAID Configuration screen when I turn my PC on for the first time on a day (after being off for many hours). If I reboot, it takes the normal two seconds.

I use a RAID 0 setup with two 300GB HDDs, my RAID controller is an Intel ICH8R/ICH9R SATA RAID Controller.

My specs and that are in DxDiag.txt

It was working fine before and now suddenly this begins happening from Monday, if you need more information let me know.

Thanks in advance.

Note: I'm not sure if this is a hardware or a software problem, so I put it here.

Attachments
------------------
System Information
------------------
Time of this report: 10/24/2008, 19:58:37
       Machine name: SAMS-PC
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.080814-1236)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
       System Model: Dell XPS420                  
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 A06
          Processor: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (4 CPUs)
             Memory: 2046MB RAM
          Page File: 856MB used, 3080MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Music Tab: No problems found.
          Input Tab: No problems found.
        Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (n/a)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: NVIDIA GeForce 8600 GTS
     Manufacturer: NVIDIA
        Chip type: GeForce 8600 GTS
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0400&SUBSYS_043810DE&REV_A1
   Display Memory: 256.0 MB
     Current Mode: 1280 x 1024 (32 bit) (75Hz)
          Monitor: LG L1752S
  Monitor Max Res: 1280,1024
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.7813 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 9/17/2008 09:55:00, 6057472 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 9/17/2008 09:55:00, 6132576 bytes
Device Identifier: {D7B71E3E-4740-11CF-EB6D-332400C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0400
        SubSys ID: 0x043810DE
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A 
 Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
DDraw Test Result: Not run
 D3D7 Test Result: Not run
 D3D8 Test Result: Not run
 D3D9 Test Result: Not run

-------------
Sound Devices
-------------
            Description: SigmaTel Audio
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_10280215&REV_1002
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: sthda.sys
         Driver Version: 5.10.4991.0000 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 3/20/2006 16:06:04, 1156648 bytes
            Other Files: 
        Driver Provider: SigmaTel
         HW Accel Level: Full
              Cap Flags: 0xB5B
    Min/Max Sample Rate: 44100, 192000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

            Description: Modem #0 Line Playback (emulated)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: 
        Manufacturer ID: 1
             Product ID: 81
                   Type: Emulated
            Driver Name: 
         Driver Version: 
      Driver Attributes: 
            WHQL Logo'd: 
          Date and Size: 
            Other Files: 
        Driver Provider: 
         HW Accel Level: Full
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

---------------------
Sound Capture Devices
---------------------
            Description: Labtec Mic (WebCam Pro)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: usbaudio.sys
         Driver Version: 5.01.2600.5512 (English)
      Driver Attributes: Final Retail
          Date and Size: 4/13/2008 19:45:12, 60032 bytes
              Cap Flags: 0x41
           Format Flags: 0x4

            Description: Modem #0 Line Record (emulated)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: 
         Driver Version: 
      Driver Attributes: 
          Date and Size: 
              Cap Flags: 0x20
           Format Flags: 0x0

            Description: SigmaTel Audio
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: sthda.sys
         Driver Version: 5.10.4991.0000 (English)
      Driver Attributes: Final Retail
          Date and Size: 3/20/2006 16:06:04, 1156648 bytes
              Cap Flags: 0x41
           Format Flags: 0xCC0

-----------
DirectMusic
-----------
        DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
     DLS Version: 1.00.0016.0002
    Acceleration: n/a
           Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
                  Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
        Registry: OK
     Test Result: Not run

-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: BT Mini-Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC719
        FF Driver: n/a

      Device Name: BT Mini-Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC719
        FF Driver: n/a

      Device Name: BT Mini-Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC719
        FF Driver: n/a

      Device Name: BT Mini-Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC719
        FF Driver: n/a

      Device Name: BT Mini-Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC719
        FF Driver: n/a

      Device Name: Dell USB Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
        FF Driver: n/a

      Device Name: Dell USB Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
        FF Driver: n/a

      Device Name: Dell USB Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x2939
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 19:45:37, 59520 bytes
| Driver: usbd.sys, 8/10/2004 19:00:00, 4736 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC718
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 19:39:48, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 19:39:47, 24576 bytes
| 
+ HID Keyboard Device
| Vendor/Product ID: 0x413C, 0x2010
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 19:39:48, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 19:39:47, 24576 bytes
| 
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
4
Contributors
21
Replies
22
Views
9 Years
Discussion Span
Last Post by Samrulez91
0

sounds like it might be a hardware problem, or BIOS. if there's a newer version of your BIOS use them.

The other thought is that it's an issue with one of the drives and it's having a hard time coming up from "cold" run thorough disk checks on them and see if they have anything wrong.

If this is a RAID 0 I'd suggest you start baking up data, whether it's your controller or drives, if either fails* you might lose the array and lose data.

*Raid arrays will only be recognized form the same chipset they were created on. If your raid controller goes out you wont really be able to recompile the array unless you replace it with the same controller.

0

I updated my BIOS as suggested by my friend, to Revision A06, which is the latest, did nothing to solve the problem.

What disk checks do you mean? I have done CHKDSK where I set it to automatically fix file system errors and scan for and attempt recovery of bad sectors, this took about an hour. There were no problems there either.

0

Ok, since it won't let me edit my post, il say this: If I press CTRL-ALT-DEL when the PC begins to hang on first boot, it reboots and then loads with no hang, even though I didn't let it hang and load up the first time.

0

There are other non windows diagnostic tools. Try the manufacturers disk tools (on their website, usually not hard to find) and just google "disk daignostic tools".

0

The problem has appeared to fix itself, It didn't hang on first boot today.

But I will use the manufacturers (one is Seagate, one is Western Digital) disk tools anyway.

Thanks for your help.

0

Ok, the problem has come back.

The manufacturers disk tools weren't much help since the two HDDs are recognised as one by Windows.

I updated my RAID controller driver to latest, didn't fix the problem. Would a reinstallation of the OS fix this? Because I was thinking of doing that anyway.

I don't understand it, both HDDs seem perfectly fine, the RAID configuration screen said status is normal. I am using the PC with the problem as I speak.

0

are you using this PC as a server of some kind? if not why do you need to enable RAID.

0

if you really have to enable it, then i would buy two HD from the same manufacturer with the same amount of disk space

0

I bought the PC from Dell and it already had a RAID 0 setup with two different manufacturer's drives. The PC originally had Vista, I changed it to XP like the same day it was delivered to my house.

The RAID 0 setup with these two different manufacturer's drives has been perfectly fine for ages now (I bought the PC in February). Both drives do have the same amount of disk space. I prefer it to be RAID 0 than split up.

Also, I'm not using the PC as a server, just for general use like playing games, music etc.

0

to save headaches and hassles, disable RAID in the BIOS and reformat your secondary HD and use it as backup storage

0

I would prefer not to split the drives, I like having it as RAID 0.

It has not caused any problems until now and even then it's not that big of a deal, only makes booting take a bit longer.

0

We really should stay on topic to fix the problem, not convince him to get rid of RAID, most people who use RAID don't need it.

On that note if you're open to the possibility of re-installing your system, consider JBOD or "Disk Spanning" thorugh windows. They work the same way as RAID 0 in that both drives show up as a single partition. It doesn't have the same performance increases in games, but there are other task where separate disks perform better.

0

Reinstalling the OS is a possibility but I would really prefer not to. What can I do?

0

Reinstalling the OS is a possibility but I would really prefer not to. What can I do?

I still have this problem.

0

Reinstalling the OS is a possibility but I would really prefer not to. What can I do?

time to bite the bullet and give in and do what you prefer not to do

0

time to bite the bullet and give in and do what you prefer not to do

Will reinstalling the OS solve the problem though, that's what I want to know.

If it does, I'l do it.

It's been like a month since I first got the problem and my HDDs have not failed or nothing so I presume my RAID 0 setup is fine and an OS reinstallation will fix the boot hang (I hope).

0

I'm not sure an OS reinstall will resolve it, but it's probably your best bet. I hang at that point in the set up is an issue with the array itself (either the disks, configuration, or controller) so breaking the array, re creating it and then starting over might be your best bet.

I have an idea for trouble shooting:

If you have or can borrow two spare drives, put them in your system and create a raid array. If you still hang after doing this you know it's the controller, if it doesn't you've narrowed it down to the current configuration and know it's a corruption of the drives or settings.

0

Ok. I will format the HDDs, reinstall OS, and re-create the RAID. I will get back to you how this goes, if the hang is fixed or not. I will begin backup of data now.

I don't have any spare drives so I can't do your idea.

0

Ok. I will format the HDDs, reinstall OS, and re-create the RAID. I will get back to you how this goes, if the hang is fixed or not. I will begin backup of data now.

I don't have any spare drives so I can't do your idea.

if you have a lot of data ,and new data all the time, a raid -0 is really not recommended for you !if raid fails you will lose all data on both drives ! or something like that !

0

I do think you'd be better with Disk spanning, you might look into JBOD raid before you recompile the array. You might fall in love.

0

It was a software problem after all, the problem is fixed. It didn't hang.

Thanks everyone for your help.

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.