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 when watching a movie, or randomly


14 Mar 2013   #1

Windows 7 64 bits + Ubuntu 12
 
 
BSOD when watching a movie, or randomly (error code: 0x0000007E)

Hi everyone.
I've recently experienced some BSOD but I don't really know how to debug them so I hope that I'm providing you with all the information that you need to help me.

The BSOD's can occur randomly (it once happened when starting the computer), but today was second time in three days that it occured while I was watching a movie (and nothing else was running on the computer).

I've began to follow these instructions BSOD Randomly/Mainly during Video playback but I don't know how to interpret the disk check. I uploaded the disk check report (sorry it's in French...).

Thank you for your help, please tell me if there is anything else I can do to make it easier for you to help me.


My System SpecsSystem Spec
.

14 Mar 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for the next BSOD. When it takes place, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

In the mean time, Free up the startup.
  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.
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.
Uninstall Trend Micro. It often causes BSODs due to various reasons. Using two different real time antivirus programs at the same time is even harmful. Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
My System SpecsSystem Spec
14 Mar 2013   #3

Windows 7 64 bits + Ubuntu 12
 
 

Alright, thank you!
However my dump files settings were already set at Kernel memory dump (it was also set this way before the BSOD I guess...I didn't need to change the settings) but the Minidump folder is empty.

I am going to follow your advices for the rest, thank you again!
My System SpecsSystem Spec
.


18 Mar 2013   #4

Windows 7 64 bits + Ubuntu 12
 
 

It happened again...My laptop restarted before I could note the error code. I'm uploading another zip. I wonder if you can't find the crash dump in it because of my bi boot. When the computer restarts it goes automatically on the boot menu (something like that =>http://images.anandtech.com/reviews/.../pcdl/boot.jpg) but I can't restart from there so I have to restart it manually.
I updated the first post for the files

PS: sorry about the double post. Should I edit my previous post next time?
My System SpecsSystem Spec
20 Mar 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
21 Mar 2013   #6

Windows 7 64 bits + Ubuntu 12
 
 

I have done what you said and a BSoD occured as expected. I have now disabled DV. The good news is that this time I have a crash dump file. I've also taken a picture of the BSoD. I've added the files to my first post.
My System SpecsSystem Spec
21 Mar 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

The crash dump looks different.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800037692d4, fffff8800371d948, fffff8800371d1a0}

Probably caused by : ntkrnlmp.exe ( nt!ViPendingCompleteAfterWait+64 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800037692d4, The address that the exception occurred at
Arg3: fffff8800371d948, Exception Record Address
Arg4: fffff8800371d1a0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ViPendingCompleteAfterWait+64
fffff800`037692d4 4c8b5df0        mov     r11,qword ptr [rbp-10h]

EXCEPTION_RECORD:  fffff8800371d948 -- (.exr 0xfffff8800371d948)
ExceptionAddress: fffff800037692d4 (nt!ViPendingCompleteAfterWait+0x0000000000000064)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to unknown address 0000000000000000

CONTEXT:  fffff8800371d1a0 -- (.cxr 0xfffff8800371d1a0)
rax=fffffa800a6f1160 rbx=fffffa800a6f4660 rcx=fffffa800a6f4661
rdx=fffffa800a6f1161 rsi=fffff9801244e790 rdi=fffffa800a5869a0
rip=fffff800037692d4 rsp=fffff8800371db80 rbp=6767676767676767
 r8=fffffa800a6f1160  r9=0000000000000000 r10=fffff80003778740
r11=fffffa800a6f4660 r12=fffff8000346ed30 r13=fffff80003769340
r14=0000000000000000 r15=fffff880009edf40
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ViPendingCompleteAfterWait+0x64:
fffff800`037692d4 4c8b5df0        mov     r11,qword ptr [rbp-10h] ss:0018:67676767`67676757=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  ffffffffffffffff

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f8100
GetUlongFromAddress: unable to read from fffff800034f81c0
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
nt!ViPendingCompleteAfterWait+64
fffff800`037692d4 4c8b5df0        mov     r11,qword ptr [rbp-10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000376936c to fffff800037692d4

STACK_TEXT:  
fffff880`0371db80 fffff800`0376936c : fffff800`0346ed30 00000000`00000080 fffffa80`03cde5f0 ffffffff`ffffff00 : nt!ViPendingCompleteAfterWait+0x64
fffff880`0371dbc0 fffff800`0356034a : 00000000`00000000 ffbbbfff`bffff7fd 00000000`00004000 ffffffff`ffffffff : nt!ViPendingWorkerThread+0x2c
fffff880`0371dc00 fffff800`032b0946 : fffff880`009e9180 fffffa80`03d0fb50 fffff880`009f3fc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`0371dc40 00000000`00000000 : fffff880`0371e000 fffff880`03718000 fffff880`0371d8d0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ViPendingCompleteAfterWait+64

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

STACK_COMMAND:  .cxr 0xfffff8800371d1a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_VRF_nt!ViPendingCompleteAfterWait+64

BUCKET_ID:  X64_0x7E_VRF_nt!ViPendingCompleteAfterWait+64

Followup: MachineOwner
---------
And it does not says that it is crashed within a driver verifier enabled environment, too. Anyway, as you said that you enabled driver verifier, I am depending that statement.

This crash dump somehow is not indicating any driver (system or third party) as the reason behind the crash. At the same time it is not very clear that it is a hardware driven BSOD.

A stop 0x1000007E and a stop 0x7E bears almost the same meaning. According to Carrona.org, STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:
Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Update the firmware of your SanDisk U100 128GB SSD.

The disc space left in C is somehow not very sufficient. Free up some space.
ITEM VALUE
Lecteur C:
Capacité 77,06 Go (82 743 128 064 octets)
Espace libre 10,22 Go (10 970 259 456 octets)
Back up some data to the external.

The display driver is very old.
Code:
fffff880`05a25000 fffff880`065e2660   igdkmd64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Fri Oct 21 22:59:55 2011 (4EA1AC13)
    CheckSum:         00BC8CF3
    ImageSize:        00BBD660
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Some data in the event log indicates (though I dont know French ) the the computer is overheating. 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. In case, you may need to buy a cooling pad for it.

BIOS update is also needed here:
Code:
Version du BIOS/Date    American Megatrends Inc. UX31E.210, 26/12/2011
Get the BIOS update from ASUS.

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.

Stress test the CPU.
Hardware - Stress Test With Prime95

Scan the system for possible virus infection.
Download and install this version of Intel Rapid Storage.

Let us know when all the suggested changes are done and all the suggested tests are taken.
My System SpecsSystem Spec
Reply

 BSOD when watching a movie, or randomly




Thread Tools



Similar help and support threads for2: BSOD when watching a movie, or randomly
Thread Forum
BSOD watching movie, MEMORY_MANAGEMENT BSOD Help and Support
BSOD WHILE PLAYING fifa 13 AS WELL AS WATCHING MOVIE BSOD Help and Support
BSOD While Playing Games Or Watching movie (3D) BSOD Help and Support
BSOD while watching a movie. BSOD Help and Support
Random bsod while watching a movie BSOD Help and Support
BSOD while browsing net and watching movie BSOD Help and Support
Bsod Screen When Iam Watching Movie 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 12:19 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33