Bluescreen on Vista install 90% (x64)


Recommended Posts

Hey guys wassup,

So I got back to england today and wanted to setup my new machine,

Spec: http://asphyxia8489.net/blog/?p=6

I got out my shiny new copy of Windows Vista Home Premium x64, put it in the DVD drive and off it went, I partitioned the drive and began the install, now I'm getting a bluescreen as soon as it hits 90%. I'm baffled.

So I went off installing alternate OSes to see if they suffer similar issues, Windows XP installed fine, minus only using 3GB of my total 8GB of RAM, and obviously Ubuntu 8.04.1 installed fine too.

I ran a full memory diagnostic and everything came up clean, it ran for Four hours BTW

I tried installing Windows Vista with one stick of RAM, two sticks of RAM, swaping them about, even using some old DDR2-667 RAM I had lying around, doesn't matter what I do, same issue.

The bluescreen message is ether PAGE_FAULT_IN_NONPAGED_AREA or IRQL_NOT_LESS_OR_EQUAL

The Motherboard is running on the latest BIOS so thats not the issue.

Anyone have any ideas at all?

Thanks guys

EDIT: Ok in this Run it got to 96%.... so close...

Link to comment
https://www.neowin.net/forum/topic/665778-bluescreen-on-vista-install-90-x64/
Share on other sites

It could be a HD drive problem.

Try disconnecting one (disable RAID in BIOS) OR using a driver disk at start of install (with RAID enabled in BIOS)...

edit: Try making a driver disk with this download (v8.5.0.1032):

http://downloadmirror.intel.com/16760/eng/f6flpy64.zip

Then during the operating system installation, after selecting the location to install Vista, click Load Driver to install a third party SCSI or RAID driver.

Edited by pjak

As already stated in my first post:

ASUS P5Q Deluxe P45 Socket 775 ATX Motherboard

Intel Core 2 Quad Q9450 2.66GHz Socket 775 Processor

Corsair 8GB DDR2-800 (4-4-4-12) RAM

2 x Samsung HD502IJ SpinPoint F1 500GB Hard Drive in a RAID0 Array

ATi Saphire HD 4850 512MB GDDR3

cant believe no ones stated the obvious :p

if its a PRE-SP1 disc then make sure you only have 2GB of ram in. If its a SP-1 integrated disc you should be able to install with all 8GB of ram in. Its a well known problem with Vista NON SP-1 integrated discs. If that still doesnt work take a look at the voltages on the memory. It might be you need to up the voltage for those sticks.

cant believe no ones stated the obvious :p

if its a PRE-SP1 disc then make sure you only have 2GB of ram in. If its a SP-1 integrated disc you should be able to install with all 8GB of ram in. Its a well known problem with Vista NON SP-1 integrated discs.

It's an SP1 disc, and I've already said that I tried it without the rest of the RAM in :)

About the driver boot disc, I assume i'll need to do that via a floppy? Damn, I dont have any of those. Any way I can do it over USB flash drive?

Edit, bluescreened at 7% this time. :D

Two things to check on:

1) At the beginning of the Vista installation (I'm assuming that you're booting off of the DVD) there is a point where the user is prompted to provide 3rd-party disk drivers - if you're installing on a SATA drive, you'll need those drivers from the manufacturer of the motherboard or it's chipset maker.

2) Check with the motherboard manufacturer to see if there are any reported problems with the BIOS & Driver releases you are installing to. Also, if the SATA controller chips have upgradeable firmware, make sure those are upt-do-date AND are working for Vista x64

Hope this helps!

--Scott

At the moment the BIOS is configured for a RAID 0 array of both drives.

I cant see any area at all that gives me the option to load drivers from a disc... :(

At the moment i'm downgrading my BIOS to it's first version to see if vista likes that more, then after the install (i hope) i'll update the BIOS again and hope everything is good :D

EDIT: Vista setup is loading now after the downgrade so we'll see how that goes, I think it was a bad idea to build a new PC after 40 hours with no sleep due to travelling....

Edited by Vegetunks

Update, ok, so now Vista is installed and running, but the Blue-Screens keep coming...

Now the main one is MEMORY_MANAGEMENT

Seriously, this cant be the RAM... The RAM is fine, happy and content in any other box I put it in. Maybe clock it down to 667MHz?

after the Vista installation, install the chipset INF (v9.0.0.1011)...

http://downloadmirror.intel.com/10884/eng/...0.0.1011_PV.exe

matrix storage manager (intel RAID - v8.5.0.1032)...

http://downloadmirror.intel.com/16750/eng/IATA85ENU.exe

and make sure your BIOS is the latest (v1306)...

http://dlsvr.asus.com/pub/ASUS/mb/socket77...DELUXE-1306.zip

and then install video drivers (latest is v8.8)

http://game.amd.com/us-en/drivers_catalyst...64/radeonx-xp64

also, your LAN network driver (v10.64.2.3):

http://www.marvell.com/drivers/files/yk60x64_v10.64.2.3.zip

then don't your sound drivers (and anything else that's displayed as unknown in Device Manager)!!!

the problem you SEEM to be having is HD access...if it fails to read/write the pagefile Windows just blue screens...you just need the correct drivers (as above)...

Edited by pjak
Update, ok, so now Vista is installed and running, but the Blue-Screens keep coming...

Now the main one is MEMORY_MANAGEMENT

Seriously, this cant be the RAM... The RAM is fine, happy and content in any other box I put it in. Maybe clock it down to 667MHz?

You ran memtest on the ram for errors?

As stated already, again, I have already done a four hour memory diagnostic and it showed up clean.

I've got all the latest drivers but am still getting bluescreens :(

This is a real odd one, dosnt make a lot of sense.

I read an article on the ASUS forums that this motherboard dislikes Corsair 4-4-4-12 RAM, yet I lowered the clock speed to 667 and upped the CAS latencys to 5-5-5-15 and had the same issues so it's obviously not RAM related, not to mention of course that I have the same issues with a different stick of RAM entirely (OCZ), it seams to be Vista that is the problem here, nothing else, SP1 seams far more unstable to me then SP0 ever did.

Going to get some sleep now, finally, and hopefully i'll come up with something, if not, guys, keep working your magic and firing ideas at me.

Vista isnt to blame here, its clearly a hardware issue, if it was a vista issue everyone would be getting it but as far as im aware your the only one.

I recently had this problem with my new build and the motherboard was causing all the issues. sent it back and bought a different mobo and it worked perfectly.

Well, it's got to be Vista as Windows XP works fine minus the huge memory difference as do several Linux Distros. Hell, even managed to get Mac OS X to run on it quite easily and error free. Maybe try a different Vista disc?

I would suggest running windows Vista with only 1GB of ram, and see if it BSOD's again. I can't really think of anything else other then bad ram, or faulty hardware....

Vista should only bsod if it detects bad drivers, or bad hardware. Something you are using is not vista compatible fully, and may require another version of the driver.

look online for all your hardware you have, and see if it returns with any vista troubles

If you have Vista installed and up to date then run the system file checker, sfc /scannow, from a command prompt, however as others have stated i'd say it's a hardware issue. Vista is allot more sensitive to hardware errors than any other OS i've tried, so just because you don't have issues with XP, for instance, doesn't mean it's not a hardware fault.

I would suggest running windows Vista with only 1GB of ram, and see if it BSOD's again. I can't really think of anything else other then bad ram, or faulty hardware....

Vista should only bsod if it detects bad drivers, or bad hardware. Something you are using is not vista compatible fully, and may require another version of the driver.

look online for all your hardware you have, and see if it returns with any vista troubles

Well, I've tried running with 2GB of RAM, as a I have 4 x 2GB of RAM. Same issue, ditto for running with different modules.

Try a different Vista disc, like you said.

Ok, I'll see if one of my mates has the x64 version or download a ISO or something.

Someone recommended to me to use VLite to integrate all the drivers into the Disc, anyone think that'd help? I dont seeing as I'm now running all the latest drivers.

However, one thing I have noticed is I downgraded to the Intel Drivers on the ASUS DVD and I couldnt even get to the desktop before it BSODed yet the newer drivers allow for almost unlimited use providing I dont open or close any applications. So MAYBE it'll be fixed in a later Driver release, so that brings me to this question.

How often do Intel release new chipset drivers?

Well, I've tried running with 2GB of RAM, as a I have 4 x 2GB of RAM. Same issue, ditto for running with different modules.

Ok, I'll see if one of my mates has the x64 version or download a ISO or something.

Someone recommended to me to use VLite to integrate all the drivers into the Disc, anyone think that'd help? I dont seeing as I'm now running all the latest drivers.

However, one thing I have noticed is I downgraded to the Intel Drivers on the ASUS DVD and I couldnt even get to the desktop before it BSODed yet the newer drivers allow for almost unlimited use providing I dont open or close any applications. So MAYBE it'll be fixed in a later Driver release, so that brings me to this question.

How often do Intel release new chipset drivers?

Every few months. It shouldn't be the Intel chipset drivers because they aren't actually drivers. They are just inf files that tell the OS more specifically how to configure the hardware.

It's the motherboard, Tested every component minus the processor in a different PC today and vista installed without a hitch, Shame, I cant RMA it because I lost the PnP cap for the processor socket :'(

Damn thats a waste of money... ?90 or so, gone, pulls hair it, going to be another month before I get this machine working now....

Can anyone recommend a good motherboard for a Core2Quad and a ATi 4850 bundled with 8GB of DDR2-800 RAM in 4 x 2GB

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!