What steps did you do before you thought all was going well?
I still do not see security software installed. Proceed with the installation and scan instructions in my first post.
All your Verifier Enabled crashes point to memory. One points to audiodg.exe for which you may need to look at Fix: Audiodg.exe High CPU Usage
Security won't cause a memory crash though I don't see why it's necessary. The intel RAID driver doesn't install though since I'm using it as an IDE drive; when running it as AHCI I landed up getting a BSOD literally every minute; I couldn't do anything with it, and that was with all of the drivers installed. I guess I'll pick up some ram or maybe shuffle mine around and see if I get anything out of that. I'll let you know if I have any further problems; thanks so far, I really hope it's something as simple as replacing ram.
I still recommend the security steps, but if you prefer to have an unsecure system, that is your choice.
Viruses/malware can cause any type of crash. Some are designed for this purpose...
Rather than buying new RAM straight away, strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, hard disk, graphics card (or use onboard graphics if you have it), keyboard, mouse, and monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.
As you add and remove hardware, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
bsod caused by ntfs.sys and another page fault in non paged area; only have two sticks of ram in (requires two sticks)... hmm.
If I can get anything to function I'll upload more logs there is no way any viruses or any sort of malware is on the system; it has only visited this forum; and that's with firefox and adblock and noscript too; all the downloads I'm pulling through the network through my laptop. Plus it's still a clean install.. which; I'm thinking about starting from scratch all over again actually. tried to run verifier; special pool detected memory error BSOD.. UGH so annoying! Can't get anything to function.
Hmmm.. interesting; running windows memory diagnostic tools and it says it has detected a hardware problem but doesn't say what.. it just says contact manufacturer.. dumb.. Maybe it will show the 'problems' when the system comes back up.
strange... so far with the two 'main' sticks of RAM it threw a bsod nearly instantly.
with the secondary slot ram sticks in the main (and original main out) it mostly worked... wifi card and graphics card ... were not working AT ALL; it wouldn't let me install drivers or anything.
One original main stick and one .. lucky? secondary stick and so far so well... I'll report once I have issues but.. maybe it was a bad stick somewhere?
I'll let you know when it throws a BSOD if it does. I'd be rather happy if it doesn't though lol!
Your board can run with one stick of RAM.GA-P55A-UD3 User's Manua said:
Well.. all the computer does when I try to boot it with one stick in is just sit there and beep at me; bios doesn't show up or anything.
On plus side.. been playing with it some and still no BSODs....
Glad to see you haven't had BSODs. You may want to contact Gigabyte and find out whether the one stick behavior is normal, though. That is uncommon in my experience, but it could be something specific to your board model. It could also indicate a bad board or incompatible memory.
The randomness of it ... hm. Well, after having zero problems with it, shut it down, went to work on something else, came back; BSOD'd before the desktop was fully loaded. second time.. got a bit further, did the same but different BSOD fault. Third time .. dunno. But here are some new ones.... They all seem to point at memory errors... but why do they function one minute, and fail the next? I don't quite understand... guess that's memory though.
Alright, see if disabling Verifier helps with testing the RAM. Verifier can sometimes generate false positives, so we may want to test how the system performs for a while with it disabled. To disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:verifier /reset-> Restart your computer.
Quote