BSOD on first boot every day

lastbuilders · Jan 11, 2010

Hi All,

(Added this in installation and setup thread in error)

I have just built my first PC from scrach and in the main it is going very well. There is one problem whereby when I first start the PC I get a BSOD with a memory_management error. I have run the memory analysis tools and they came back fine. When I restart it after this it is fine.

Error Details

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 6153
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002115E10
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010710-21216-01.dmp
C:\Users\crossonb\AppData\Local\Temp\WER-97344-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hardware Details:
MOBO Gigabyte GA-P55-UD3, Intel P55, ATX, DDR3, PCI-Express

Mem - 4GB-Kit G-Skill PC3-10667U CL9

CPU - Intel Core i5-750 Box 8192Kb

HD - Samsung HD103SI 1TB SATA II EcoGreen, 32MB

Graphics Card - MSI 5750 1024MB, PCI-Express

PSU - Corsair VX450W 450 Watt

Coolness · Jan 11, 2010

lastbuilders said:
Hi All,

(Added this in installation and setup thread in error)

I have just built my first PC from scrach and in the main it is going very well. There is one problem whereby when I first start the PC I get a BSOD with a memory_management error. I have run the memory analysis tools and they came back fine. When I restart it after this it is fine.

Error Details

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 6153
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002115E10
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010710-21216-01.dmp
C:\Users\crossonb\AppData\Local\Temp\WER-97344-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hardware Details:
MOBO Gigabyte GA-P55-UD3, Intel P55, ATX, DDR3, PCI-Express

Mem - 4GB-Kit G-Skill PC3-10667U CL9

CPU - Intel Core i5-750 Box 8192Kb

HD - Samsung HD103SI 1TB SATA II EcoGreen, 32MB

Graphics Card - MSI 5750 1024MB, PCI-Express

PSU - Corsair VX450W 450 Watt

Have you tried to take out one of the RAM sticks? There could be a fault with them. Does all 4gb RAM show in bios?

richc46 · Jan 11, 2010

Until someone with more knowledge regarding the BSOD, try this.

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Also take the memory diagnostic test.

lastbuilders · Jan 11, 2010

Thanks for the replies. All 4GB of ram is showing.

richc46 - When I restart then all is fine so I don't think a clean boot will help isolate the issue.

Thanks,
Lastbuilders

zigzag3143 · Jan 11, 2010

lastbuilders said:
Hi All,

(Added this in installation and setup thread in error)

I have just built my first PC from scrach and in the main it is going very well. There is one problem whereby when I first start the PC I get a BSOD with a memory_management error. I have run the memory analysis tools and they came back fine. When I restart it after this it is fine.

Error Details

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 6153
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002115E10
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010710-21216-01.dmp
C:\Users\crossonb\AppData\Local\Temp\WER-97344-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hardware Details:
MOBO Gigabyte GA-P55-UD3, Intel P55, ATX, DDR3, PCI-Express

Mem - 4GB-Kit G-Skill PC3-10667U CL9

CPU - Intel Core i5-750 Box 8192Kb

HD - Samsung HD103SI 1TB SATA II EcoGreen, 32MB

Graphics Card - MSI 5750 1024MB, PCI-Express

PSU - Corsair VX450W 450 Watt

Hi and welcome

This one was probably caused by memory managent.

I would
download memtestx86 and run 5 passes
run a system file check SFC /SCANNOW

Let us know if that doesnt help

Ken J+

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Thu Jan  7 03:20:35.809 2010 (GMT-5)
System Uptime: 0 days 0:00:29.354
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8002115e10, ffff, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8002115e10
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cfd26e to fffff80002c8af00

STACK_TEXT:  
fffff880`039fb968 fffff800`02cfd26e : 00000000`0000001a 00000000`00041790 fffffa80`02115e10 00000000`0000ffff : nt!KeBugCheckEx
fffff880`039fb970 fffff800`02cccc4a : 00000000`00000000 00000000`0db40fff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`039fbb30 fffff800`02c8a153 : ffffffff`ffffffff 00000000`00bef658 00000000`00bef650 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`039fbc20 00000000`76fb009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bef5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fb009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02cfd26e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

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

lastbuilders · Jan 11, 2010

zigzag3143 said:

lastbuilders said:
Hi All,

(Added this in installation and setup thread in error)

I have just built my first PC from scrach and in the main it is going very well. There is one problem whereby when I first start the PC I get a BSOD with a memory_management error. I have run the memory analysis tools and they came back fine. When I restart it after this it is fine.

Error Details

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 6153
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002115E10
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010710-21216-01.dmp
C:\Users\crossonb\AppData\Local\Temp\WER-97344-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hardware Details:
MOBO Gigabyte GA-P55-UD3, Intel P55, ATX, DDR3, PCI-Express

Mem - 4GB-Kit G-Skill PC3-10667U CL9

CPU - Intel Core i5-750 Box 8192Kb

HD - Samsung HD103SI 1TB SATA II EcoGreen, 32MB

Graphics Card - MSI 5750 1024MB, PCI-Express

PSU - Corsair VX450W 450 Watt

Hi and welcome

This one was probably caused by memory managent.

I would
download memtestx86 and run 5 passes
run a system file check SFC /SCANNOW

Let us know if that doesnt help

Ken J+

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\K\Desktop\010710-21216-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Thu Jan  7 03:20:35.809 2010 (GMT-5)
System Uptime: 0 days 0:00:29.354
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1A, {41790, fffffa8002115e10, ffff, 0}
 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8002115e10
Arg3: 000000000000ffff
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x1a_41790
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  MsMpEng.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from fffff80002cfd26e to fffff80002c8af00
 
STACK_TEXT:  
fffff880`039fb968 fffff800`02cfd26e : 00000000`0000001a 00000000`00041790 fffffa80`02115e10 00000000`0000ffff : nt!KeBugCheckEx
fffff880`039fb970 fffff800`02cccc4a : 00000000`00000000 00000000`0db40fff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`039fbb30 fffff800`02c8a153 : ffffffff`ffffffff 00000000`00bef658 00000000`00bef650 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`039fbc20 00000000`76fb009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bef5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fb009a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02cfd26e cc              int     3
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
 
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
 
BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
 
Followup: MachineOwner
---------

Thanks for the suggestion.

Is this ok for a 64 bit OS?

zigzag3143 · Jan 11, 2010

Memtest is installed to a dvd and run outside windows so it will work on either.

Ken

lastbuilders · Jan 11, 2010

Where would I get memtest from?

computersplus · Jan 11, 2010

Power Supply

even though Corsair makes a very good power supply your may be a little light on over all wattage the video card alone idles about 129 watts by itself.

zigzag3143 · Jan 11, 2010

lastbuilders said:
Where would I get memtest from?

Um from memtest. here Memtest86+ - Advanced Memory Diagnostic Tool

Ken J+

lastbuilders · Jan 15, 2010

Hi all,

Ran memtest and it didn't find any issues but I am now getting a different BSOD message relating to ntfs.sys and PAGE FAULT IN NONPAGED AREA .

I have attached the minidump file.

Lastbuilders

usasma · Jan 16, 2010

NTFS.SYS errors are an error with the file system on your hard drive. There's many possible causes, but these tests will rule out the most common ones.

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

If that doesn't reveal an issue (and if the BSOD's continue) - please run Driver Verifier using these settings:

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

Here's a summary of the BSOD analysis:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 15 04:26:32.610 2010 (GMT-5)
System Uptime: 0 days 0:02:36.155
BugCheck 50, {fffff8a101613c6c, 1, fffff88001258469, 5}
Probably caused by : Ntfs.sys ( Ntfs!memmove+1d9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

lastbuilders · Jan 23, 2010

Just an update that this is still happening but it is back to the memory_management error. Details an minidump attached.

I have tried moving the RAM to another slot.

Details here
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 6153
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000031
BCP2: FFFFFA8005751070
BCP3: FFFFF8800D29C000
BCP4: FFFFF8A00162CE67
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\012310-18829-01.dmp
C:\Users\crossonb\AppData\Local\Temp\WER-34304-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

usasma · Jan 23, 2010

This is not a Driver Verifier enabled minidump. Please continue to run Driver Verifier and post the memory dump files as they occur.

lastbuilders · Feb 10, 2010

Just a follow up that I am still getting this every day. I have attached the minidumps files

computersplus · Feb 10, 2010

you need to up your power supply I said that before you really should read this

Radeon HD 5770 review

lastbuilders · Feb 17, 2010

Just an update.

Changed memory to slots 1 and 3 from 1 and 2 and used optimized BIOS settings and started ok this morning. Will check for few more days to confirm.

Thanks,
Lastbuilders

glennerd · Mar 4, 2010

I have the exact same problem

I built a computer with:
intel p55WG board
intel 17 860 cpu
4gb Gskill 10600 DDR3
Windows 7 Ultimate 64 bit
ATI Radeon HD 4650 Graphics card
BFG 450 Watt power supply

Every day my computer gets the BSoD on boot once or twice before working properly.
I have done memtest and passed every time, I have checked to see if my memory appears in BIOS and it does, I have all new Windows updates, I'm using a genuine retail version of Windows from a disc I was given from Microsoft (I'm a Best Buy employee- but I don't work in computers) for passing a Windows 7 training course. The wattage of my power supply isn't that high, but my Graphics card doesn't need extra power, and wattage is still above recommended wattage for my system.

OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80018DE360
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I click on check for solution when my system recovers, but nothing seems to come back.

Dwarf · Mar 4, 2010

What is your system memory configuration? How many sticks of RAM do you have installed?

vagpower · Apr 14, 2010

I have the same problem...
My config:
I5 750
Asus P7P55D Deluxe
2x2gb ddr3 Gskill 1600mHz CL7
nvidia 8800GT
LC Power Arkangel 850W
Windows 7 64bits

BSOD on first boot every day

New member

My Computer My Computer

Mr Anderson

My Computer My Computer

Moderator

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

Mr. Cranky Pants

My Computer My Computer

New member

My Computer My Computer

Mr. Cranky Pants

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

The Contemplator, (1963-2013)

My Computer My Computer

New member

My Computer My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer