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: BSOD From cold start WIN 7 X 64 Ultimate

14 Dec 2013   #1
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 
BSOD From cold start WIN 7 X 64 Ultimate

Hi everyone,

From my title you can guess I'm having problems from cold start.

If I switch my PC on first thing in the morning I get a lovely BSOD "What Joy" , when I eventually get past the BSOD by reset and selecting start in normal mode it starts up ok. When I've finnished using it I always turn it fully off including mains power, but if I were to turn it on later the same evening it powers up fine as if BSOD never existed.

Every time I've had a BSOD it throws up a different code, I've done a "Who's Crashed" and below are the results



computer name: PETE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 17072349184 total
VM: 2147352576, free: 1934598144




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 14/12/2013 10:38:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121413-7051-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 12/12/2013 10:40:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-6864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BC46090, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/12/2013 14:48:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121113-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BAACDD0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/12/2013 13:54:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121013-5647-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 09/12/2013 13:07:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120913-5896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800B8CE090, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 08/12/2013 10:26:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-5226-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 07/12/2013 13:43:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-4648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800B83FB90, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 07/12/2013 13:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BB7A390, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 07/12/2013 13:41:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-6052-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003186068, 0xFFFFF880031858C0, 0xFFFFF80003091CFB)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 29/11/2013 12:59:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112913-6614-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BC075D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.




Please help, I'm running out of hair to pull out

Thanks in advance

Pete


My System SpecsSystem Spec
.
14 Dec 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Fill up your system specs.
See your system specs and fill it up here.

Publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
My System SpecsSystem Spec
14 Dec 2013   #3
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 

Hi, I have updated my system spec, and added the zip file with all info

thanks again
My System SpecsSystem Spec
.

14 Dec 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Update AMD AHCI Driver V1.2.1.329 for Windows Vista 32bit & Vista 64bit & Win7 32bit & Win7 64bit from ASUSTeK Computer Inc. -Support- Drivers and Download M5A97 LE R2.0.

Make it sure that your SSD is running with the latest firmware.
Samsung SSD (Solid State Drive) 840 series | Samsung SSD Website

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.

