Gpt/uefi bsod

So I've finally got my new GPT/UEFI sytsem to run the windows install. However when it comes time to set up a desktop and computer name I get the Blue screen. Any input? Have tried and failed the same way 4 times.

-also before when I had it operational and running as an MBR it would blue screen randomly.
-I cant post logs because I haven't even set up my desktop yet

Are you able to boot into Safe Mode at all? Do you have a Windows 7 installation DVD or System Repair disc?

-update- I removed 2 dimms and was able to finally get my desktop created. However after the motherboard driver installation went through it's first system restart I got the BSOD as soon as the point where the windows loading screen would come up came along. I did a hard reboot and successfully logged in and installed the rest of the drivers for the mother board and haven't crashed yet. No I was not able to boot into safe mode while the instillation process is incomplete.

Since you able to boot into Windows, please follow - Blue Screen of Death (BSOD) Posting Instructions

here are some crash logs

BSOD Analysis:

Code:

BugCheck 1A, {41790, fffffa8004dabb20, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )

Code:

Usual causes:  Device driver, memory, kernel

The bugcheck indicates that a serve memory management issue has occurred, more specifically from parameter one (in blue) we can see that the page table has become corrupt. The other parameters indicate that the reference count for the number of used PTE's has dropped below zero, leading to a fatal error. This is usually caused by drivers unlocking pages more times than it was locked.

Code:

8: kd> dt nt!_MMPFN fffffa8004dabb20
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40000798 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`40000798 Void
   +0x010 Lock             : 0n1073743768
   +0x010 PteLong          : 0xfffff6fb`40000798
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

When a page is locked, the reference count is incremented, and then decremented when the device driver unlocks the page, unlocking a page more often than locking the page, will cause the reference count to drop below zero.

----------------------------------------------------------------------

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Install Service Pack 1:

• Learn how to install Windows 7 Service Pack 1 (SP1)

Service Pack 1 has provided many security and stability updates for Windows 7, which would be highly beneficial for your system.

crashed as soon as i booted. couldn't even login with verifier running

Code:

BugCheck C4, {83, 5354414d, 8, 53544}

*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Probably caused by : AppleCharger.sys ( AppleCharger+1df0 )

The driver has called MmMapIoSpace without locking any MDLs to describe the physical page layout for virtual memory used by device drivers.

Code:

0: kd> k
Child-SP          RetAddr           Call Site
fffff880`009a9368 fffff800`0e95a4ec nt!KeBugCheckEx
fffff880`009a9370 fffff800`0e95ad63 nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a93b0 fffff800`0e96bab6 nt!MmCheckMapIoSpace+0xe3
fffff880`009a9400 fffff880`053b2df0 nt!VerifierMmMapIoSpace+0x46 <-- Bugcheck
fffff880`009a9440 00000000`5354414d AppleCharger+0x1df0
fffff880`009a9448 fffff880`06f9d3d8 0x5354414d
fffff880`009a9450 00000000`00000034 0xfffff880`06f9d3d8
fffff880`009a9458 00000000`00000002 0x34
fffff880`009a9460 00000000`0000001c 0x2
fffff880`009a9468 fffff980`016d6fd0 0x1c
fffff880`009a9470 ffffffff`80000180 0xfffff980`016d6fd0
fffff880`009a9478 00000000`00000001 0xffffffff`80000180
fffff880`009a9480 fffffa80`1210fd60 0x1
fffff880`009a9488 fffff880`06f66000 0xfffffa80`1210fd60
fffff880`009a9490 00000000`00000000 0xfffff880`06f66000

Code:

0: kd> lmvm AppleCharger
start             end                 module name
fffff880`053b1000 fffff880`053b9000   AppleCharger T (no symbols)           
    Loaded symbol image file: AppleCharger.sys
    Image path: \SystemRoot\system32\DRIVERS\AppleCharger.sys
    Image name: AppleCharger.sys
    Timestamp:        Wed Nov 02 02:46:00 2011 (4EB0AEE8)
    CheckSum:         0000C20A
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Gigabyte On/Off Charge driver is causing problems, and is a well known cause for BSODs with Windows 7 and Windows 8, please remove the program or driver completely from your system.

removed.... let's see what happens.

Okay thanks, just leave this thread open for a few days, and report back if you have any crashes.