Solved Gpt/uefi bsod

[ShadowFalls]

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.

:edit: also before when I had it operational and running as an MBR it would blue screen randomly.

 

[gregrocker]

I would upload the BSOD Crash dump file to a post in our Crashes forum for expert analysis. This is going to be the quickest way to get to the cause. Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Forums

Meanwhile you can go over your new install closely using the Troubleshooting Steps for Windows 7

 

[ShadowFalls]

I would upload the dump files except I haven't even created a desktop to explore my drives yet

 

[gregrocker]

Unplug all other HD's and peripherals,

Boot into BIOS setup, reset to defaults, save changes. (If an EFI BIOS you'll need to decide if you want UEFI BIOS vs. Legacy BIOS. If UEFI follow these special steps for Install, otherwise enable Legacy BIOS or Compatibility Support Module to proceed with normal install.) Set DVD drive first to boot, HD second, set SATA controller to AHCI, Save changes and Exit.

Then boot into Windows 7 installer DVD or flash stick burned or written using tool and latest ISO for your licensed OS version here.

At first installer screen Press Shift + F10, or enter System Recovery Options to open a Command Box, type:

DISKPART
LIST DISK
SELECT DISK 0 (after confirming Windows 7 target HD #)
CLEAN
CREATE PARTITION PRIMARY
FORMAT FS=NTFS LABEL="WINDOWS 7"
ACTIVE
EXIT
EXIT

Next click Install Now, then Custom install to Clean Install Windows 7 to the partition you created. If it fails then report back at which step and the verbatim error message.

In addition read over these steps to understand the tools and methods which work best to get and maintain a perfect Clean Reinstall - Factory OEM Windows 7. The steps are the same for retail.

After install you can adjust partition size or Create new partitions for data, etc. in Disk Mgmt. You are creating the partition here for the purpose of wiping the HD and marking Active which overcomes certain install failures.



If this won't get you any further before the BSOD then I'd access the dump file using the same method as to access Device Manager - Access During Windows 7 Installation. In fact it's worth checking if there are erroring drivers to disable to see if install will complete.

 

[ShadowFalls]

the EUFI install is the one I'm trying to do because I want to make full use of all 4tb of my hard drive with no unnecessary partitions which the legacy bios would do because of the lack of support for booting off of ghp format drives and only booting off of MBR which partitions every 2TB. The issue is at step 11 on http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html I get the BSOD.

 

[gregrocker]

If you've tried the steps above which avoid most installation problems, then what do you find when you enter Device Manager during install to disable any erroring (!) devices?

Can you access the Crash Dump at the log file will be %systemroot%\Minidump which is normally C:\windows\Minidump

if the files don't exist then setup your system to record them:

1. Go to Start and type in sysdm.cpl and press Enter
2. Click on the Advanced tab
3. Click on the Startup and Recovery Settings button
4. Ensure that Automatically restart is unchecked
5. Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
6. Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later

See if you can run the collection tool there in Safe Mode: Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Forums then post to our Crashes forum and link it here.

 

[ShadowFalls]

I was able to create a desktop so now I should be able to upload the dump. I'll flow your first post and thanks.​

 

[ShadowFalls]

my next post will have the logs from the bsod

 

[gregrocker]

What exactly did you do that allowed you to complete install to the desktop?

Did you disable an erroring Driver in Dev Mgr? That may have solved your crashing, too.

Has it crashed since?

 

[ShadowFalls]

I removed 2 dimms. I still got the BSOD but only after I was done creating the desktop and was logged on.

 

[gregrocker]

Then in addition test your RAM - Test with Memtest86+ for 5-6 passes or overnight. Test both sticks and slots as shown. Blow any debris out of slots.

 

[ShadowFalls]

here are some crash logs. Ill do that memory test now and get back to you.

 

[TVeblen]

It sounds like you have RAM problems. You should run Memtest as Gregrocker suggests before you do anything else. Report back what you find.

If Memtest reports any errors you can stop the test. In that case you should test each stick of RAM individually in the first RAM slot (usually A1) to determine if just one stick is bad.

If all the sticks are bad in slot A1 then you could have a defective RAM slot. In that case test each stick in the first second channel slot (usually A2).

You do not list the brand and model of RAM in your specs. Have you checked to see if that RAM is compatible with that motherboard and CPU?
On your motherboard's website there will be a page where they list their QVL for the board. This is the Qualified Vendors List of RAM that has been tested and approved for the board. You don't have to buy only the RAM on the list, but whatever RAM you buy must meet all of the specifications of the RAM on the list. Pay particular attention to the voltages.

I also noticed that you posted in Hardware asking for recommendations for 64GB of RAM. (I don't do shopping advice). Don't go there until you have done the tests and have determined the cause of the RAM problems.

 

[ShadowFalls]

Alright, another guy told me to run "verifier" which when i did wouldn't even let me log in without a BSOD. I had to go into safe mode to disable it. So here aer the results from that. Now i'm going to do the memory test. Also you should know that currently my memory is 2 dimms that are a 4gb and a 2gb. If I put all in I will have (2) 4gb dimms and (2) 2gb dimms

 

[gregrocker]

Do you have another thread open here, and why? Please link it so we know what else is being done.

 

[ShadowFalls]

Yea I took your advice and opened up a new thread in BSOD Help and Support
here's the link http://www.sevenforums.com/bsod-help-support/297815-gpt-uefi-bsod.html

Also I took out the 2gb dimm and replaced it with a 4gb so now I only have (2) 4gb dimms installed

 

[gregrocker]

Is it stable with that RAM config so far? If not try another, and complete the RAM testing according to the tutorial and with TVeblen's help.

At the same time work with Harry in your other thread to trace the driver crash. It may still be RAM related, but work with Harry to find his own cause since a different process is used reading BSOD's.

 

[ShadowFalls]

I literally just did this so we'll see what happens. After the memory test I might run verifier again to see if I can boot up without crashing with this ram config.

 

[TVeblen]

If it is Driver Verifier you are running, that program torture tests drivers. A great tool. But it's purpose is to find and identify problematic device drivers. The only way it won't crash to bluescreen is if you have no faulty drivers.
So keep on with the BSOD guys, if there is a software problem, they will find it!

The RAM issue is a separate test. There are no drivers for RAM. It is pure BIOS-level hardware. So you are working on this separately from the BSOD stuff. (They can be related, surely, but for testing treat them separately). RAM should install and test out fine without an operating system installed at all.

Can you list here the brand and specs of all your current RAM?

 

[ShadowFalls]

2 I have in my case right now Amazon.com : ADATA Gaming Series DDR3 1600Mhz 8 GB Kit 2 x 4 GB CL9 Desktop Memory AX3U1600GC4G9-2G : Computer Internal Memory : Electronics
2 i took out Amazon.com: ADATA DDR3 1600Mhz 4GB Kit 2 x 2GB CL9 Desktop Memory AX3U1600GB2G9-2G: Electronics still get bsod... still testing memory