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: 1000007e

15 Jun 2012   #1

Windows 7 Ultimate x64
 
 
BSOD: 1000007e

Hi,

I'm getting BSOD crashes intermittently, but strangely enough only when my PC is idle.
Error log below, and dump file attached.

Thanks very much in advance.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 7177

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800033CCB6B
BCP3: FFFFF880031FC898
BCP4: FFFFF880031FC100
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\061512-27144-01.dmp
C:\Users\Vurkmoord\AppData\Local\Temp\WER-24622480-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

My System SpecsSystem Spec
.

15 Jun 2012   #2

Windows 8.1 Pro x64
 
 

Outdated drivers are likely the cause here.

Update those:
Razer Tarantula Keyboard Driver Razer Support
AMD Display driver AMD Graphics Drivers & Software
Atheros Extensible Wireless LAN ATHEROS Wireless drivers for Windows (Or from System Manufacturer's website)

Uninstall those software:
Asus Update, Asus PC-Probe

Post back with any new dumps if BSODs still occur.
Code:
*******************************************************************************
*                                                                             *
*                        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: fffff800033ccb6b, The address that the exception occurred at
Arg3: fffff880031fc898, Exception Record Address
Arg4: fffff880031fc100, 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!IopDeleteFile+24b
fffff800`033ccb6b 488b09          mov     rcx,qword ptr [rcx]

EXCEPTION_RECORD:  fffff880031fc898 -- (.exr 0xfffff880031fc898)
ExceptionAddress: fffff800033ccb6b (nt!IopDeleteFile+0x000000000000024b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000008000000000
Attempt to read from address 0000008000000000

CONTEXT:  fffff880031fc100 -- (.cxr 0xfffff880031fc100)
rax=fffff8a01b038a70 rbx=fffffa800ae081d0 rcx=0000008000000000
rdx=fffff88002f64180 rsi=fffffa8006d2d600 rdi=fffffa8007e17030
rip=fffff800033ccb6b rsp=fffff880031fcad0 rbp=0000000000000001
 r8=0000000000000003  r9=0000000000000110 r10=fffff8000304c000
r11=0000000000000189 r12=fffffa8007c549a0 r13=fffff8a01be79a00
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!IopDeleteFile+0x24b:
fffff800`033ccb6b 488b09          mov     rcx,qword ptr [rcx] ds:002b:00000080`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  0000000000000000

EXCEPTION_PARAMETER2:  0000008000000000

READ_ADDRESS:  0000008000000000 

FOLLOWUP_IP: 
nt!IopDeleteFile+24b
fffff800`033ccb6b 488b09          mov     rcx,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff800030c0604 to fffff800033ccb6b

STACK_TEXT:  
fffff880`031fcad0 fffff800`030c0604 : 00000000`00000000 00000000`00000000 fffffa80`06d2d600 00000000`00000000 : nt!IopDeleteFile+0x24b
fffff880`031fcb60 fffff800`033a79e5 : 00000000`00000000 00000000`0008c081 fffffa80`0addbbc0 fffffa80`0008c081 : nt!ObfDereferenceObject+0xd4
fffff880`031fcbc0 fffff800`031e347b : fffffa80`0addbbc8 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0xa1
fffff880`031fcc00 fffff800`031e3aed : 00000000`00000000 00000000`00000080 fffffa80`06d1d040 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`031fccc0 fffff800`0335b6e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`0309a566 : fffff880`02f64180 fffffa80`06d3c040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc800 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!IopDeleteFile+24b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f7912ee

STACK_COMMAND:  .cxr 0xfffff880031fc100 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!IopDeleteFile+24b

BUCKET_ID:  X64_0x7E_nt!IopDeleteFile+24b

Followup: MachineOwner
---------
My System SpecsSystem Spec
15 Jun 2012   #3

Windows 7 Ultimate x64
 
 

Thanks very much for the quick response.

Could you maybe help me out with how to find the model number for the Atheros Wireless Chip?
I've googled around but can't seem to find a way to identifyu which driver to download.

Thanks!
My System SpecsSystem Spec
.


15 Jun 2012   #4

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by staticvoidlol View Post
Thanks very much for the quick response.

Could you maybe help me out with how to find the model number for the Atheros Wireless Chip?
I've googled around but can't seem to find a way to identifyu which driver to download.

Thanks!
Open Device Manager and search for the Device ID/Model Number, I can't tell you the exact model since I have no information on your hardware.
My System SpecsSystem Spec
Reply

 BSOD: 1000007e




Thread Tools



Similar help and support threads for2: BSOD: 1000007e
Thread Forum
1000007e BSOD BSOD Help and Support
BSOD BCCode: 1000007e please help! BSOD Help and Support
BSOD Crash 1000007e BSOD Help and Support
BSOD 1000007e BSOD Help and Support
BSOD:1000007e BSOD Help and Support
Bsod 1000007e 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 10:52 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