BSOD error BCC 7f, BCP1 0000000000000008

Sebruz · 24 Jul 2013

I am having problems with my computer first freezing for about 30 seconds, and then rebooting by itself. After this occurance the following info is given:

Ongelmatapahtuman nimi: BlueScreen
Käyttöjärjestelmän versio: 6.1.7601.2.1.0.768.3
Aluekohtaisten asetusten tunnus: 1035

Lisätietoja ongelmasta:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002E94974
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

(It's in Finnish, but It's not really hard to know what they mean.)
This happens almost every time I start my computer, I log in and use the desktop for a while, then my mouse coursor won't move, the whole screen freezes and it reboots. After the first time it usually runs pretty well, and I can use my computer without problems for several hours with some luck. At some point though, sooner or later, it happens again. If I have any sound on while it happens, the sound will continue after the screen freezes and eventually turn into loud static noice. I've had this computer for 4+ years, and it has happened once or twice during the last 6 months, but recently it has started happening very much.

I checked the system logs and tried to find errors that occur around the same time as my computer has been crashing. I found the following:
Critical Event: Kernel power 41 (63), These seem to have occured during all the crashes. I've ran system diagnostics, and they showed nothing. I also ran Memcheck through an usb-drive to check my systems memory, but it didn't find anything either. I've read some other forums about this matter, but can't say I'm sure of what to do. Please help!

Sebruz · 24 Jul 2013

Here is the information gathered with the SF tool.

Arc · 24 Jul 2013

It appears that the display driver is failing here.

Code:

fffff880`02332158  fffff880`059f2b47Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1b8b47

And the driver is somehow old.

Code:

fffff880`0583a000 fffff880`062e1000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jan 18 18:52:15 2013 (50F94C87)
    CheckSum:         00A92B69
    ImageSize:        00AA7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install the latest WHQL only.

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
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Also do the following things:

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

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe. Also let us know th wattage of the PSU.
______________________________________________________________________________________
BSOD ANALYSIS:

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002e9d974}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002e9d974

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e931a9 to fffff80002e93c00

STACK_TEXT:  
fffff880`03370de8 fffff800`02e931a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`03370df0 fffff800`02e91672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03370f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02e91672 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

HPE-345sc, 05/19/2010

Sebruz · 24 Jul 2013

I have now uninstalled my previous nvidia items and installed the 314.22 WHQL, however I wasn't able to uncheck the installation of the 3D vision controller driver. I also wiped the left over driver files. Remains to be seen if the problem persists, I havent checked my computers temperature, power nor stresstessed the graphics card yet (the last one I've already done earlier though, and the results were quite satisfying). If no BlueScreens occur during the next few days I will mark the problem as solved, and if so, thanks a ton for your help!

Arc · 24 Jul 2013

We need to know the system temperature and the wattage of the PSU, as yours a branded desktop, and a few years old. Without checking those, we cannot conclude at anything.

And the health of the GPU too.

Better you let us know those information too.

Sebruz · 24 Jul 2013

Here are the results of speccy:
Attachment 277932

Sebruz · 24 Jul 2013

My computer crashed again, so seems like the Nvidia stuff didn't solve it alone at least. I ran the furmark test, and it got to around 80 celsius before my screen froze and I had to force a shutdown. Average fps was 6.
I'm not sure how exactly I should be checking if my power supply is enough for the needs of my computer, I visited the page but I really don't know all of the details that you have to fill in.

Sebruz · 24 Jul 2013

Recently received another blue screen after removing the old nvidia components and it replaced them with defaults:
BCCode: 50
BCP1: FFFFF88006B76000

Arc · 24 Jul 2013

Sebruz said:

My computer crashed again, so seems like the Nvidia stuff didn't solve it alone at least. I ran the furmark test, and it got to around 80 celsius before my screen froze and I had to force a shutdown. Average fps was 6.
I'm not sure how exactly I should be checking if my power supply is enough for the needs of my computer, I visited the page but I really don't know all of the details that you have to fill in.

Need to know the wattage of your PSU. GPU is failing for sure, but the power it is obtaining from the PSU is also a required info.

And, only you can say it by verifying it physically.