BSOD on start up, freezing on boot

Hello, i didnt get a chance to use that new tool because the computer that BSOD on me is at my office and i am not there till monday, but i was able to grab the minidump file anyway

specs:
AMD FX4100
Gigabyte 990 motherboard
8 GB DDR3 1600 corsair
550 Watt PSU
750GB WD Cavier Black
Windows 7 Ultimate 64

i had updated the bios cause i figured that was what was causing the BSOD. i have random freezes on start up and then i finally got a BSOD

im thinking its the motherboard cause i built this computer recently but changed the HD to a bigger one so that might be it also. sometimes i can use it for hours and not have an issue, sometimes it will just random freeze, any help would be appreciated.

it was a page fault

here is the minidump

Hello lovewin7yea.

It appears thet BSODs are frequent for you? Was checking the threads you started earlier.

Is it the only BSOD you faced lately? If not, some more information will be good. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

But if it is a single BSOD occurred lately, your crash dump is not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
______________________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88009cc15f8, 0, fffff80004573617, 0}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88009cc15f8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80004573617, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046bf100
GetUlongFromAddress: unable to read from fffff800046bf1c0
 fffff88009cc15f8 Nonpaged pool

FAULTING_IP: 
nt!EtwpLogKernelEvent+1c7
fffff800`04573617 448b9424c8000800 mov     r10d,dword ptr [rsp+800C8h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009c413a0 -- (.trap 0xfffff88009c413a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006dd6e80 rbx=0000000000000000 rcx=fffffa8006dd6e80
rdx=fffffe0002e6a7d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004573617 rsp=fffff88009c41530 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=006500780065002e
r11=fffffa8006dd6e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!EtwpLogKernelEvent+0x1c7:
fffff800`04573617 448b9424c8000800 mov     r10d,dword ptr [rsp+800C8h] ss:0018:fffff880`09cc15f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004505be0 to fffff80004487c00

STACK_TEXT:  
fffff880`09c41238 fffff800`04505be0 : 00000000`00000050 fffff880`09cc15f8 00000000`00000000 fffff880`09c413a0 : nt!KeBugCheckEx
fffff880`09c41240 fffff800`04485d2e : 00000000`00000000 fffff880`09cc15f8 fffffa80`08253900 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`09c413a0 fffff800`04573617 : 00000000`00001000 00000000`00000001 00000000`00000000 fffff880`09c41568 : nt!KiPageFault+0x16e
fffff880`09c41530 fffff800`045738a6 : 00000000`00000004 00000000`00000000 00000000`00000002 fffff800`044683ba : nt!EtwpLogKernelEvent+0x1c7
fffff880`09c415d0 fffff800`047c6c35 : 00000000`00000000 fffff800`04636d20 00000000`000012cc fffff800`045bbd0e : nt!EtwpTraceKernelEvent+0xa6
fffff880`09c41620 fffff800`047a8b98 : 00000000`000000b2 fffff880`09c417a0 00000000`00000001 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x1c8e8
fffff880`09c41700 fffff800`0477939d : 00000000`00000000 fffff880`09c41b60 00000000`00000001 fffffa80`0949c620 : nt!PsCallImageNotifyRoutines+0xdc
fffff880`09c41760 fffff800`047771e2 : fffffa80`07277060 fffffa80`07277060 00000000`14050800 00000000`7efde000 : nt!DbgkCreateThread+0x151
fffff880`09c41940 fffff800`04478a35 : fffff880`009ec180 00000000`00000000 fffff800`04777154 fffffa80`07277060 : nt!PspUserThreadStartup+0x8e
fffff880`09c419a0 fffff800`044789b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`09c41ae0 00000000`77b2c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0027f588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b2c500


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000457361d - nt!EtwpLogKernelEvent+1cd
    [ 00:08 ]
1 error : !nt (fffff8000457361d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

actually, last BSOD i posted was a year from this date. And i try to keep all my drivers updated, as i stated, i just built this a few months ago so it was working pretty good, then i started getting lock ups and finally 2 BSOD 2 weeks apart, now it seems i cant even use the computer unless its in safe mode which doesnt freeze (obviously)

i will goto my office tomorrow and use that and edit my main post with an update, i was going to go to the river but decided i will just stay home this weekend. thanks for your response.

Lol ... it it not broken, better to not fix it.

If you want to get the drivers updated, upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

An old crash dump will provide the old information only.