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 on cold boot no clue this time

27 Jan 2014   #1
bullfights

W764 & W764
 
 
BSOD on cold boot no clue this time

Shut down computer last night and after waking started computer, the BSOD was just after few seconds of hearing familiar windows music just before login, I looked up and BAM, but looked to see what if any files were mentioned, like the last one a few days ago was the nvidia drivers, but didnt see nothing.

I have the SF diagnostics attached.

Thanks

gerry


My System SpecsSystem Spec
.
27 Jan 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Yes, the last BSOD during logon is totally silent about any possible cause. But with 30 programs at startup can cause it.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
Any change in configuration may also cause it. If it recurs, you may try Advanced Boot Options > Last Known Good Configuration.

The bugcheck stop 0xA is usually caused by the following reasons: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. So if possible, plan to update the BIOS to Version 2301 dated 2012.09.29; from ASUSTeK Computer Inc. -Support- Drivers and Download M4A88TD-V EVO/USB3 .

Also, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

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.

Install the latest NVIDIA DRIVERS 314.22WHQL.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
_________________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa000fdc4b60, 2, 1, fffff800044f318f}

Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+9f )

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: fffffa000fdc4b60, 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: fffff800044f318f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000470f100
GetUlongFromAddress: unable to read from fffff8000470f1c0
 fffffa000fdc4b60 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeReleaseSemaphore+9f
fffff800`044f318f 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  LogonUI.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff880026d4680 -- (.trap 0xfffff880026d4680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa000fdc4b60 rbx=0000000000000000 rcx=fffffa000fdc4b60
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800044f318f rsp=fffff880026d4810 rbp=fffffa000fdc4b60
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8a0058e0880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeReleaseSemaphore+0x9f:
fffff800`044f318f 488908          mov     qword ptr [rax],rcx ds:fffffa00`0fdc4b60=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800044d7169 to fffff800044d7bc0

STACK_TEXT:  
fffff880`026d4538 fffff800`044d7169 : 00000000`0000000a fffffa00`0fdc4b60 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`026d4540 fffff800`044d5de0 : 00000000`00000000 00000000`00000001 fffff880`026d46c8 fffffa80`0fdc4b58 : nt!KiBugCheckDispatch+0x69
fffff880`026d4680 fffff800`044f318f : fffff880`03046cc0 fffff880`026d4850 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`026d4810 fffff800`047e3e10 : fffffa80`00000000 fffff8a0`00000001 00000000`00000000 fffff8a0`058e0700 : nt!KeReleaseSemaphore+0x9f
fffff880`026d4890 fffff800`047e55fe : 00000000`00000000 00000000`00000200 fffffa80`1013aad0 fffff800`044daa8a : nt!AlpcpCompleteDispatchMessage+0xa10
fffff880`026d4920 fffff800`047e6071 : 00000000`00010002 fffff8a0`04c7ee78 00000000`00000000 00000000`00000000 : nt!AlpcpDispatchNewMessage+0x24e
fffff880`026d4980 fffff800`047abe13 : 00000000`00000030 fffff880`026d4ae0 00000000`00000000 fffffa80`1013aa00 : nt!AlpcpSendMessage+0x907
fffff880`026d4a90 fffff800`047ac531 : 000007ff`00000000 00000000`00000000 000007fe`fcdb2700 00000000`00000000 : nt!PspExitThread+0x223
fffff880`026d4b90 fffff800`047ac639 : fffffa80`1013aad0 00000000`00000000 fffffa80`1013aad0 00000000`0000ff00 : nt!PspTerminateThreadByPointer+0x4d
fffff880`026d4be0 fffff800`044d6e53 : fffffa80`1013aad0 fffff880`026d4ca0 00000000`770145c0 fffffa80`1003c6d0 : nt!NtTerminateThread+0x45
fffff880`026d4c20 00000000`76f617ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02fbf438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f617ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeReleaseSemaphore+9f
fffff800`044f318f 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeReleaseSemaphore+9f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

FAILURE_BUCKET_ID:  X64_0xA_nt!KeReleaseSemaphore+9f

BUCKET_ID:  X64_0xA_nt!KeReleaseSemaphore+9f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!kereleasesemaphore+9f

FAILURE_ID_HASH:  {f3a81e12-c8c0-c08f-ca6b-de395fe4b101}

Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff8801469a1cc, fffff88005d9f820, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+25e1cc )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8801469a1cc, Address of the instruction which caused the bugcheck
Arg3: fffff88005d9f820, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nvlddmkm+25e1cc
fffff880`1469a1cc 07              ???

CONTEXT:  fffff88005d9f820 -- (.cxr 0xfffff88005d9f820;r)
rax=0000000000000000 rbx=fffffa800f303000 rcx=fffffa800f141000
rdx=0000000000000000 rsi=fffffa800f141000 rdi=fffffa800f141000
rip=fffff8801469a1cc rsp=fffff88005da0208 rbp=000000000000001f
 r8=0000000000000014  r9=0000000000000000 r10=0000000000000000
r11=fffff88014953657 r12=0000000000000001 r13=fffffa800e769a68
r14=fffffa800f2f1000 r15=fffffa800f303000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x25e1cc:
fffff880`1469a1cc 07              ???
Last set context:
rax=0000000000000000 rbx=fffffa800f303000 rcx=fffffa800f141000
rdx=0000000000000000 rsi=fffffa800f141000 rdi=fffffa800f141000
rip=fffff8801469a1cc rsp=fffff88005da0208 rbp=000000000000001f
 r8=0000000000000014  r9=0000000000000000 r10=0000000000000000
r11=fffff88014953657 r12=0000000000000001 r13=fffffa800e769a68
r14=fffffa800f2f1000 r15=fffffa800f303000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x25e1cc:
fffff880`1469a1cc 07              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8801469a1cc

STACK_TEXT:  
fffff880`05da0208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x25e1cc


FOLLOWUP_IP: 
nvlddmkm+25e1cc
fffff880`1469a1cc 07              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+25e1cc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5280da75

STACK_COMMAND:  .cxr 0xfffff88005d9f820 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+25e1cc

BUCKET_ID:  X64_0x3B_nvlddmkm+25e1cc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nvlddmkm+25e1cc

FAILURE_ID_HASH:  {d3a53aff-5c33-8ab5-e555-83559e84884d}

Followup: MachineOwner
---------
My System SpecsSystem Spec
27 Jan 2014   #3
bullfights

W764 & W764
 
 

ok cool I unchecked all from the startup minus the anti-virus, and starts up quicker now lol, didnt know I had that many lol.

I also updated the bios, and am current.

I'll check the ram tonight or next overnight I get, cant do it now as I have to go to wake up at 0200 to drive up to LA from Mexico for work.

Nvidia drivers I have are the latest, had a BSOD and had to update to current for that fix.

I'll check the Video test right now.

keep ya posted thanks
My System SpecsSystem Spec
.

Reply

 BSOD on cold boot no clue this time




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random Freezing/BSOD, Boot Disk Failure, OK Cold Boot then Repeat
Yesterday Windows Explorer began to stop responding fairly frequently, but would restart itself without issue and continue to run fine. Today, Windows now freezes completely every 45ish minutes - usually a random program stops responding followed by everything, the mouse gets stuck,...
BSOD Help and Support
BSOD within minutes of cold boot every time
Every day I come home and boot up my computer, and every day it BSODs either instantly or within 10 minutes, once I restart it seems to be fine and will run for DAYS. Also seems like all of my last systems have been having the same problem, so possibly it's some of the hardware I have been...
BSOD Help and Support
BSOD only on cold boot
Hi everyone, new to the forums so go easy on me :D. I have read about a half dozen similar threads and still have yet to find a solution. I've been an avid computer person who puts together systems in his spare time, and have never seen this problem before. What is happening is each cold...
BSOD Help and Support
BSOD KSOD No Boot Win7 64bit Cold Boot
I'm at my wits end... The problem: First installed Windows 7 Proff 64-bit on this machine last monday after installing updates / drivers etc I began to recieve intermitent BSODs then began the trouble shooting. Tested memory with memtest86+ passed manually set voltages / timings ran...
BSOD Help and Support
BSOD w/cold boot
As w/many posters, I have had the BSOD w/a cold boot recurring for several weeks. It does not occur w/a warm reboot. I haven't installed any new hardware and this issue seems to have arisen spontaneously (something I'm sure you've heard many times before). Per your instructions, I am attaching...
BSOD Help and Support
BSOD on cold boot
Hi, every time I do a cold boot, my computer crashes with bluescreen at exactly the same time, the Win7 loading screen. After this, I turn the computer off, than i turn off the power supply and a few seconds later, I turn it on again. If I now start the computer, it will boot without any...
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 11:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App