Mem management, bad pool header, & other BSODs after 7 x64 install

Just bought a used 'built' computer from a nice on a car forum I'm part of, he's been great with contact, and with me on this whole journey of problems. He never had a single problem with this computer after building it and using it. Of course when he sends off his baby in the mail, something happens and now I'm having NUMEROUS problems. For a while I was throwing BSODs left and right within seconds of restarts, even with the system idling it would throw BSODs for no apparent reason. I was running the main drive which is an SSD in AHCI mode, and he mentioned he left the BIOS at default settings, so I reset it all to IDE, reinstalled windows, and my problems have been alleviated; but for the past few hours (just got this computer last Friday so been trying to get it up and running for work to be done) I've been getting quite a few bsods; but not nearly as many as before. Besides the uploads, some other things I've noticed which have been odd, opening and closing Java will lock up the system (or rather run the i5 too 100% across the board), then I will get a BSOD and a system restart. Sometimes firefox will absolutely randomly crash on me for no reason, again.. when it's idling, it just freaks out. Twice now I've noticed 7 will drop out of Aero mode and into the 'basic' non-clear graphics, and sometimes my wifi card will drop out entirely for a minute or two and act like there isn't one. I know a fair amount of computers, or rather used to, but I'm absolutely no good at debugging or figuring out what is causing BSOD errors or what... so hopefully someone here can help me out! Thanks. windows 7 home premium 64bit intel i5 750 Nvidia 460 GTX corsair 8gb ram corsair 64gb ssd & 1tb hdd 1 day old windows install with adobe suite, only drivers _I_ have installed have been the nvidia graphics driver, I let windows choose what I need; so far that's been working .. longest. 0 updates have been put on the windows install either. Something else to mention, I ran memtest86+ for a good 14 hours (14 passes) and it came up with 0 errors. Hopefully some logs will make sense of the issues I'm having because I have no clue what is causing any of this. If you need any other in formation let me know! Thanks again for anyone who helps!

Just trying to let the system handle basic things and it's throwing bsods, but at least these are clean ones.

Not sure what the first bsod read, but I KNOW the second one was memory management, was just playing Minecraft and had firefox running in the background; nothing else is going on with the system, I don't understand.

I need this computer to be running solid within two weeks, any help is greatly appreciated.

Problem Devices:

Code:

Ethernet Controller	PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_06\4&43FAD29&0&00E1	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_50071458&REV_03\4&304316D0&0&00E2	The drivers for this device are not installed.

I would recommend installing the driver for the above as a first step. NOTE: The below links are for rev. 2.0 of your motherboard. If you have rev. 1.0, the below link has a link within it to that board as well.

• GIGABYTE - Motherboard - Socket 1156 - GA-P55A-UD3 (rev. 2.0) -> Downloads -> Driver -> Windows 7 64bit -> Intel INF installation
• GIGABYTE - Motherboard - Socket 1156 - GA-P55A-UD3 (rev. 2.0) -> Downloads -> Driver -> Windows 7 64bit -> Realtek LAN Driver
• GIGABYTE - Motherboard - Socket 1156 - GA-P55A-UD3 (rev. 2.0) -> Downloads -> Driver -> Windows 7 64bit -> NEC USB 3.0 Driver

Security Software: ??? I recommend either of these two setups:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• Good and Free system security combination.

Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.


The crashes seem to be pointing to bad RAM, but there could also be an underlying driver conflicting with the system to cause the same crashes. It may also be hard disk corruption.

Code:

Event[1671]:
  Log Name: System
  Source: Ntfs
  Date: 2012-04-23T19:31:46.059
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Andrew-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume MyBook.

• Run Disk Check with both boxes checked for MyBook. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  If you do not get the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

If you do not use your MyBook drive often, or if fixing the disk errors on it does not resolve the crashes, then proceed to the following steps to see if memory or a driver is at fault for the crashes.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. 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.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 208994
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready 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.

had one crash after installing a driver, then during the verifier it wouldn't boot the OS, let it fail twice, then let it come back. Perfmon failed like 10 times; not sure why but it finally did work this last time :/ not sure.

You need to go ahead and run memtest86 now, per the instructions writhziden has already posted for you. If you do have bad memory, which I highly suspect, you need to resolve that issue before you can successfully complete his other instructions.

I have; 12 passes and 0 errors; I guess it won't hurt to run it again tonight but I highly doubt it will show anything. I've run memtest86+ quite a few times, even two sticks at a time (mobo requires two sticks), and after a few tests still nothing. I have no problem replacing the RAM, I just want to know that's the problem; I don't want to spend $50 on ram a week after buying this computer and find out that wasn't the problem lol! I just find it odd the previous owner literally was just using it and had zero problems with it the whole time he had it, and once I get it connected nothing really works :/ oh well, hopefully that last zip will have some info behind whatever is going wrong with this thing.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\XCNuse\nuse426\Windows_NT6_BSOD_jcgriff2\042612-12074-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030ab650
Debug session time: Thu Apr 26 17:47:43.782 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:10.171
Loading Kernel Symbols
...............................................................
............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e1, fffff98001402f9c, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\uim_vimx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for uim_vimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uim_vimx64.sys
Probably caused by : uim_vimx64.sys ( uim_vimx64+1a2ce )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e1, Synchronization object address is bogus or pageable.
Arg2: fffff98001402f9c, Synchronization object address.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_e1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000336c3dc to fffff80002ee3c80

STACK_TEXT:  
fffff880`031a1568 fffff800`0336c3dc : 00000000`000000c4 00000000`000000e1 fffff980`01402f9c 00000000`00000000 : nt!KeBugCheckEx
fffff880`031a1570 fffff800`0336f028 : 00000000`00000000 00000000`00000000 00000000`00000005 00000000`00000004 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031a15b0 fffff800`03373491 : 00000000`004d4955 fffffa80`0674b980 fffff880`03fc49f8 fffff800`03374a46 : nt!VfUtilSynchronizationObjectSanityChecks+0x88
fffff880`031a15f0 fffff880`03fc52ce : fffff980`01402f6c fffff980`01402f6c 00000000`00000010 00000000`00010282 : nt!VerifierKeInitializeEvent+0x21
fffff880`031a1620 fffff980`01402f6c : fffff980`01402f6c 00000000`00000010 00000000`00010282 00000000`00000000 : uim_vimx64+0x1a2ce
fffff880`031a1628 fffff980`01402f6c : 00000000`00000010 00000000`00010282 00000000`00000000 fffff880`03fc2d58 : 0xfffff980`01402f6c
fffff880`031a1630 00000000`00000010 : 00000000`00010282 00000000`00000000 fffff880`03fc2d58 fffffa80`0674b980 : 0xfffff980`01402f6c
fffff880`031a1638 00000000`00010282 : 00000000`00000000 fffff880`03fc2d58 fffffa80`0674b980 fffffa80`0904db80 : 0x10
fffff880`031a1640 00000000`00000000 : fffff880`03fc2d58 fffffa80`0674b980 fffffa80`0904db80 fffffa80`0904dcd0 : 0x10282


STACK_COMMAND:  kb

FOLLOWUP_IP: 
uim_vimx64+1a2ce
fffff880`03fc52ce ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  uim_vimx64+1a2ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: uim_vimx64

IMAGE_NAME:  uim_vimx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e5c2063

FAILURE_BUCKET_ID:  X64_0xc4_e1_VRF_uim_vimx64+1a2ce

BUCKET_ID:  X64_0xc4_e1_VRF_uim_vimx64+1a2ce

Followup: MachineOwner
---------

Verifier enabled crashes indicate Paragon Image Mounter with faulty drivers. Please remove the Paragon software for the time being. I do not know if it is the software itself, a corrupted install of the software, or a bad image. The software appears to be corrupted and a re-install may resolve the issue. However, as a testing step, remove the software completely through Start Menu -> Control Panel -> Uninstall a program and re-enable Verifier to test.

Haven't gotten a chance to do verifier, I will have to tomorrow; I ran memtest with a wall time of 24 hours and it showed zero errors so.... Was a busy day, didn't have time to really work on the computer tonight but can certainly get to it tomorrow to test out driver verifier again and remove paragon (which really shouldn't be the problem but I can uninstall it anyway) I will say; there have been a few times chkdsk has run during startup and some files WERE removed / reinstated so.... yeah, not sure what's going on there... Maybe the SSD is going back? Do SSDs just .. go bad like that? Don't they have a break down time where errors will begin to show up? I find it odd one week it worked, the next week I received computer it just craps out. I just don't know, I don't keep up with computer and the technology anymore

It is not common for SSDs to go bad. They usually arrive working or not working.

Make sure your SSD firmware, your motherboard BIOS, the Chipset drivers, and the hard disk controller drivers are up to date.
Corsair Support
GIGABYTE - Motherboard - Socket 1156 - GA-P55A-UD3 (rev. 2.0) -> Downloads -> Windows 7 64bit -> BIOS, Chipset, SATA Intel® drivers
Avoid the Marvell drivers for now as they may cause problems with the SSD.


Also, run Disk Check with Automatically fix file system errors checked. Post back the logs for the disk check by using Check Disk (chkdsk) - Read Event Viewer Log to find the logs.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

thought all was going well! then.. nope! Fail..