Let us know the results.
_____________________________________________________________________________________
Code:
BugCheck 24, {c08a5, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
------------------------------------------------------------------------------
BugCheck 1A, {41790, fffffa800bc46090, ffff, 0}

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

Followup: MachineOwner
---------
My System SpecsSystem Spec
16 Dec 2013   #5
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 

Hi,

I thought I'd update you

I completed a RAM test and it passed ok, no errors.

I checked my SSD was running the latest firmware and thats ok too, I done a cold start this morning and still BSOD, I have now loaded the latest BIOS too see what that brings

Thanks again
My System SpecsSystem Spec
18 Dec 2013   #6
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 

Hi,

System was running ok until this morning, I got the usual windows 7 glowing symbol, then Bam BSOD.

Here's the what crashed report

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 18/12/2013 13:09:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-6302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C1D75D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Aaaaaarrrgh !!
My System SpecsSystem Spec
18 Dec 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
18 Dec 2013   #8
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 

Ok here's the zip file

thanks again
My System SpecsSystem Spec
18 Dec 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If you ran memtest86+ for at least 7 passes and it resulted no 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   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   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   Tip

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

Use !analyze -v to get detailed debugging information.

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

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800c1d75d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LOCK_ADDRESS:  fffff8000327bbe0 -- (!locks fffff8000327bbe0)

Resource @ nt!PiEngineLock (0xfffff8000327bbe0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff8000327bbe0
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800030e8d50 to fffff80003077bc0

STACK_TEXT:  
fffff880`03170848 fffff800`030e8d50 : 00000000`0000001a 00000000`00041790 fffffa80`0c1d75d0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`03170850 fffff800`030aa7d9 : 00000000`00000000 00000000`01180fff fffff880`00000000 fffff800`03077242 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`03170a10 fffff800`03390631 : fffffa80`0d551890 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`03170b30 fffff800`03390a33 : 00000000`00000000 00000000`00540000 fffffa80`00000001 fffff800`03075d00 : nt!MiUnmapViewOfSection+0x1b1
fffff880`03170bf0 fffff800`03076e53 : 00000000`00004800 00000000`0000f53a fffffa80`0c9eb890 00000000`00554800 : nt!NtUnmapViewOfSection+0x5f
fffff880`03170c40 fffff800`03073410 : fffff800`034532c9 00000000`00000000 00000000`00000000 00000000`00100000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03170dd8 fffff800`034532c9 : 00000000`00000000 00000000`00000000 00000000`00100000 fffff880`03171198 : nt!KiServiceLinkage
fffff880`03170de0 fffff800`0345340c : ffffffff`80000134 fffffa80`00100000 00000000`00540000 ffffffff`80000068 : nt!MmCheckSystemImage+0x319
fffff880`03170f10 fffff800`03453627 : ffffffff`80000134 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
fffff880`03170fc0 fffff800`0345f20d : 00000000`00000000 00000000`00000000 fffffa80`0cafc040 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`03171020 fffff800`03461ead : fffff880`03171198 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23d
fffff880`03171140 fffff800`034f6190 : 00000000`00000001 00000000`00000000 fffff880`031716e8 ffffffff`80000158 : nt!IopLoadDriver+0x44d
fffff880`03171410 fffff800`0333276e : 00000000`00000001 00000000`00000000 fffff8a0`0053f730 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`03171510 fffff800`0333247e : ffffffff`80000168 00000000`00000000 fffff880`03171720 fffff880`031716e8 : nt!RtlpCallQueryRegistryRoutine+0x106
fffff880`03171590 fffff800`0346573c : fffffa80`0cb4c6e0 00000000`00000000 00000000`c0000034 fffff880`031716e8 : nt!RtlQueryRegistryValues+0x17e
fffff880`03171660 fffff800`03466ed2 : fffffa80`0cb3e010 fffffa80`0cb4c6e0 00000000`00000002 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`03171810 fffff800`0346736c : fffff800`03279560 00000000`00000000 00000000`00000001 fffff800`032e2e08 : nt!PipProcessDevNodeTree+0x2b2
fffff880`03171a80 fffff800`0317a802 : 00000001`00000003 fffff800`0321d2d8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`03171ad0 fffff800`03081261 : fffff800`0317a500 fffff800`0321d201 fffffa80`0cafc000 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`03171b70 fffff800`033142ea : 00000000`00000000 fffffa80`0cafc040 00000000`00000080 fffffa80`0c9eb890 : nt!ExpWorkerThread+0x111
fffff880`03171c00 fffff800`030688e6 : fffff880`009b3180 fffffa80`0cafc040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03171c40 00000000`00000000 : fffff880`03172000 fffff880`0316c000 fffff880`0316f610 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`030e8d50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Dec 2013   #10
SPUDZNUTS

windows 7 ultimate x64 7601 Multiprocessor Free
 
 

Hi,
I tried running Driver Verifier, but when I do the pc wont start, I get the windows logo and then blank screen. Is this normal?
My System SpecsSystem Spec
Reply

 BSOD From cold start WIN 7 X 64 Ultimate




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD not specific to loading but always within 5 min of cold start
This is driving me crazy, I have a gaming rig which has been fine up until Dec 16. I did update some drivers with the IOrbit Driver program on that day. This is what happens, I get one BSOD from a cold boot within 5-15 minutes, This occurs wither or not I actually log onto windows, windows...
BSOD Help and Support
Assist with bsod cold start
Hi I hope someone can assist me are having cold start blue screen, so I turned of auto restart, to see what blue screen said, IRQL_NOT_LESS_OR EQUAL (forgot to write down the complete set of 0s etc however last set are 0xfffff80002cf3f74 hopefully someone may just kno what this refers to ie...
BSOD Help and Support
P5QL-CM Fresh W7x64 BSOD after COLD Wake/Start
Windows 7 SP1 x64 Pro or Enterprise (tried both) Not-yet-activated (no need, I'm trying to resolve before actually activating...) The build is hmmm a bit more than 2 years old. All errors are with FRESH installs + SP1 + Updates. ASUS P5QL Latest BIOS (was also same problem before with previous...
BSOD Help and Support
BSOD after cold start.
Hello all, I made my own computer in the summer, everything went fine until i turned it off for a night and it took around 20 restarts until it would come back on, just from BSOD's right after the "Windows is loading" black screen with the emblem on it. Here are my system specs DxDiag.txt | Game...
BSOD Help and Support
BSOD during cold start (suspect RAM or Motherboard)
Hi! I get a BSOD or just system freeze/strange crashes of critical windows functions when I start the computer after being switched off for a couple of hours. After 3-5 resets it starts booting fine and running ok. During BSOD I get the following dump file can anyone help me debug this and maybe...
BSOD Help and Support
Warm/Cold Start
When I ask my system to do a warm start i.e. a restart not a shut down it always does a cold start ie as if I had just pressed the start button on the desktop to start my computer. I seem to remember that on XP there was a differance between cold start (boot up) and a warm start. Or am I...
General Discussion


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 10:11.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App