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 only occurs in normal mode, Works fine on safe mode.


27 May 2013   #1
Soqu

Windows 7 Home Premium 64bit
 
 
BSOD only occurs in normal mode, Works fine on safe mode.

Everytime i open my pc up in normal mode, it seems to restart itself within a few seconds to a few minutes, It tends to happen when i open up a program like Chrome. I',m currently on safe mode with networking and have done registry cleaners, updated video card drivers and looked for viruses, yet nothing has seemed wrong, I've also done a system restore to when my pc was working fine, but it still was happening, I saw on another post here that i should post my msinfo32 so here you go, Thanks.


My System SpecsSystem Spec
27 May 2013   #2
Soqu

Windows 7 Home Premium 64bit
 
 

Just tried opening in normal mode again, got a blue screen within 2 minutes. Didn't open chrome, only programs i had opened was mozilla firefox, and startup programs
My System SpecsSystem Spec
27 May 2013   #3
Soqu

Windows 7 Home Premium 64bit
 
 

here is the SF Diagnostic Tool v5 thing
My System SpecsSystem Spec
27 May 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

It is a driver bug.

The computer thinks it is Driver Verifier enabled. Stop code 0xC4 occurs only when it is Driver Verifier enabled.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
But actually it is not driver verifier enabled. See here ...
Code:
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
If DV is actually enabled, the value would have been "VERIFIER_ENABLED_VISTA_MINIDUMP"

So the situation is not normal, and we have more reason to believe that it is a buggy driver. See here, in the arguments ...
Code:
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa8006c04060
Arg4: 0000000000000000
Now, the question is .... which driver is buggy? From the dump data, it is your display driver.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa8006c04060, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b775d )

Followup: MachineOwner
---------
The particular version you have installed and the driver earlier to this one behaves in the same way. We have noticed it many a times in the past. Here what you need to do is to remove the display driver totally from your system, and install the latest one.

Install the latest WHQL only.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
  • Double click to open it.
  • Click this button only:
  • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
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.
Let us know the results.
My System SpecsSystem Spec
27 May 2013   #5
Soqu

Windows 7 Home Premium 64bit
 
 

Hey man, Thanks for the help. I reinstalled the video drivers, and updated them again, and i also began windows free of startup, no blue screen has shown up yet so i think it worked, I'll let you know if it happens again though! Thanks for the help, - Soqu
My System SpecsSystem Spec
27 May 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Let us know the situation after a couple of days
My System SpecsSystem Spec
Reply

 BSOD only occurs in normal mode, Works fine on safe mode.




Thread Tools




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 09:28 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App