BSOD 0x000003B ntoskrnl.exe / win32k.exe

daymare

Honorable
Oct 27, 2013
7
0
10,510
Hi,

my problem is that I encounter random bsod approx 1 time a day at totally random situations

my spec :

windows 7 sp1 64 bit

asus sabertooth z77
asus gtx 660 oc
intel 3570k @stock
patriot 8gb 1600 mhz
seagate 1tb 64 mb cache
nzxt phantom 410
ocz zt 650 W modular


What Ive done so far is I reinstalled my gpu drivers (clean install, manual uninstall/install, driver sweeper - tried everything)
My temps are fine cpu 65 under full load prime 95 (other components below 50), voltages stable.
I scanned my system with bitdefender 2013 and malwarebytes (both full versions), CCleaner.

I think I willtry to replace ntoskrnl.exe file but I want to know what you guys think about it. Might be a faulty mobo ?

thanks.



bug check string is SYSTEM_SERVICE_EXCEPTION caused mainly by win32k.exe / nvlddmkm.sys and once by dxgkrnl.sys the weird thing is that the first one is from september last year, then 4th december and then 28th january (almost 2 months gap) and since 28 january it happens like every second day. Please help :)





Guys, to help you and me out I ran a driver verifier which turned out to be a good idea. SO I turned it on , restarted my PC and boom - bsod after logging into windows (then again and again- couldnt do nothing). The number was 0x00000c4 and c2 which was strange but I guess it must be a driver, how can I verify it?
 

daymare

Honorable
Oct 27, 2013
7
0
10,510
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {40, 0, fffff98008096c20, 0}

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

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

3: 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: 0000000000000040, acquiring a spinlock when not at DISPATCH_LEVEL.
Arg2: 0000000000000000, current IRQL,
Arg3: fffff98008096c20, spinlock address
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc4_40

CURRENT_IRQL: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: NetSvcHelp.exe

LAST_CONTROL_TRANSFER: from fffff800036f83dc to fffff8000326f880

STACK_TEXT:
fffff880`0ca3a788 fffff800`036f83dc : 00000000`000000c4 00000000`00000040 00000000`00000000 fffff980`08096c20 : nt!KeBugCheckEx
fffff880`0ca3a790 fffff800`037097af : 00000000`00000002 fffffa80`06665008 00000000`00000000 fffff800`0370658b : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0ca3a7d0 fffff880`069b7716 : fffffa80`0c649ac0 fffff980`08096bd0 fffffa80`0c29b340 fffff880`0ca3a898 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0xa0
fffff880`0ca3a830 fffffa80`0c649ac0 : fffff980`08096bd0 fffffa80`0c29b340 fffff880`0ca3a898 00000000`00000000 : ndisrd+0x2716
fffff880`0ca3a838 fffff980`08096bd0 : fffffa80`0c29b340 fffff880`0ca3a898 00000000`00000000 fffff880`069b8b99 : 0xfffffa80`0c649ac0
fffff880`0ca3a840 fffffa80`0c29b340 : fffff880`0ca3a898 00000000`00000000 fffff880`069b8b99 00000000`00010001 : 0xfffff980`08096bd0
fffff880`0ca3a848 fffff880`0ca3a898 : 00000000`00000000 fffff880`069b8b99 00000000`00010001 fffffa80`0c649ac0 : 0xfffffa80`0c29b340
fffff880`0ca3a850 00000000`00000000 : fffff880`069b8b99 00000000`00010001 fffffa80`0c649ac0 00000000`00000000 : 0xfffff880`0ca3a898


STACK_COMMAND: kb

FOLLOWUP_IP:
ndisrd+2716
fffff880`069b7716 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ndisrd+2716

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndisrd

IMAGE_NAME: ndisrd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4fc6df85

FAILURE_BUCKET_ID: X64_0xc4_40_VRF_ndisrd+2716

BUCKET_ID: X64_0xc4_40_VRF_ndisrd+2716

Followup: MachineOwner
 

TRENDING THREADS