Multiple crashes with no reason

Shadowcast · Sep 6, 2010

Greetings,

I seem to be having quite a few issues with BSOD's and i can't seem to figure out the reason.

The error i get most often is: 0x0000003B: SYSTEM_SERVICE_EXCEPTION

I've attached the latest dumps.

Any help is appreciated.

Thank you,
Shadowcast

ttran · Sep 6, 2010

Hi Shadowcast!

There are different stop codes with different things were blamed including graphic card driver as well as directx. First thing to try is to re-install the graphic card driver. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Update directX as well:
Download details: DirectX End-User Runtime

Remove Kaspersky for testing purpose:
Removal tool for Kaspersky Lab products
Install MSE for testing, it is known for BSODs free:
Security Essentials Software Support | Microsoft Security Essentials

Run system file check and let us know the result please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Looks like almost every dmp suggest memory access violation, please check for your RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

Code:

BugCheck D1, {0, 2, 0, fffff8800167d6f4}

Probably caused by : wanarp.sys ( wanarp!WanNdisReceivePackets+317 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff9600026605f, fffff88003a8e880, 0}

Probably caused by : win32k.sys ( win32k+23605f )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050031, 6f8, fffff80002c8d8fb}

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

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff88001061494, fffff88002660ac0, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpCacheCreateNames+2a4 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff88005175554, fffff88008036d58, fffff880080365c0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchSubmitCommand+204 )

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

Regard,

Tuan

Shadowcast · Sep 7, 2010

Hello and thank you for your quick reply.

I've went ahead and installed a new copy of Win. 7 x64 Ultimate to make sure it's a clean install.

Obviously enough, the system file check was ok.

As for the memory check, i`m just getting ready to run it, but meanwhile i still got a new BSOD, the only one since i reinstalled that is. I've attached the dump.

Thank you,

Shadowcast

Later edit: I've ran the memory test and i let it load for around 7 passes and got no errors so i guess that it's not the ram's fault...

ttran · Sep 7, 2010

Hi there,

Your Realtek Ethernet driver, Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver. was out of date and should be updated

Code:

fffff880`041c6000 fffff880`041f8000   Rt64win7 Rt64win7.sys Thu Feb 26 16:04:13 2009 (49A65B0D)
fffff880`04000000 fffff880`04014000   Rtnic64  Rtnic64.sys  Mon Mar 31 12:39:38 2008 (47F0791A)

Realtek

Did you use memtestx86 to test your RAM?

If after updating the driver and BSODs keep pursuing, please enable driver verifier:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\tuan_pc\Desktop\090710-20810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a94e50
Debug session time: Tue Sep  7 18:44:37.481 2010 (UTC + 7:00)
System Uptime: 0 days 0:13:24.229
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa80060b8630, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )

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

Regard,

Tuan

Shadowcast · Sep 7, 2010

Yes, i did use memtestx86 to test the ram. I've let it run for about 7 passes and didn't get any errors...

At the moment everything seems to be running fine, but in case of a new BSOD i will come back and post the new dump.

Until then, thank you for your help

Shadowcast

L.E.: Scratch that, just got a new one. Dump attached

CarlTR6 · Sep 7, 2010

This is a hardware/hardware related crash.

Error code 18, REFERENCE_BY_POINTER - usual causes are device driver, kernel, hardware.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\090710-20810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a94e50
Debug session time: Tue Sep  7 07:44:37.481 2010 (GMT-4)
System Uptime: 0 days 0:13:24.229
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa80060b8630, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa80060b8630, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000285efdc to fffff800028c7740

STACK_TEXT:  
fffff880`08541ad8 fffff800`0285efdc : 00000000`00000018 00000000`00000000 fffffa80`060b8630 00000000`00000002 : nt!KeBugCheckEx
fffff880`08541ae0 fffff800`029cd4b9 : fffffa80`060b8630 fffffa80`041ac000 fffffa80`041acd50 fffffa80`041acd48 : nt! ?? ::FNODOBFM::`string'+0x46411
fffff880`08541b40 fffff800`02d186ae : fffffa80`0000071d fffffa80`04da3000 fffffa80`060b8630 fffffa80`041acd50 : nt!MmFreeAccessPfnBuffer+0x29
fffff880`08541b70 fffff800`02d39cd0 : fffffa80`06b4f001 00000000`00000080 fffffa80`03ccf040 fffff800`02a55568 : nt!PfpFlushBuffers+0x23e
fffff880`08541c10 fffff800`02b6bc06 : ffffffff`ff676980 fffffa80`06b4f060 fffff880`08541db0 fffffa80`06b4f060 : nt!PfTLoggingWorker+0xe0
fffff880`08541d40 fffff800`028a5c26 : fffff880`02f63180 fffffa80`06b4f060 fffff880`02f6dfc0 fffff880`01247a90 : nt!PspSystemThreadStartup+0x5a
fffff880`08541d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46411
fffff800`0285efdc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46411

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46411

BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46411

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

The dump indicates your ATI drivers are involved; however these drivers are up to date.

I do find an older driver on your system along with an obsolete driver. Generally speaking, Win 7 does not like obsolete drivers. They can and do cause conflicts, memory corruption and crashes.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek LAN driver, Realtek

Rtnic64.sys Mon Mar 31 01:39:38 2008 - Realtek Ethernet NIC driver Realtek

As Ttran suggested, update these two Reatek drivers, especially that 2008 driver. It may not be the cause of your crash; but it is not helping the stability of your system.

Post back if you need help updating. After you update, reboot your system and see how it runs. If you get another BSOD, upload the dump file and enable Driver Verifier following the instructions in this tutorial:

Driver Verifier - Enable and Disable

If Driver Verifier finds a faulty driver, it will trigger a BSOD. Upload any Driver Verifier enabled dump files. Hopefully the dump(s) will point to the offending driver.

Shadowcast · Sep 7, 2010

Well, i did update the drivers, then ran the driver verifier, got no BSOD and seems to be running just fine at the moment...

I also reduced the OC from my CPU as i read that it might be the cause of the issues as well.

All fine for now but i will keep you posted.

Thank you for your help,

Shadowcast

CarlTR6 · Sep 7, 2010

You are welcome; I'm glad we could help. It's good news that you are running smoothly and we hope that countinues. That was good detective work to reduce the OC. That can most definitely cause issues. If you get another BSOD, please upload it. I suspect that it was the obsolete drivers plus overclocking that gave your the trouble.

Shadowcast · Sep 8, 2010

Well, it didn't last too long as i got another one, but whatever the cause, the pc is far more stable than before ...

I've attached the new dump

Thank you,

Shadowcast

ttran · Sep 8, 2010

Are you still having Driver Verifier on? If so, turn it off please.
Also, can you please run system file check again?
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

CarlTR6 · Sep 8, 2010

I am glad we are making progress; that is good news. But we want to get you BSOD free.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Code:

Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Tue Sep  7 20:28:21.261 2010 (GMT-4)
System Uptime: 0 days 0:41:56.712
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800104391f, 0, 58434ffe}

Probably caused by : fltmgr.sys ( fltmgr!FltpPassThrough+f )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800104391f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000058434ffe, Parameter 1 of the exception

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


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

