Com-Central.net

Interesting. I installed their basic drivers and nothing more, haven't had a BSoD to my recollection, system is *extremely* stable, like a rock! Actually is left on 24/7. And simply eats up anything I throw at it.

Glad everything is humming well for you now!

Everything..., except not all of the RAM appears to be fully functioning.
Haven't figured that one out yet.
32Gb is 'seen' by the BIOS and Windows (7), but the system reports a RAM presence of "32.0 Gb (16.0 Gb useable)".

It's all seated properly and working (otherwise it wouldn't know there's 32.0 Gb installed) but something's stopping 16.0 Gb of it from functioning properly.
I thought it might be the GPU RAM total preventing all of the system RAM from being used, but the card only has 2.0 Gb onboard, so it's not that.
It's a 64-bit installation of Windows 7 (and 16 Gb is above the old 32-bit total limit anyway).
Must be something in the BIOS but I haven't found it yet.

Will advise.

Incidentally, my temp's (twin-fan cooled only, with the 120mm CoolerMaster unit in my sig) are topping out at 25°.
With all but one prog. left to re-install (Propellerhead's "Reason") it takes 15 seconds to post and boot to my Windows password.

LOVIN' it.

So Windows 7 (Home) only sees 16Mb of RAM.
I have upgraded to Windows 10 (Home) which sees all 32Mb of it.

However, I have the same Win10 issues I had on my last system.
Conflicting drivers and BSoD's.

Had to uninstall and reinstall my sound and graphic cards and drivers which fixed some problems (Win10 did not do this automatically, but did on my laptop which runs fine in Win 10).

However I still get a BSoD every time I boot, which doesn't happen when I reboot (having done nothing to change anything).

I have checked all the error messages (which do not contain the detail of pre-Win 10 OS's) and everything points to memory issues but not how to fix them.

MEMORY-MANAGEMENT_SYSTEM_SERVICE_EXCEPTION

ATTEMPTED_TO_WRITE_TO_READONLY_MEMORY

KMODE_EXCEPTION_NOT_HANDLED

IRQL_NOT_LESS_OR_EQUAL

IRQL_NOT_LESS_OR_MORE

DRIVER_IRQL_NOT_LESS_OR_EQUAL

SYSTEM_SERVICE_EXCEPTION

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGR.SYS)

BAD_POOL_HEADER

These are just some of the happy memories from the nineties Bill is giving me this time.

For interest, I can restart this system from Windows 10 and back in 25 seconds.
...When I don't get a BSoD!
Otherwise add another 15 seconds for the faff.

Just had to reformat my HP laptop that I upgraded to Win 10 from Win 7. It was to the point of taking almost 4 minutes just to boot up and then when you click on any program to start, it would take up to 1 minute before that program would start. Then it started locking up. Ram would be at 81% and processor would max out at 100% and lockup. Went back to Windows 7 factory install like out of the box and it is running like a scalded dog again! Never again will I upgrade to Win 10.

Now a new puter with all hardware made for Windows 10 might be a good thing.

Hope you figured out you new rig Shades.

My new desktop build with SSD hardrive, 3.6 Ghz AMD processor, 32 gigs of DDR3 1600mhz ram, 750 watts gold power supply, NVida GT 740 vid card with 2 gigs of DDR5 ram on it and Windows 7 Ultimate 64 bit is BLAZING fast and will boot in 22 seconds

Not quite.
I just went back to Win10 during the week.
Unfortunately, although M$'s major selling point is how you can reverse the install, it didn't revert well.
I kept the original files but some have been moved and others deleted so now Win7 didn't work well either.

I downloaded the Win10 upgrade this time and installed from the disk.
The reason I did it this way is because I found so many 'fixes' online that refer back to "the installation disk".

I have not had the same quantity of blue screen issues this time (ie. on every boot), but have so far had two "IRQL_NOT_LESS_OR_EQUAL"s and one boot lock up (with an SSD???! lolol).

I still can't track it back properly but it seems to point to either the RAM or, I'm thinking, maybe my soundcard.
I'm satisfied everything else seems to be running okay this time, possibly because of the fixes I made last time around.

Bloody annoying that the blue screens just give an error message without identify where the problem(s)/causes is/are though.

It is still running much better now than last time though (touch wood).
Whole thing goes from post to boot in under 15 seconds now (was getting 17-20 in Win7 as well).

Homey, you might want to look at what prog's are opening during startup.
There are loads which the providers authorise to load during the boot process nowadays which aren't necessary to run Windows.
It may be convenient to have them load then and be available straight way, but it delays the boot and, if you're not going to use them, what's the point?

Apple has lots that they bless you with during an iTunes install and updates (most are useless in Windows).
I've disabled most of them during the boot process itself, although I keep iTunes as I use it all the time and iPlayer itself has a minimal impact on the startup.
Video players like RealPlayer have massive impacts on bootup.
But many of these things can all start later, when you might actually want to use them.
But that doesn't sound like the whole problem in your case.

It may be driver related (as mine was/is)
Win10 doesn't automatically load or update all the drivers it should after the upgrade.

I found a [properly] updated graphic driver fixed more than half of my issues.
But even then it wouldn't work just by downloading and installing, oh no.

I had to remove the existing driver (which I'd already updated to the correct one for Win10 64-bit) and then auto re-install it from the NVidia site.
Presumably there was a load of cobblers left behind when I upgraded and this was removed during the second process.

Did the same with SoundBlaster but I still think that may need some tweaking and may be the cause of at least some of my current bluescreens.

Hope this helps.

So now that you have a new machine, you can join us on the Sunday afternoon Bush flights!

So many punchlines and not one of 'em would keep this thread outta Ms. Kitty's.

Yup I use the startup manager....used to be MSconfig...to control proggies that start at boot. Only ones needed are the ones I allow. I also still use the Driver Cleaner from NVida everytime I update the drivers. Anyway the laptop is running GREAT again on 7 and I will never upgrade to 10. I might build a new puter with all hardware made to run on 10 because I kinda liked 10 when it was running good but it never ran Great as an upgrade.

Good Luck on yours.

Yeah, it's really stupid.
I run a laptop which I upgraded from Win8 to Win10 and it runs as good as gold.
But my main rig I went from 7 to 10 and the process could not have been more involved and given me so many problems since.
Still getting some now.
Just locks during the boot and restarts every day.
Might be something to do with the internal clock I guess.
No real idea.

Matter of interest, trying to fix my blue screen issues just lead me into the BIOS where I found a Flash Drive had inserted itself into prime position of my boot sequence.
I re-positioned it and then re-booted again.

I'm down to just 10 seconds to reach my password screen now!

Not had a blue screen yet, so that may have been part (or all) of the issue.
Will let you know once it's had tiome to settle down and I can definitely attribute it.

Glad that it seems to be a configuration issue, Shades. Sounded unusual considering the good hardware... errr, "kit"... ya got there!

Heheheh.
Ta.

Still getting some issues.
Not as many as last time around fortunately.
Think it may be audio related as the sound was crackling and dropping out altogether yesterday.
I shall persist in trying to get to the bottom of it.
I have to as it's main use is audio these days.
lol