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: Random BSOD on new build

30 Dec 2009   #1

Win 7 64 bit
Random BSOD on new build

Have posted previously when the computer was built on an upgrade from XP. I have now built on a fresh HDD and am getting occasional Blue screens. Sometimes when nothing is happening and once when playing a game.

I have attached the minidump files. If someone could take a look and give me some pointers, that woudl be great

Many Thanks


My System SpecsSystem Spec
30 Dec 2009   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by kwack View Post
Have posted previously when the computer was built on an upgrade from XP. I have now built on a fresh HDD and am getting occasional Blue screens. Sometimes when nothing is happening and once when playing a game.

I have attached the minidump files. If someone could take a look and give me some pointers, that woudl be great

Many Thanks


Hi KWack and welcome

Well fairly obvious these were probably caused by memory corruption. Might also be heat. In any case its not sofware because you had these both under the upgrade and clean install

download memtestx86 anr run 5 passes. let us know if it passes or if you get any new bsods

Ken J+

123009-16286-01.dmp    12/30/2009 4:45:40 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    00000002`00000259    00000000`00000002    00000000`00000001    fffff800`02b29abf    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123009-16707-01.dmp    12/30/2009 10:58:02 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    00000000`00000048    00000000`00000002    00000000`00000001    fffff800`02b27abf    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122909-17113-01.dmp    12/29/2009 9:35:18 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041287    00000000`00000038    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\123009-16707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Wed Dec 30 17:56:55.458 2009 (GMT-5)
System Uptime: 0 days 6:11:36.034
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {48, 2, 1, fffff80002b27abf}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

Followup: MachineOwner

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

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.
Arg1: 0000000000000048, 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: fffff80002b27abf, address which referenced memory

Debugging Details:

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0


fffff800`02b27abf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh




PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff880044ec4f0 -- (.trap 0xfffff880044ec4f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0c00000000000020
rdx=0000000000013904 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b27abf rsp=fffff880044ec680 rbp=fffffa8001d252c8
 r8=0000000000013946  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`02b27abf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a76469 to fffff80002a76f00

fffff880`044ec3a8 fffff800`02a76469 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`044ec3b0 fffff800`02a750e0 : 00000000`42506650 02000000`0000f0b3 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`044ec4f0 fffff800`02b27abf : 00000000`0005178f fffffa80`0517efd0 00000000`000018c0 fffff800`02d3bc8f : nt!KiPageFault+0x260
fffff880`044ec680 fffff800`02b2876b : 00000000`00000000 00000000`00000004 fffffa80`0517efe8 fffffa80`0517e000 : nt!MiIdentifyPfn+0x26f
fffff880`044ec720 fffff800`02e880f5 : fffffa80`0517e000 fffff880`044ecca0 fffff880`044ec7f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`044ec760 fffff800`02dccf78 : 00000000`00000006 00000000`00000000 fffffa80`0517e000 fffff800`02a05001 : nt!PfpPfnPrioRequest+0x115
fffff880`044ec7b0 fffff800`02d71cb3 : 00000000`00000000 fffff800`02a05000 fffffa80`0321f000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4853d
fffff880`044ec840 fffff800`02d72e49 : 00000000`0179bd68 00000000`03257e50 00000000`0179bdc0 00000000`0179d3f0 : nt!ExpQuerySystemInformation+0x11c2
fffff880`044ecbe0 fffff800`02a76153 : 00000000`00000000 00000000`02fd7210 fffffa80`0188e601 00000000`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`044ecc20 00000000`7772021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0179bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772021a


fffff800`02b27abf f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh


SYMBOL_NAME:  nt!MiIdentifyPfn+26f

FOLLOWUP_NAME:  MachineOwner



IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f

Followup: MachineOwner
My System SpecsSystem Spec
31 Dec 2009   #3

Win 7 64 bit


Thanks for the advice. I downloaded and ran Memtest for over 6 hours in total and had no errors reported.

I am overclocking the PC and RAM which has never caused any concerns before under XP or Win 7 32bit.

Should I try lowering the overclock or is there another way to check which RAM module has a problem. The OCZ memory does come with a lifetime warranty if my memory servces me right?


My System SpecsSystem Spec

31 Dec 2009   #4
Microsoft MVP


The most effective way to determine if errors are due to the overclock - is to reset the system to stock values.
If the errors go away - then the overclock is to blame.

Additionally, the standard tests are built on the assumption that everything is stable - so it's essential to reset the system to stock values in order to test. OTOH, if you pass Memtest w/the overclock - then it's most likely that RAM isn't the problem.

So, reset the system to stock values and see if you still get BSOD's. If you do, then try running Driver Verifier (because of the SystemService and the PFN stuff in the stack) using these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
04 Jan 2010   #5

Win 7 64 bit

This sounds like a bit too much grief??

I will try running Prime and see how that goes, other than that will lower the overclock and run it for a few days.

I dont think it is heat as it crashed after about 10 minutes from turning it on
My System SpecsSystem Spec

 Random BSOD on new build

Thread Tools

Similar help and support threads
Thread Forum
BSOD at random on new build
OK so I built a system and after a frustrating bout with BSODs caused by a bad mobo (replaced) i finally got it to work. However i was just browsing the interwebs and i got a bluescreen in fact ive gotten several 3 have been stop code 3b Specs Win7 Ultimate AMD FX-4100 ASUS Sabertooth 990FX...
BSOD Help and Support
Random BSOD on new build
Hi, I have a new custom built computer put together by someone I work with. I have been plagued with problems and I think it's hardware related. I got my friend to reinstall Windows but it crashed several times before install completed. He said he tried on my SSD and Samsung HD but still the same...
BSOD Help and Support
New build! Keep getting random BSOD!
I recently build a new computer and installed windows 7. I keep getting random BSOD though. I have reinstalled windows already and ran a memory test. I also tried using driver verifier but whenever I enable it windows automatically gets a BSOD. I have no idea what to do after that so I just restore...
BSOD Help and Support
Random BSoD on new build.
Hi guys First time here,never had this happen before on a build. Put this machine together last week installed OS(retail version 64bit win 7 Pro),after install started getting BSoDs randomly. After much frustration I did a fresh install and all was looking good for a couple of days until I...
BSOD Help and Support
Random BSOD new build!!!!!!why!?!
My 3 month old build is periodically crashing. i have tested the ram with memstest and no errors i have also updated my motherboards bios to the latest version & still no help i have updated to latest video card drivers im not sure whats causing the issues? if i had to guess i was thinking...
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 07:29.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App