FAULTING_IP: 
fltmgr!FltpPassThrough+f
fffff880`0104391f 498bb0b8000000  mov     rsi,qword ptr [r8+0B8h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000058434ffe

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0
 0000000058434ffe 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002849d08 -- (.exr 0xfffff88002849d08)
ExceptionAddress: fffff8800104391f (fltmgr!FltpPassThrough+0x000000000000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000058434ffe
Attempt to read from address 0000000058434ffe

TRAP_FRAME:  fffff88002849db0 -- (.trap 0xfffff88002849db0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004dd8010 rbx=0000000000000000 rcx=fffff88002849fe0
rdx=fffffa8004752a40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800104391f rsp=fffff88002849f40 rbp=0000000000000001
 r8=0000000058434f46  r9=000000000000000c r10=fffffa8003d21090
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr!FltpPassThrough+0xf:
fffff880`0104391f 498bb0b8000000  mov     rsi,qword ptr [r8+0B8h] ds:f000:00000000`58434ffe=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b09a39 to fffff80002acf740

STACK_TEXT:  
fffff880`02849538 fffff800`02b09a39 : 00000000`0000001e ffffffff`c0000005 fffff880`0104391f 00000000`00000000 : nt!KeBugCheckEx
fffff880`02849540 fffff800`02aced82 : fffff880`02849d08 fffff880`02849fe0 fffff880`02849db0 fffffa80`056ad330 : nt!KiDispatchException+0x1b9
fffff880`02849bd0 fffff800`02acd8fa : 00000000`00000000 fffff880`02849fe0 fffffa80`0510a000 fffff800`02c81300 : nt!KiExceptionDispatch+0xc2
fffff880`02849db0 fffff880`0104391f : fffffa80`00004001 fffffa80`065e80b8 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`02849f40 fffff880`010426c7 : 00000000`00000001 fffff800`02dd49f0 fffff880`0284a100 00000000`00000801 : fltmgr!FltpPassThrough+0xf
fffff880`02849fc0 fffffa80`04590010 : 00000000`00000b60 fffffa80`04dd8108 fffffa80`045ba1d0 fffffa80`065e80e8 : fltmgr!FltpDispatch+0xb7
fffff880`0284a020 00000000`00000b60 : fffffa80`04dd8108 fffffa80`045ba1d0 fffffa80`065e80e8 00000000`000000d6 : 0xfffffa80`04590010
fffff880`0284a028 fffffa80`04dd8108 : fffffa80`045ba1d0 fffffa80`065e80e8 00000000`000000d6 00000000`00000000 : 0xb60
fffff880`0284a030 fffffa80`045ba1d0 : fffffa80`065e80e8 00000000`000000d6 00000000`00000000 00000000`00000001 : 0xfffffa80`04dd8108
fffff880`0284a038 fffffa80`065e80e8 : 00000000`000000d6 00000000`00000000 00000000`00000001 fffffa80`056ad330 : 0xfffffa80`045ba1d0
fffff880`0284a040 00000000`000000d6 : 00000000`00000000 00000000`00000001 fffffa80`056ad330 fffffa80`045ba1d0 : 0xfffffa80`065e80e8
fffff880`0284a048 00000000`00000000 : 00000000`00000001 fffffa80`056ad330 fffffa80`045ba1d0 fffffa80`0434e738 : 0xd6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fltmgr!FltpPassThrough+f
fffff880`0104391f 498bb0b8000000  mov     rsi,qword ptr [r8+0B8h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  fltmgr!FltpPassThrough+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11f

FAILURE_BUCKET_ID:  X64_0x1E_fltmgr!FltpPassThrough+f

BUCKET_ID:  X64_0x1E_fltmgr!FltpPassThrough+f

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

The dump indicates a hardware/driver problem.I still find an obsolete driver on your system. The dumps shows a memory error, c0000005 (Access violation). As I stated previously, that driver may not be the cause of your crash; but it is not helping the stability of your system.

Rtnic64.sys Mon Mar 31 01:39:38 2008 - Realtek Ethernet NIC driver Realtek

This driver really needs to be updated; it is a pre-Windows 7 driver.

Shadowcast · Sep 9, 2010

@ttran

I stopped the driver verifier just after the check so that's not the issue..
I've also ran the system file check again and found no issues.

@CarlTR6

That's rather strange as i've seen the update manager adding a driver for that network card but i went ahead and updated the driver myself just to be on the safe side...

I did get two more BSOD's last night but they started after i installed poweriso and the drivers for my xbox 360 controller but i removed them both afterwords and it was stable again..

I've attached the dumps anyway, just to be sure.

Thank you,

Shadowcast

CarlTR6 · Sep 9, 2010

Your dumps verify what you stated above. They don't show the specific causes and they blame two MS system drivers which are involved in running Poweriso and Xbox.

Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL - usual causes are device drivers.

Error code 3B, SYSTEM_SERVICE_EXCEPTION - usual cause are System service, Device driver, graphics driver, ?memory.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\090910-18673-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
Debug session time: Wed Sep  8 20:03:45.356 2010 (GMT-4)
System Uptime: 0 days 0:05:56.213
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {100, 2, 0, fffff8800165f6c6}

Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
Probably caused by : wanarp.sys ( wanarp!WanNdisReceivePackets+317 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000100, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800165f6c6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e0
 0000000000000100 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!IpFlcReceivePackets+1f6
fffff880`0165f6c6 488b36          mov     rsi,qword ptr [rsi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000ba1fd0 -- (.trap 0xfffff80000ba1fd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006733c30 rbx=0000000000000000 rcx=fffffa8004ce9270
rdx=fffffa8006db4a30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800165f6c6 rsp=fffff80000ba2160 rbp=fffffa8004ce9138
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8003e21882
r11=0000000000000100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!IpFlcReceivePackets+0x1f6:
fffff880`0165f6c6 488b36          mov     rsi,qword ptr [rsi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a85ca9 to fffff80002a86740

STACK_TEXT:  
fffff800`00ba1e88 fffff800`02a85ca9 : 00000000`0000000a 00000000`00000100 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba1e90 fffff800`02a84920 : 00000000`00000001 fffff880`0176e9a0 00000000`00000000 00000000`00000801 : nt!KiBugCheckDispatch+0x69
fffff800`00ba1fd0 fffff880`0165f6c6 : 00028770`00000011 fffffa80`04ce9000 00000000`00000100 00000000`00000101 : nt!KiPageFault+0x260
fffff800`00ba2160 fffff880`02d90377 : fffffa80`06733c30 00000000`00000100 00000000`00000101 fffffa80`06aaa990 : tcpip!IpFlcReceivePackets+0x1f6
fffff800`00ba2360 fffff880`014f10eb : 00000000`00000002 00000000`00000000 00000000`00000000 fffffa80`05930840 : wanarp!WanNdisReceivePackets+0x317
fffff800`00ba2410 fffff880`014bb165 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffff880`03e99b70 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff800`00ba2480 fffff880`0143da24 : fffffa80`054181a0 00ba2950`fffff800 00000000`00000000 fffffa80`0592a9d0 : ndis!ndisMDispatchReceiveNetBufferLists+0x375
fffff800`00ba2900 fffff880`0143d9e9 : 00000000`00000000 00000000`00000001 fffffa80`0690fb70 fffff880`02d3b2c9 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff800`00ba2940 fffff880`0143d980 : fffa8005`00000000 fffffa80`068bb6ff fffffa80`068bb6d0 fffff880`03e546fc : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff800`00ba2980 fffff880`02d3d5fc : 00000000`00000001 00000000`00000000 fffffa80`0690fa40 00000000`00000001 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff800`00ba29c0 fffff880`0143d9e9 : fffffa80`05947890 00000000`00000000 00000000`00000001 fffff880`02d5c117 : pacer!PcFilterReceiveNetBufferLists+0x10c
fffff800`00ba2a40 fffff880`0143d980 : 00000000`00000002 fffff880`02d5e0f0 fffff800`00ba2a40 fffff800`00ba2a98 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff800`00ba2a80 fffff880`02d5b6eb : fffffa80`06eaa250 00000000`00000000 00000000`00000002 fffffa80`05925ad0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff800`00ba2ac0 fffffa80`06eaa250 : 00000000`00000000 00000000`00000002 fffffa80`05925ad0 fffff880`00000001 : klim6+0x26eb
fffff800`00ba2ac8 00000000`00000000 : 00000000`00000002 fffffa80`05925ad0 fffff880`00000001 fffffa80`06eaa250 : 0xfffffa80`06eaa250


STACK_COMMAND:  kb

FOLLOWUP_IP: 
wanarp!WanNdisReceivePackets+317
fffff880`02d90377 f0834350ff      lock add dword ptr [rbx+50h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  wanarp!WanNdisReceivePackets+317

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wanarp

IMAGE_NAME:  wanarp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcced

FAILURE_BUCKET_ID:  X64_0xD1_wanarp!WanNdisReceivePackets+317

BUCKET_ID:  X64_0xD1_wanarp!WanNdisReceivePackets+317

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\090910-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Wed Sep  8 19:49:46.295 2010 (GMT-4)
System Uptime: 0 days 0:52:19.153
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001264b4, fffff8800992a140, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c64b4 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001264b4, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800992a140, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
win32k+c64b4
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0

CONTEXT:  fffff8800992a140 -- (.cxr 0xfffff8800992a140)
rax=000000000101020d rbx=fffff900c00bf010 rcx=0000000000000000
rdx=fffff900c1e8d380 rsi=fffff900c06bb010 rdi=fffffa8005aff9a0
rip=fffff960001264b4 rsp=fffff8800992ab10 rbp=fffff8800992aca0
 r8=0000000000000002  r9=fffff900c06bb210 r10=fffff900c0200000
r11=fffff900c06bb084 r12=0000000000000001 r13=0000000000000000
r14=fffff900c2a55010 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k+0xc64b4:
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0 ds:002b:00000000`01010399=????????????????????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001264b4

STACK_TEXT:  
fffff880`0992ab10 00000000`00000000 : 00000001`00000001 fffff900`c00bf010 fffff960`000da9e1 00000000`00000000 : win32k+0xc64b4


FOLLOWUP_IP: 
win32k+c64b4
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+c64b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c4840

STACK_COMMAND:  .cxr 0xfffff8800992a140 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k+c64b4

BUCKET_ID:  X64_0x3B_win32k+c64b4

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

I am going to ask some of the gaming guys to take at look at this. I am not a gamer and they may have some insight into setting up Xbox.

I do find an obsolete driver that could very easily play into this.

Rtnic64.sys Mon Mar 31 01:39:38 2008 - Realtek Ethernet NIC driver Realtek. Update this driver; it is very out of date for Win 7. Reboot and let's see what happens. If you are still having trouble after that, I will get help from the gaming guys.

Keep us posted.

Shadowcast · Sep 9, 2010

Well, seems that something is still wrong... got 3 more BSOD's.

I've tried looking for a more recent driver for the ethernet controller but i already have the latest one ...

I don't think the software for the xbox controller is an issue anymore, as it seems to run just great without it.

I've attached the new dumps.

Thank you,
Shadowcast

CarlTR6 · Sep 9, 2010

One of the dump files is corrupted. Let me suggest that you use zip instead of rar to avoid one possible source of corruption when uploading dump files.

Error code 124, WHEA_UNCORRECTABLE_ERROR. This is the dump that was corrupted.

Error code 3B, SYSTEM_SERVICE_EXCEPTION - usual cause are System service, Device driver, graphics driver, ?memory.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED - usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Both of the remaining dumps indicate memory corruption, 0xc0000005.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005172028, b2000040, 800}

Unable to load image Unknown_Module_00000000`00144042, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00144042
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00144042
Unknown module 'Unknown_Module_00000000_00144042' found on stack, using vad to reload module.
!vad_reload -1 0x144042
Unable to read KTHREAD address fffffa800876abd0
Failed to get new vadroot
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
---------

Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Wed Sep  8 19:49:46.295 2010 (GMT-4)
System Uptime: 0 days 0:52:19.153
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001264b4, fffff8800992a140, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c64b4 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001264b4, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800992a140, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
win32k+c64b4
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0

CONTEXT:  fffff8800992a140 -- (.cxr 0xfffff8800992a140)
rax=000000000101020d rbx=fffff900c00bf010 rcx=0000000000000000
rdx=fffff900c1e8d380 rsi=fffff900c06bb010 rdi=fffffa8005aff9a0
rip=fffff960001264b4 rsp=fffff8800992ab10 rbp=fffff8800992aca0
 r8=0000000000000002  r9=fffff900c06bb210 r10=fffff900c0200000
r11=fffff900c06bb084 r12=0000000000000001 r13=0000000000000000
r14=fffff900c2a55010 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k+0xc64b4:
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0 ds:002b:00000000`01010399=????????????????????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001264b4

STACK_TEXT:  
fffff880`0992ab10 00000000`00000000 : 00000001`00000001 fffff900`c00bf010 fffff960`000da9e1 00000000`00000000 : win32k+0xc64b4


FOLLOWUP_IP: 
win32k+c64b4
fffff960`001264b4 f30f7f808c010000 movdqu  xmmword ptr [rax+18Ch],xmm0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+c64b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c4840

STACK_COMMAND:  .cxr 0xfffff8800992a140 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k+c64b4

BUCKET_ID:  X64_0x3B_win32k+c64b4

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

Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Thu Sep  9 10:20:53.337 2010 (GMT-4)
System Uptime: 0 days 1:48:36.194
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5cab952f01eadf7c
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2558 -- (.exr 0xfffff80000ba2558)
ExceptionAddress: fffff80002cc02d6 (nt!KiDeferredReadyThread+0x00000000000003f6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba2600 -- (.trap 0xfffff80000ba2600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=fffffa8005b61b60
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cc02d6 rsp=fffff80000ba2790 rbp=0000000000000000
 r8=0000000000000008  r9=0000000000000008 r10=fffff80002c4b000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeferredReadyThread+0x3f6:
fffff800`02cc02d6 a12003000080f7ffff mov   eax,dword ptr [FFFFF78000000320h] ds:fffff780`00000320=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cb346e to fffff80002cbb710

STACK_TEXT:  
fffff800`00ba1648 fffff800`02cb346e : 00000000`00000000 00000000`00000000 fffff800`00ba1dc0 fffff800`02ce8668 : nt!KeBugCheck
fffff800`00ba1650 fffff800`02ce140d : fffff800`02ec9b7c fffff800`02e03e84 fffff800`02c4b000 fffff800`00ba2558 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1680 fffff800`02ce8a90 : fffff800`02e0aa40 fffff800`00ba16f8 fffff800`00ba2558 fffff800`02c4b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba16b0 fffff800`02cf59ef : fffff800`00ba2558 fffff800`00ba1dc0 fffff800`00000000 fffffa80`06f5b6d0 : nt!RtlDispatchException+0x410
fffff800`00ba1d90 fffff800`02cbad82 : fffff800`00ba2558 fffff800`02e35e80 fffff800`00ba2600 fffff800`02e35e80 : nt!KiDispatchException+0x16f
fffff800`00ba2420 fffff800`02cb968a : fffff800`00ba2700 00000000`00000001 fffffa80`070063b0 fffff880`0487fc07 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2600 fffff800`02cc02d6 : fffffa80`06be1da8 fffffa80`063833b0 00000000`00000000 fffffa80`06be1da0 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2790 fffff800`02cc6e67 : fffffa80`06be1da0 fffffa80`08ad5ce0 fffffa80`08ad5ce0 00000000`00000000 : nt!KiDeferredReadyThread+0x3f6
fffff800`00ba2810 fffff800`02cc74be : 0000000f`2bf46e5e fffff800`00ba2e88 00000000`00065fa6 fffff800`02e39748 : nt!KiProcessExpiredTimerList+0x157
fffff800`00ba2e60 fffff800`02cc6cb7 : fffff800`02e35ec1 fffffa80`00065fa6 fffffa80`058f12b0 00000000`000000a6 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02cc1865 : 00000000`00000000 fffffa80`05b61b60 00000000`00000000 fffff880`0147bd80 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02cc167c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`079068c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02cb346e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

You definitely have a hardware/hardware related problem. I cannot say that that 2008 driver is causing the crashes; but I can safely say it is not helping your system's stability. It is a pre Win 7 driver.

I would like for you to follow this tutorial and upload all the information requested. We need to know your system information in order to help you sort this thing out.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

For example, I do not know if your computer is desktop or a laptop. If you have a desktop, I recommend that you upgrade your network adapter card to one compatible with Windows 7 if there is not an updated driver for your existing card.

Shadowcast · Sep 10, 2010

Well, i`ve collected all the info and attached the archive.

Yes, the system is a desktop.

If nothing else works i will directly change the network adapter

Thank you,
Shadowcast

CarlTR6 · Sep 10, 2010

Thank you very much for the info. I am glad you have a desktop; that makes things easier. It is good to see that you have updated that Ethernet driver. Good job.

Your Perfmon report shows that Kaspersky is still installed. Ttran mention that in his post:

Remove Kaspersky for testing purpose:
Removal tool for Kaspersky Lab products
Install MSE for testing, it is known for BSODs free:
Security Essentials Software Support | Microsoft Security Essentials

Kaspersky in a known cause of crashes on some Win 7 systems. Be sure to uninstall it using the removal tool linked above. Install MSE and make sure Windows Firewall is turned on. You can try Kaspersky again after you get your system running smoothly; but I do not recommend doing so.

Your most recent crashes show error code 124 and 1E.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED - ususal causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Error code 124, WHEA_UNCORRECTABLE_ERROR - possible causes are Hardware, Incompatibility, May be driver corruption.

Error code 124 is not a nice to see. It definitely says there is a hardware problem. If you are overclocking anything, return to default values.Please read this article on your bugcheck 124: [2-Int] Stop 0x124 - what it means and what to try.

You have already run Memtest and your memory appears to be OK.

1. Uninstall Kaspersky.

2. Monitor your temps with Speedfan.

3. Do a CPU stress test as well, using Prime95[FONT=&quot]. Be sure to watch you CPU temp during the Prime test. Post back with the results of the Prime test.

4. Go down the list in [/FONT][2-Int] Stop 0x124 - what it means and what to try.
[FONT=&quot]

Code:

Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Fri Sep 10 03:58:30.260 2010 (GMT-4)
System Uptime: 0 days 17:36:55.728
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80050a2028, b2000040, 800}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80050a2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009eea58 fffff800`031ee903 : 00000000`00000124 00000000`00000000 fffffa80`050a2028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`009eea60 fffff800`02d86593 : 00000000`00000001 fffffa80`04c92ea0 00000000`00000000 fffffa80`04c92ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009eeaa0 fffff800`031ee5c8 : 00000000`00000728 fffffa80`04c92ea0 fffff880`009eee30 fffff880`009eee00 : nt!WheaReportHwError+0x263
fffff880`009eeb00 fffff800`031edf1a : fffffa80`04c92ea0 fffff880`009eee30 fffffa80`04c92ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009eec50 fffff800`031eddd5 : 00000000`00000004 00000000`00000001 fffff880`009eeeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009eec90 fffff800`031e1e88 : 00000000`00000000 fffff880`009e6180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009eecc0 fffff800`02c6efec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009eecf0 fffff800`02c6ee53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009eee30 fffff880`02cdb9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_system_info.zip\Windows_NT6_BSOD_jcgriff2\090910-35927-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Thu Sep  9 10:20:53.337 2010 (GMT-4)
System Uptime: 0 days 1:48:36.194
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5ccf952f01f9de54
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2558 -- (.exr 0xfffff80000ba2558)
ExceptionAddress: fffff80002cc02d6 (nt!KiDeferredReadyThread+0x00000000000003f6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba2600 -- (.trap 0xfffff80000ba2600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=fffffa8005b61b60
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cc02d6 rsp=fffff80000ba2790 rbp=0000000000000000
 r8=0000000000000008  r9=0000000000000008 r10=fffff80002c4b000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeferredReadyThread+0x3f6:
fffff800`02cc02d6 a12003000080f7ffff mov   eax,dword ptr [FFFFF78000000320h] ds:fffff780`00000320=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cb346e to fffff80002cbb710

STACK_TEXT:  
fffff800`00ba1648 fffff800`02cb346e : 00000000`00000000 00000000`00000000 fffff800`00ba1dc0 fffff800`02ce8668 : nt!KeBugCheck
fffff800`00ba1650 fffff800`02ce140d : fffff800`02ec9b7c fffff800`02e03e84 fffff800`02c4b000 fffff800`00ba2558 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1680 fffff800`02ce8a90 : fffff800`02e0aa40 fffff800`00ba16f8 fffff800`00ba2558 fffff800`02c4b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba16b0 fffff800`02cf59ef : fffff800`00ba2558 fffff800`00ba1dc0 fffff800`00000000 fffffa80`06f5b6d0 : nt!RtlDispatchException+0x410
fffff800`00ba1d90 fffff800`02cbad82 : fffff800`00ba2558 fffff800`02e35e80 fffff800`00ba2600 fffff800`02e35e80 : nt!KiDispatchException+0x16f
fffff800`00ba2420 fffff800`02cb968a : fffff800`00ba2700 00000000`00000001 fffffa80`070063b0 fffff880`0487fc07 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2600 fffff800`02cc02d6 : fffffa80`06be1da8 fffffa80`063833b0 00000000`00000000 fffffa80`06be1da0 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2790 fffff800`02cc6e67 : fffffa80`06be1da0 fffffa80`08ad5ce0 fffffa80`08ad5ce0 00000000`00000000 : nt!KiDeferredReadyThread+0x3f6
fffff800`00ba2810 fffff800`02cc74be : 0000000f`2bf46e5e fffff800`00ba2e88 00000000`00065fa6 fffff800`02e39748 : nt!KiProcessExpiredTimerList+0x157
fffff800`00ba2e60 fffff800`02cc6cb7 : fffff800`02e35ec1 fffffa80`00065fa6 fffffa80`058f12b0 00000000`000000a6 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02cc1865 : 00000000`00000000 fffffa80`05b61b60 00000000`00000000 fffff880`0147bd80 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02cc167c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`079068c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02cb346e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

[/FONT]

Multiple crashes with no reason

New member

My Computer

Computational Biologist

My Computer

New member

My Computer

Computational Biologist

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Computational Biologist

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Similar threads