Results 1 to 10 of 10

Thread: NF&-S v2: Blue screen after reinstalling Windows, HELP!!

  1. #1
    O\/\/N3D
    Join Date
    Jul 2003
    Location
    Glasgow
    Posts
    372
    Thanks
    0
    Thanked
    0 times in 0 posts

    NF&-S v2: Blue screen after reinstalling Windows, HELP!!

    Hi all,
    My PC was running fine for about 12 months, overclocked nicely too.

    About 3 months ago it started randomly rebooting itself, no real pattern, temps were good but I downclocked it anyway, no difference so yesterday I finally got round to reinstalling Windows.

    I'm using an NF7-S V2, Barton 2600+ Mobile, 1gb (2x512mb) Crucial Ballistix and a 120 Maxtor SATA HDD

    First problem ... when booting from CD and it asks "press F6 to install sata/raid driver" when I press F6 nothing happens?? I thought it might be the keyboard but I tried another one.
    I could sort of get past that as a little later it says something like "no hard disk found if you have an install disk for your hard drive put it in the floppy drive now" so I enter the raid/sata floppy disk (latest version) and it installs it, then it goes through the whole copying windows files etc etc then on the first reboot the Windows XP loading screen flashes up just for a second then I get a blue screen "stop" error.

    I have tried this several times.
    I have flashed the bios from D26 Black MantraRay back to the latest one form the Abit site.
    I have removed everything from the computer including the processor and rebuilt it just with essentials.
    I have tried the memory in different slots and tried only using one stick at a time.

    No idea what to do next, it could be the memory, hard disk or the motherboard, dont have the money or the means to test them all.

    HELPPPPP??!! :bang:

  2. #2
    Theoretical Element Spud1's Avatar
    Join Date
    Jul 2003
    Location
    North West
    Posts
    6,846
    Thanks
    229
    Thanked
    228 times in 180 posts
    • Spud1's system
      • Motherboard:
      • Mac Pro
      • CPU:
      • 2x 2.8ghz Quad Core Xeons (octo-core)
      • Memory:
      • 4gb DDR2 FB-Dimm
      • Storage:
      • 1x1TB, 1x320gb, 2x500gb, 1x250gb, 120GB SSD
      • Graphics card(s):
      • Nvidia Geforce 560Ti
      • PSU:
      • Mac pro PSU
      • Case:
      • Mac Pro Case
      • Operating System:
      • Windows 8
      • Monitor(s):
      • 1x22" LG 3D TFT 1x 19" ViewSonic
      • Internet:
      • 80mb BT Infinity
    I have had this problem before Last time it turned out to be the drivers I was using.

    make 100% sure they are for your specific chipset first of all, and if you are sure that they are then try the versions for different OS's. That is, I assume you are trying the XP ones, but try the 2k ones too, or the win2003 ones. For me I have always had better luck with win2003 drivers than XP ones..no idea why but it seems to work

  3. #3
    Senior Member just_laze's Avatar
    Join Date
    Aug 2005
    Location
    London
    Posts
    581
    Thanks
    19
    Thanked
    0 times in 0 posts
    • just_laze's system
      • Motherboard:
      • Gigabyte GA-P35-DS3R v1.0
      • CPU:
      • Intel Core 2 Duo E5200
      • Memory:
      • 4 x Corsair 1GB 6400C4 800MHz
      • Storage:
      • Samsung Spinpoint F1 1TB x2
      • Graphics card(s):
      • nVidia 9600GT 512MB
      • PSU:
      • Tagan T430-U15 430W
      • Case:
      • Cooler Master ATC-201B SXT
      • Operating System:
      • Windows 7 Home Premium 64bit
      • Monitor(s):
      • LG L227WT
      • Internet:
      • 8Mbit
    The point where he's receiving Blue-Screens suggests he hasn't even got around to installing the chipset drivers.

    As for using drivers designed for one operating system on another, i'd strongly advise against it.

    laze.
    You're invited to follow me on Twitter

  4. #4
    Senior Member Max Tractor's Avatar
    Join Date
    Jan 2006
    Posts
    1,248
    Thanks
    44
    Thanked
    41 times in 38 posts
    • Max Tractor's system
      • Motherboard:
      • Biostar TA890GXE
      • CPU:
      • 95w 1055T@x4-3.5Ghz-1.15v
      • Memory:
      • Samsung Green 30nm low voltage 2x4GB@1.26v
      • Storage:
      • Corsair 3 60GB-Sandisk Extreme 240GB
      • Graphics card(s):
      • 7850 2GB
      • PSU:
      • Seasonic SS-1050XM
      • Case:
      • Coolermaster elite 120(Modd)
      • Monitor(s):
      • BenQ EW2430
    The only way to trouble shoot this is with other kit, although you can test the memory with memtest, and you can use powermax from the maxtor site to test your HD. I would also check the NB fan, these are notorious on the nf7 for craping out

  5. #5
    O\/\/N3D
    Join Date
    Jul 2003
    Location
    Glasgow
    Posts
    372
    Thanks
    0
    Thanked
    0 times in 0 posts
    Not the northbridge as I have an aftermarket cooler on there.

    I guess I'll try Powermax, but dont I need to low level format the drive with that first? I really dont want to lose all the stuff that is on there!

    Memory should be fine, its Crucial Ballistix that ive been running at 200fsb with not much voltage for ages when its rated to run at nearer 250

  6. #6
    Senior Member just_laze's Avatar
    Join Date
    Aug 2005
    Location
    London
    Posts
    581
    Thanks
    19
    Thanked
    0 times in 0 posts
    • just_laze's system
      • Motherboard:
      • Gigabyte GA-P35-DS3R v1.0
      • CPU:
      • Intel Core 2 Duo E5200
      • Memory:
      • 4 x Corsair 1GB 6400C4 800MHz
      • Storage:
      • Samsung Spinpoint F1 1TB x2
      • Graphics card(s):
      • nVidia 9600GT 512MB
      • PSU:
      • Tagan T430-U15 430W
      • Case:
      • Cooler Master ATC-201B SXT
      • Operating System:
      • Windows 7 Home Premium 64bit
      • Monitor(s):
      • LG L227WT
      • Internet:
      • 8Mbit
    PowerMax will allow you to run an advanced test without formatting the drive, definitely run memtest86, a good CD full of utilities for attacking hardware problems can be found here.

    laze.
    You're invited to follow me on Twitter

  7. #7
    Resident abit mourner BUFF's Avatar
    Join Date
    Jul 2003
    Location
    Sunny Glasgow
    Posts
    8,067
    Thanks
    7
    Thanked
    181 times in 171 posts
    the SATA RAID BIOS & SATA driver tend to have to be "matched".
    If you have the latest Abit BIOS it will have a later SATA BIOS (it's integrated into the main BIOS) so you need to use the drivers for that not the original Abit driver floppy.

    btw what parameters are on the BSOD?

    MSI P55-GD80, i5 750
    abit A-S78H, Phenom 9750,

    My HEXUS.trust abit forums

  8. #8
    O\/\/N3D
    Join Date
    Jul 2003
    Location
    Glasgow
    Posts
    372
    Thanks
    0
    Thanked
    0 times in 0 posts
    Ok, ran PowerMax ... its not the hard disk.

    The BSOD goes on about some crap like IRQL_NOT_LESS_THAN_OR_EQUAL_TO whatever the hell that means, google seems to indicate something to do with memory but that could be the board making the memory malfunction or the memory itself.

  9. #9
    O\/\/N3D
    Join Date
    Jul 2003
    Location
    Glasgow
    Posts
    372
    Thanks
    0
    Thanked
    0 times in 0 posts
    Have run Memtest on both sticks seperately and I'm almost 100% convinced now that its the memory, my Ballistix has died on me!

    Anyone ever had any experience of Crucial's warranty process?

  10. #10
    Senior Member just_laze's Avatar
    Join Date
    Aug 2005
    Location
    London
    Posts
    581
    Thanks
    19
    Thanked
    0 times in 0 posts
    • just_laze's system
      • Motherboard:
      • Gigabyte GA-P35-DS3R v1.0
      • CPU:
      • Intel Core 2 Duo E5200
      • Memory:
      • 4 x Corsair 1GB 6400C4 800MHz
      • Storage:
      • Samsung Spinpoint F1 1TB x2
      • Graphics card(s):
      • nVidia 9600GT 512MB
      • PSU:
      • Tagan T430-U15 430W
      • Case:
      • Cooler Master ATC-201B SXT
      • Operating System:
      • Windows 7 Home Premium 64bit
      • Monitor(s):
      • LG L227WT
      • Internet:
      • 8Mbit
    Crucial aren't particularly enthusiastic about taking memory back, at least not in my experience but if you mention you've ran the memory at the stated voltage and timings as outlined in the specification and memtest86 has produced errors i'm sure they'll gladly take it back and replace it for you.
    You're invited to follow me on Twitter

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. The future of OS/2 - Open source or not?
    By Steve in forum HEXUS News
    Replies: 11
    Last Post: 18-07-2009, 08:06 PM
  2. Windows XP Email?
    By joshwa in forum Software
    Replies: 9
    Last Post: 18-01-2004, 09:38 AM
  3. Stealth Fighter is windows based ;)
    By Skii in forum General Discussion
    Replies: 11
    Last Post: 23-12-2003, 10:16 PM
  4. Windows Server 2003 Login Screen
    By Dorza in forum Software
    Replies: 8
    Last Post: 17-12-2003, 02:12 AM
  5. Windows Update flaw 'left PCs open' to MSBlast
    By Bunjiweb in forum Software
    Replies: 10
    Last Post: 19-08-2003, 02:44 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •