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: BSODs - 1000007e & 116

10 Mar 2013   #41
ProdigyGamer

Windows 7 Ultimate x64
 
 

116 BSOD uploaded to SkyDrive: 031113-49623-01

https://skydrive.live.com/#cid=F9598...14D867BA%21115

I had just finished watching a small YouTube Video linked on Facebook, clicked on a new pages and was looking at photo's when my screen went black then power save mode then restarted with a Dump report. This is what always happens.


My System SpecsSystem Spec
.
11 Mar 2013   #42
Saurabh A

Windows 7 64bit
 
 

Hi ProdigyGamer,

Thank you for the reply.

'nvlddmkm.sys' driver causing the same error: 'VIDEO_TDR_FAILURE (116)'
Code:
Loading Dump File [C:\Errors\031113-49623-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03a05000 PsLoadedModuleList = 0xfffff800`03c49670
Debug session time: Mon Mar 11 09:09:08.974 2013 (UTC + 5:30)
System Uptime: 0 days 0:13:16.833
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801a5a6010, fffff880073726c4, ffffffffc000009a, 4}

*** 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+9316c4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801a5a6010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880073726c4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+9316c4
fffff880`073726c4 4055            push    rbp

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08aa2a48 fffff880`07546000 : 00000000`00000116 fffffa80`1a5a6010 fffff880`073726c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08aa2a50 fffff880`07519867 : fffff880`073726c4 fffffa80`24a7e000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08aa2a90 fffff880`07545e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`1a5a6010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`08aa2b40 fffff880`05da7ec1 : fffffa80`1a5a0d50 00000000`00000080 00000000`00000000 fffffa80`225b6410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08aa2bc0 fffff800`03d1b34a : 00000000`068e918e fffffa80`22479b50 fffffa80`1942cb30 fffffa80`22479b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08aa2c00 fffff800`03a6b946 : fffff880`03942180 fffffa80`22479b50 fffff880`0394d1c0 fffffa80`249d3f20 : nt!PspSystemThreadStartup+0x5a
fffff880`08aa2c40 00000000`00000000 : fffff880`08aa3000 fffff880`08a9d000 fffff880`08aa24d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`073726c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
Quote:
Common issues that can cause a TDR:
  • Incorrect memory timings or voltages
  • Insufficient/problematic PSU
  • Corrupt driver install
  • Overheating
  • Unstable overclocks (GPU or CPU)
  • Incorrect MB voltages (generally NB/SB)
  • Faulty graphics card
  • A badly written driver or piece of software, but this is an unlikely cause in most cases
  • Driver conflicts
  • Another possibility is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very 'low FPS'; something graphically complex occurs and the 'GPU' may not be able to respond and a 'TDR error may occur'
Please try the following troubleshooting steps:

1. Try remove the 'display drivers' from 'Device Manager' and try re-installing from 'nVidia website'. Before beginning the uninstall process there are a few things you need to do:
- Stop windows from installing updates automatically. Go to your control panel, then windows upate, then change settings. Change this setting to "Check for updates but let me choose whether to download and install them."
- Disable or turn off any antivirus you have running, especially any that have some sort of real time scanner
- Disable the 'system monitoring software', if installed. Especially the ones that are set to launch when you start Windows. If you are using any of these software to overclock your 'graphics card', you need to return you cards to stock settings
- Go to your control panel and go to programs and features or add/remove programs
- Uninstall the NVIDIA Stereoscopic 3D Driver & NVIDIA PhysX
- Open 'Device Manager' to uninstall the 'nVidia device driver' listed under 'Display Adapters'
- Navigate to C:/NVIDIA/ (And delete the 'DisplayDriver' folder)
- Navigate to C:/Program Files (x86)/ (And delete the entire 'NVIDIA Corporation' folder)
- Go to this folder c:/Windows/System32/DriverStore/FileRepository; delete any folder that begins with 'nv_disp.inf'
- Restart the system in 'Safe Mode' Safe Mode
- Use this tutorial to clean up the residues of the previous display driver: Drivers - Clean Left over Files after Uninstalling
- Restart the system and install fresh display drivers from the 'nVidia website' as before.

2. If you added any new hardware or updated/installed any new drivers immediately before the issue re-occurred, try rolling them back and check results.

3. Run diagnostics on the 'graphics card' and check for abnormal rise in temperature. You may refer to this tutorial: Video Card - Stress Test with Furmark

4. Reset the BIOS to factory defaults.
Restart the system and repeatedly tap 'F2 key' at 'Dell splash screen' to enter the 'system setup'. Tap 'F9 key' to 'restore defaults' and tap 'F10 key' to save settings.

Hope this helps. Do reply with the findings.

My System SpecsSystem Spec
11 Mar 2013   #43
ProdigyGamer

Windows 7 Ultimate x64
 
 

- Go to this folder c:/Windows/System32/DriverStore/FileRepository; delete any folder that begins with 'nv_disp.inf'

I am stuck on this part, I do not have permission now to delete the folder after I did a format and fresh install a few days ago, i used to have this setup so that I was the administrator as I am the only one who uses the PC and it is a home/private PC that is never shared.

Any suggestions? I have tried changing permissions but it will not let me delete the folder and this will become annoying in the future.
My System SpecsSystem Spec
.

11 Mar 2013   #44
Saurabh A

Windows 7 64bit
 
 

Hi ProdigyGamer,

Please try the following steps to see if they help:
- Right click on the folder and go to 'properties'
- A window will pop up and you need to go the 'security' tab
- At the bottom next to where it says 'For special permissions.....' click the 'advanced' button
- Another window will pop up and you need to go the 'owner' tab
- At the bottom of this window, click the 'edit' button and another window will pop up
- You will see a box in this window that says 'Change owner to:' at the top. In this box, click/highlight the name that has 'Administrators' in it
- Cick 'Apply' and then 'OK' to close that window
- Click 'OK' to close the Advanced Security Settings window
- Click 'OK' to close the properties window
- Now, again right click on the folder and go to properties
- Again, a window will pop up and you need to go to the "security" tab
- Click the 'Edit' button next to where it says 'To change permissions, click Edit' and another window will pop up
- In this new window, in the box under where it says 'Group or user names:' click/highlight 'Everyone'
- Now, in the box that says 'Permissions for Everyone', click the box in the 'Allow' Column next to 'Full Control'
- Cilck 'Apply' and then ok to close the window
- Click 'OK' to close the properties window

Hope this helps you change the permissions. Do reply with the results; glad to assist.

My System SpecsSystem Spec
11 Mar 2013   #45
ProdigyGamer

Windows 7 Ultimate x64
 
 

That worked and allowed me to delete the folder, thank you Saurabh.

Continuing with the rest of your instructions now.
My System SpecsSystem Spec
11 Mar 2013   #46
ProdigyGamer

Windows 7 Ultimate x64
 
 

I was able to follow your instructions without issue until I got to the "Furmark - Stress Test point".

First run - just under 2 mins then crash - 031113-35724-01

Recovered from crash and restarted Furmark - Stress Test.

Second run - roughly 20 seconds then crash - 031113-51542-01

Both uploaded to SkyDrive: https://skydrive.live.com/#cid=F9598...14D867BA%21115

Both GPUs got up to around 87c-89c before the first crash after only around 1 min 45 seconds of running test.

Monitor goes blank, then sleep mode then unresponsive then auto reboot with dump report, this is what happens every time now, no more BSODs just black screen/sleep/hibernate mode then auto reboot.

Is there a report from the test I can upload?
My System SpecsSystem Spec
11 Mar 2013   #47
Saurabh A

Windows 7 64bit
 
 

Hi ProdigyGamer,

Thank you for the reply.

The crash dump persists with the same error as before. Since the 'nvlddmkm.sys' driver continues to crash despite 'driver re-installation', it may point at a possible 'hardware issue' with the 'video card'.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801a4be010, fffff880073c16c4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\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
Probably caused by : nvlddmkm.sys ( nvlddmkm+9316c4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801a4be010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880073c16c4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+9316c4
fffff880`073c16c4 4055            push    rbp

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`088eaa48 fffff880`05665000 : 00000000`00000116 fffffa80`1a4be010 fffff880`073c16c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`088eaa50 fffff880`05638867 : fffff880`073c16c4 fffffa80`249b6000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`088eaa90 fffff880`05664e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`1a4be010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`088eab40 fffff880`05733ec1 : fffffa80`21e00560 00000000`00000080 00000000`00000000 fffffa80`231f2410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`088eabc0 fffff800`03d7634a : 00000000`06b8cfc7 fffffa80`24877a00 fffffa80`1942cb30 fffffa80`24877a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`088eac00 fffff800`03ac6946 : fffff880`03942180 fffffa80`24877a00 fffff880`0394d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`088eac40 00000000`00000000 : fffff880`088eb000 fffff880`088e5000 fffff880`088ea4d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`073c16c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
Would recommend you to try the 'Dell Diagnostics' also:
- Restart the system > Repeatedly tap 'F12 key' at 'Dell Splash Screen' to enter the 'BIOS Boot Menu' > Highlight 'Diagnostics' with the 'down arrow key' > Tap 'Enter' (Please check the reference image below)
- Run the 'Quick Test' on the system (It runs by default and scans all system components one by one)
- Also run 'Thorough Test' on the 'Video Card' and capture results. (Option for selecting the 'Thorough Test Mode' is located at the bottom right corner of the screen)



Do reply with the findings; will take it forward.
My System SpecsSystem Spec
11 Mar 2013   #48
ProdigyGamer

Windows 7 Ultimate x64
 
 

I was just about to reboot to Diagnostics when my PC crashed with a c4 error: 031213-44397-01

The PC was idle and had not been used for around an hour or so, then just went into sleep mode, black screen, auto reboot with Dump report which has been uploaded to SkyDrive.

I will try again to reboot into F12 Diag menu, thanks Saurabh.
My System SpecsSystem Spec
12 Mar 2013   #49
Saurabh A

Windows 7 64bit
 
 

Hi ProdigyGamer,

Thank you for the reply.

Please find below the crash dump details:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {62, fffffa80212c4218, fffffa80212c4b20, 3}

*** 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

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

11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: fffffa80212c4218, name of the driver having the issue.
Arg3: fffffa80212c4b20, verifier internal structure with driver information.
Arg4: 0000000000000003, total # of (paged+nonpaged) allocations that weren't freed.
	Type !verifier 3 drivername.sys for info on the allocations
	that were leaked that caused the bugcheck.

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


BUGCHECK_STR:  0xc4_62

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff88005cb5000 nvlddmkm

VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY fffffa80212c4b20
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003f113dc to fffff80003a82c40

STACK_TEXT:  
fffff880`03b55478 fffff800`03f113dc : 00000000`000000c4 00000000`00000062 fffffa80`212c4218 fffffa80`212c4b20 : nt!KeBugCheckEx
fffff880`03b55480 fffff800`03f2054a : 00000000`00000001 00000000`00000000 fffff880`05cb5000 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03b554c0 fffff800`03b75460 : 00000000`00000000 00000000`00000000 fffff880`03942180 00000000`00000000 : nt!VfPoolCheckForLeaks+0x4a
fffff880`03b55500 fffff800`03e3a10e : fffffa80`212c4010 00000000`00000000 00000000`00000000 00000000`00000018 : nt!VfTargetDriversRemove+0x160
fffff880`03b555a0 fffff800`03e5eb33 : 00000000`00000000 00000000`000e0082 00000000`00000000 00000000`00000001 : nt!VfDriverUnloadImage+0x2e
fffff880`03b555d0 fffff800`03e5efad : 00000000`00000000 fffffa80`212c4010 00000000`00000000 00000000`00010200 : nt!MiUnloadSystemImage+0x283
fffff880`03b55640 fffff800`03f00541 : 00000000`00000000 00000000`0000002b fffffa80`194b8de0 00000000`00000018 : nt!MmUnloadSystemImage+0x4d
fffff880`03b55680 fffff800`03a8c174 : 00000000`00000000 00000000`0000002b fffffa80`194b8de0 00000000`00000000 : nt!IopDeleteDriver+0x41
fffff880`03b556b0 fffff800`03cf28f9 : 00000000`0000002b fffffa80`21495040 fffffa80`194b8f30 00000000`00000018 : nt!ObfDereferenceObject+0xd4
fffff880`03b55710 fffff800`03a8c174 : fffffa80`212c4ad0 fffff800`03e70a6e fffff8a0`001b1878 fffffa80`212c4ad0 : nt!IopDeleteDevice+0x49
fffff880`03b55740 fffff800`03b852eb : 00000000`0000002b fffff8a0`001b1870 ffffffff`fff82970 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`03b557a0 fffff800`03e70ad4 : fffffa80`1b5d4740 00000000`00000000 00000000`00000002 fffff800`03e7af10 : nt!PnpRemoveLockedDeviceNode+0x23b
fffff880`03b557f0 fffff800`03e70be0 : 00000000`00000000 fffffa80`1b5d7000 fffff8a0`001f67b0 fffff800`03c87a80 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`03b55820 fffff800`03e70cd9 : fffffa80`20d62002 fffffa80`20d62010 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`03b55890 fffff800`03e70e51 : fffffa80`20d62010 00000000`00000000 fffffa80`20d62010 00000000`00000001 : nt!PnpDelayedRemoveWorker+0x79
fffff880`03b558e0 fffff800`03b85479 : 00000000`00000000 fffffa80`214877f0 00000000`00000001 00000000`00000000 : nt!PnpChainDereferenceComplete+0x131
fffff880`03b55920 fffff800`03f01e60 : 00000000`00000000 fffffa80`1b5d4700 fffff8a0`0015ede0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`03b559a0 fffff800`03f020fc : fffff880`03b55b78 fffff800`03cf2000 00000000`00000000 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`03b55ae0 fffff800`03deb2ce : 00000000`00000000 fffffa80`214910d0 fffff8a0`0015ede0 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03b55b10 fffff800`03a8bca9 : fffff800`03cf1f90 fffff8a0`0015ede0 fffff800`03c292d8 fffffa80`194b0b50 : nt! ?? ::NNGAKEGL::`string'+0x5721b
fffff880`03b55b70 fffff800`03d2334a : 00000000`00000000 fffffa80`194b0b50 00000000`00000080 fffffa80`1942cb30 : nt!ExpWorkerThread+0x111
fffff880`03b55c00 fffff800`03a73946 : fffff880`03942180 fffffa80`194b0b50 fffff880`0394d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b55c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xc4_62_VRF_LEAKED_POOL_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0xc4_62_VRF_LEAKED_POOL_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
It appears that the 'Driver Verifier' is enabled; causing more extra stress on the drivers. Please try to disable 'Driver Verifier' and run the 'Diagnostics'again: Driver Verifier - Enable and Disable

Do reply with the results; will take it forward.

My System SpecsSystem Spec
12 Mar 2013   #50
ProdigyGamer

Windows 7 Ultimate x64
 
 

Sorry about that, I completely forgot I had that on.

It has been disabled, the diagnostics test ran even with it enabled and showed no errors at all. I ran both the normal and thorough versions and everything passed.

I will run Furmark again now that the Verifier tool has been disabled and report back.
My System SpecsSystem Spec
Reply

 BSODs - 1000007e & 116




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSODs or crashes (Error 1000007e bcp1:80000003)
Hello everyone, first post in this website! I ended up here because I'm getting random crashes/bsods, it started months ago. After a while I did a fresh install formatting my hard drive, but I still get those. When I'm working or playing, I get BSODs, but I also notice that whenever putting my...
BSOD Help and Support
1000007e BSOD
I just got a BSOD. I have attached all the information according to this thread : http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html I got a new router, and my internet became messed up. At the beginning of each startup, it would autoconnect to...
BSOD Help and Support
BSOD 1000007e
I have gotten this BSOD at least 4 times over the past few days. I have a HP Pavilion p6654y. It usually occurs after i wake the computer up or sometimes it is just random. I purchased it on 10/10/10. Specs: AMD Athlon II 630 Quad-Core Processor 4GB DDR3 Ram 750GB HDD ATI Radeon HD 4200...
BSOD Help and Support
BSOD:1000007e
Hi all I got a computer recently with Windows 7 Ultimate. I'm having a lot of BSODs especially when I'm playing or when I leave my computer to idle for a long while, and I don't know what to do. When computer has restarted it shows following error message: Problem signature: Problem Event...
BSOD Help and Support
Bsod 1000007e
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1049 Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF88000E6D141 BCP3: FFFFF88003124628
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 15:55.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App