BSOD Shortly After Began Using New Build

[slodoc259]

Greetings,

Thanks for being here. I've learned a lot even before this post.

I built this system about a month ago. Started having blue screens during the Windows Update process. They continue to occur fairly frequently often while the computer is just sitting. Here's the file data. I'm about to update my Mobo drivers. AFAIK I've got the most current Invidia driver and all Windows updates have been downloaded and installed. Most current version of NIS is also installed. The SSD firmware has not been updated. I use Ccleaner to remove registry problems.

Thanks for the help.
View attachment 287283

 

[Arc]

The system fails to record BSOD dumps.

Event[25457]:
  Log Name: System
  Source: volmgr
  Date: 2013-09-25T10:48:22.869
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Build6
[COLOR=Red]  Description: 
Crash dump initialization failed![/COLOR]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[slodoc259]

Sorry for the delay. I set up a dump file as you suggested, had a blue screen then couldn't find %SystemRoot% or %SystemRoot%\MEMORY.DMP. When I googled the file for location it didn't help. Where can I find the file to send? Or can I specify a different location?

 

[Teerex]

Did you by any chance disable the pagefile?

 

[slodoc259]

I did.

 

[slodoc259]

I restored the page file. Is there a specific size I should set it at? Also, is it important that the system restart immediately after a blue screen? I had it set to not so I could see the stop codes.

 

[Arc]

Sorry for the delay. I set up a dump file as you suggested, had a blue screen then couldn't find %SystemRoot% or %SystemRoot%\MEMORY.DMP. When I googled the file for location it didn't help. Where can I find the file to send? Or can I specify a different location?

C:\Windows\Minidump ..... it is the root if you browse to it. But we need you tp post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Teerex]

I restored the page file. Is there a specific size I should set it at? Also, is it important that the system restart immediately after a blue screen? I had it set to not so I could see the stop codes.

A dump can't be saved without a pagefile. Leave the size to Windows.

You had a pagefile when the BSODs started, right?

 

[slodoc259]

Yes. The first BSOD occurred during the windows update process before I got rid of the page file.

 

[slodoc259]

Page file was recreated.

Also, SSD firmware updated and BIOS flashed successfully to V9. I tried to update my MB drivers from the Gigabyte website with varying degrees of success.

Here's the data from the latest BSOD which occurred after the above changes. It occurred while surfing the internet.

 

[slodoc259]

Bump for help.

 

[slodoc259]

Dump file posted

Good morning,

Posted the dump file about 4 days ago and wondered if someone would look at it.

Thanks.

 

[Arc]

Hi slodoc259. I did not post there as I wanted to avoid any chance of conflict of suggestions.

The BSOD 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 it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

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.
____________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80c031f8a0, 2, 1, fffff800036ba150}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80c031f8a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800036ba150, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038cc100
GetUlongFromAddress: unable to read from fffff800038cc1c0
 fffffa80c031f8a0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`036ba150 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff8800d097350 -- (.trap 0xfffff8800d097350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=000000000cee9010 rsi=0000000000000000 rdi=0000000000000000
rip=00000000024caefc rsp=00000000003def70 rbp=00000000003def78
 r8=000000000000002b  r9=0000000074ee5758 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
0023:024caefc ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003694129 to fffff80003694b80

STACK_TEXT:  
fffff880`0d096d88 fffff800`03694129 : 00000000`0000000a fffffa80`c031f8a0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d096d90 fffff800`03692da0 : fffffa80`1160db50 00000000`00000000 00000000`02170000 fffffa80`c031f890 : nt!KiBugCheckDispatch+0x69
fffff880`0d096ed0 fffff800`036ba150 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0d097060 fffff800`036b890f : fffffa80`0cbd0078 00000000`00000003 fffffa80`00321090 00000000`00000003 : nt!MiReplenishPageSlist+0xc0
fffff880`0d0970d0 fffff800`036a2044 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`0d0971f0 fffff800`03692cae : 00000000`00000001 00000000`0cee9000 00000000`00000001 00000000`0c412d78 : nt!MmAccessFault+0x1224
fffff880`0d097350 00000000`024caefc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`003def70 fffff800`0368c1d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x24caefc
fffff880`0d097530 00000000`ffffffff : fffff8a0`136d3810 fffff880`0d097900 fffff8a0`13182530 00000000`00000200 : nt!KiCallUserMode
fffff880`0d097538 fffff8a0`136d3810 : fffff880`0d097900 fffff8a0`13182530 00000000`00000200 fffff880`0d097c70 : 0xffffffff
fffff880`0d097540 fffff880`0d097900 : fffff8a0`13182530 00000000`00000200 fffff880`0d097c70 00000000`0000ffc0 : 0xfffff8a0`136d3810
fffff880`0d097548 fffff8a0`13182530 : 00000000`00000200 fffff880`0d097c70 00000000`0000ffc0 00000000`0000ffc0 : 0xfffff880`0d097900
fffff880`0d097550 00000000`00000200 : fffff880`0d097c70 00000000`0000ffc0 00000000`0000ffc0 414b7740`3ffffffa : 0xfffff8a0`13182530
fffff880`0d097558 fffff880`0d097c70 : 00000000`0000ffc0 00000000`0000ffc0 414b7740`3ffffffa 00000000`00000000 : 0x200
fffff880`0d097560 00000000`0000ffc0 : 00000000`0000ffc0 414b7740`3ffffffa 00000000`00000000 00000000`00000000 : 0xfffff880`0d097c70
fffff880`0d097568 00000000`0000ffc0 : 414b7740`3ffffffa 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffc0
fffff880`0d097570 414b7740`3ffffffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffc0
fffff880`0d097578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x414b7740`3ffffffa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+c0
fffff800`036ba150 f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

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