Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Custom Built Computer - Random BSOD

10 Apr 2014   #1

Windows7 Professional 64Bit
Custom Built Computer - Random BSOD

Hi team,

I built my own computer a few weeks ago, after a few days I started getting the BSOD randomly. I have never had the time to sit and troubleshoot the issue until now.

I have tested the RAM but this did not help the issue.
I have performed a clean install of Windows 7
My machine has up to date drivers
My machine has up to date Windows Updates
I have ran SFC /SCANNOW
C:\Windows\system32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
My computer does not look like it is over heating

Dump File : 040914-57500-01.dmp
Crash Time : 09/04/2014 16:18:04
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : nvstor.sys
Caused By Address : nvstor.sys+16385
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\040914-57500-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 300,979
Dump File Time : 09/04/2014 16:19:33

My System SpecsSystem Spec
10 Apr 2014   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

How many passes did you take memtest for?

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

Loading Dump File [C:\Users\Yusra\Downloads\DPC4LF-10_04_2014__91543_41\040914-57500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02819000 PsLoadedModuleList = 0xfffff800`02a5c6d0
Debug session time: Wed Apr  9 21:18:04.183 2014 (UTC + 6:00)
System Uptime: 0 days 3:18:31.201
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 38, 0, 0}

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

Followup: MachineOwner

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

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
    Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000038
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:

BUGCHECK_STR:  0x1a_41287



PROCESS_NAME:  CcmExec.exe


TRAP_FRAME:  fffff88003139900 -- (.trap 0xfffff88003139900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004c2e0c8 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a004003120 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002995a87 rsp=fffff88003139a90 rbp=0000000000000000
 r8=fffffa8004a1001a  r9=fffffa800644b048 r10=fffffa800558e010
r11=fffffa80055793b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff800`02995a87 8b4138          mov     eax,dword ptr [rcx+38h] ds:00000000`00000038=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002827d2e to fffff8000288ebc0

fffff880`03139798 fffff800`02827d2e : 00000000`0000001a 00000000`00041287 00000000`00000038 00000000`00000000 : nt!KeBugCheckEx
fffff880`031397a0 fffff800`0288ccee : 00000000`00000000 00000000`00000038 fffff8a0`050ee300 00000000`000c241a : nt! ?? ::FNODOBFM::`string'+0x454f5
fffff880`03139900 fffff800`02995a87 : 00000000`00000000 fffffa80`0558e050 00000000`00000002 fffff880`009e97f0 : nt!KiPageFault+0x16e
fffff880`03139a90 fffff800`0290ff73 : fffffa80`04a13060 00000003`00000000 00000000`00000000 fffffa80`04c2e0c8 : nt!MiEmptyPageAccessLog+0xe7
fffff880`03139b00 fffff800`02878b06 : 00000000`00002e89 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4c84b
fffff880`03139b80 fffff800`02878fb3 : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`02b2b2ea : fffffa80`0370e040 00000000`00000080 fffffa80`036ea040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`0287f8e6 : fffff800`02a09e80 fffffa80`0370e040 fffff800`02a17cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`03139840 00000000`00000000 : nt!KxStartSystemThread+0x16


nt! ?? ::FNODOBFM::`string'+454f5
fffff800`02827d2e cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+454f5

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5

Followup: MachineOwner
I suggest you test your RAM again in the following way.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

My System SpecsSystem Spec

 Custom Built Computer - Random BSOD

Thread Tools

Similar help and support threads
Thread Forum
BSOD Random, Custom Built Comp, not by me
Have had BSOD's in the past, but it seems like it is happening more often. I used to play games like Need For Speed Most Wanted, and I wouldn't have an issue. Now I will just be watching a Plex on my computer and I'll get a random BSOD. I don't know much of anything about BIOS, so I've never...
BSOD Help and Support
BSOD custom built computer not shure what to due, randomly happens.
Just built this computer and had no problem and out of no where after a couple weeks i started getting bsod ive done "sfc /scannow" no discrepancy ive scanned multiple things including the harddrive, virus scan and entire computer with nothing coming up i included sf debug files as i do not know...
BSOD Help and Support
Various BSoD's on Custom Built Computer
Hello, A small bit of history first: The computer in question is a custom build that I had been using for around 5 years with no problems at all. I then gave it to my sister after a complete format, and she has started to experience many BSoD's with it. Please note that only the internal...
BSOD Help and Support
random BSOD on my custom-built PC
Hi, I got a BSOD as soon as I woke my pc up from sleep. I also got a second BSOD after I restarted my PC a few moments later. Here is the message that I got in case it might be of any use: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601. Locale ID: 1033...
BSOD Help and Support
0x0000001e BSOD on custom built computer
I recently built a new computer and have been getting between 1 and 4 BSODs a day. They seem to occur at no particular occasion when I am not doing a particular task. I have had blue screens when the computer is idle, when playing a game. Can someone please help me find out the issue here?
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:26.
Twitter Facebook Google+