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: Multiple crashes with no reason


06 Sep 2010   #1

Windows 7 ultimate x64
 
 
Multiple crashes with no reason

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


My System SpecsSystem Spec
.

06 Sep 2010   #2

Microsoft Window 7 Professional 32 bit
 
 

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:
SFC /SCANNOW Command - System File Checker

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
My System SpecsSystem Spec
07 Sep 2010   #3

Windows 7 ultimate x64
 
 

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...
My System SpecsSystem Spec
.


07 Sep 2010   #4

Microsoft Window 7 Professional 32 bit
 
 

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:
Driver Verifier - Enable and Disable

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
My System SpecsSystem Spec
07 Sep 2010   #5

Windows 7 ultimate x64
 
 

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
My System SpecsSystem Spec
07 Sep 2010   #6

Windows 7 Ultimate 32 bit
 
 

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*Symbol information
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.
Quote:
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.

My System SpecsSystem Spec
07 Sep 2010   #7

Windows 7 ultimate x64
 
 

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
My System SpecsSystem Spec
07 Sep 2010   #8

Windows 7 Ultimate 32 bit
 
 

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.
My System SpecsSystem Spec
08 Sep 2010   #9

Windows 7 ultimate x64
 
 

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
My System SpecsSystem Spec
08 Sep 2010   #10

Microsoft Window 7 Professional 32 bit
 
 

Are you still having Driver Verifier on? If so, turn it off please.
Also, can you please run system file check again?
SFC /SCANNOW Command - System File Checker
My System SpecsSystem Spec
Reply

 Multiple crashes with no reason




Thread Tools



Similar help and support threads for2: Multiple crashes with no reason
Thread Forum
Every game I play crashes for no reason? Gaming
Multiple different BSOD. Cannot find reason. BSOD Help and Support
BSOD random crashes, no rhyme or reason BSOD Help and Support
BSOD, Crashes without a reason. BSOD Help and Support
I Installed Windows 7, then for some reason it just randomly crashes. BSOD Help and Support
Untimely System Crashes-Reason? BSOD Help and Support
Bsod Crashes Also, No known reason 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:01 AM.
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