Question
Applies to
92 views

Lots of ntoskernl.exe Bsods, why?

Brownsfan02 asked on

Hello, I have been having a lot of BSODs lately and it's been driving me a little crazy. I have a custom built computer running Windows 7 64 bit. The motherboard and other specs are: 

Motherboard: MSI 970A-G46

RAM: 8 GB DDR3 Corsair made

Processor: AMD Phenom II x4 965

Graphics Card: NVIDIA GeForce GTX 660Ti

My most recent dump files are here:

https://onedrive.live.com/redir?resid=5318F910484B0D7F%21133

https://onedrive.live.com/redir?resid=5318F910484B0D7F%21134

https://onedrive.live.com/redir?resid=5318F910484B0D7F%21135

I have a Driver View Report Here:

https://onedrive.live.com/redir?resid=5318F910484B0D7F%21136

I have an exported system information file here: 

https://onedrive.live.com/redir?resid=5318F910484B0D7F%21137

The system info file wasn't done in safe mode but if you want it in safe mode I will be checking back to this often and can do it. If anyone needs any more info I will definitely post it, these BSODs are really annoying. 

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Hi,


We have three bug checks:


SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.


BugCheck 3B, {c000001d, fffff80002e4b43c, fffff8800a65cef0, 0}


3: kd> ln fffff80002e4b43c
(fffff800`02e4b438)   nt!MmIsSpecialPoolAddress+0x4   |  (fffff800`02e4b4d8)   nt!MI_VA_IN_SESSION_SPECIAL_POOL


^^ The exception occurred in nt!MmIsSpecialPoolAddress. This indicates Driver Verifier was enabled at the time of the crash and there is very likely a 3rd party driver corrupting pool.


PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.


DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

This is the general bug check code for fatal errors found by Driver Verifier.


3: kd> k
Child-SP          RetAddr           Call Site
fffff880`0aadfe98 fffff800`033204ec nt!KeBugCheckEx
fffff880`0aadfea0 fffff800`03335bf4 nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0aadfee0 fffff800`030ed890 nt!VfCheckUserHandle+0x1b4
fffff880`0aadffc0 fffff800`031aff1c nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`0aae0090 fffff800`031b0c06 nt!IopXxxControlFile+0x17c
fffff880`0aae01c0 fffff800`02e92e53 nt!NtDeviceIoControlFile+0x56
fffff880`0aae0230 fffff800`02e8f410 nt!KiSystemServiceCopyEnd+0x13
fffff880`0aae0438 fffff880`01491082 nt!KiServiceLinkage
fffff880`0aae0440 00000000`00000000 Tpkd+0x6082


^^ The driver causing memory corruption appears to be Tpkd.sys which is the

PACE Anti-Piracy InterLok software driver.


-------------------

1. Uninstall PACE ASAP.

2. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

and rename AODDriver2.sys to AODDriver.2old

and then Restart.

Regards,

Patrick

Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress