Solved various BSODs, not much of a pattern

impjuju · Mar 22, 2014

Hi, I have problems with BSODs on my PC, including page_fault_in_nonpaged_area, driver_irql_not_less_or_equal, system_service_exception, system_thread_exception_not_handled. They seem to be somewhat random except *maybe* occurring more often during gaming (although that might just be me noticing it more then). A month or two ago I assumed it was a hard drive going bad, so I replaced that - didn't fix it, migrated my system to a new SSD - didn't fix it. Memtest86 as of approx one month ago came up good with 8 passes. This is an incomplete list of the past months BSODs due to the hard drive moving and windows reinstalling but I think I waited long enough to give a decent sample.
Thanks lots for your help.

Thedoctor44 · Mar 22, 2014

Before you do any of the following can I please ask that you create a restore point be fore altering drivers. Follow these instructions.

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Your Realtek Family PCI-E Gigabit Ethernet NIC appears to be causing problems. It is fairly up to date but can you update it to a newer version.

Realtek

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffff9a800d97e280, 2, 0, fffff80002c94c40}

Unable to load image Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
[COLOR="Red"]Probably caused by : Rt64win7.sys[/COLOR] ( Rt64win7+17a02 )

Code:

fffff880`06ebd000 fffff880`06f98000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="red"]Wed Dec 18 03:21:42 2013[/COLOR] (52B114C6)
    CheckSum:         000DCE9A
    ImageSize:        000DB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Ventrilo software also appears to be causing problems. Can you please update it here.

Ventrilo - Download

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002cdf981, fffff8800af91998, fffff8800af911f0}

Unable to load image vrtaucbl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vrtaucbl.sys
*** ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys
[COLOR="red"]Probably caused by : vrtaucbl.sys[/COLOR] ( vrtaucbl+9675 )

Code:

fffff880`0450a000 fffff880`0451e080   vrtaucbl T (no symbols)           
    Loaded symbol image file: vrtaucbl.sys
    Image path: vrtaucbl.sys
    Image name: vrtaucbl.sys
    Timestamp:        [COLOR="red"]Sun Apr 01 10:08:53 2012[/COLOR] (4F781B25)
    CheckSum:         000252B0
    ImageSize:        00014080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You are getting memory corruption, however the bugcheck is 0xD1 which indicates a driver is responsible. I would like you to run a memtest86 scan anyway.

Please run it here following these instructions.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {a870f28, 2, 0, fffff88001866dfc}

Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Followup: memory_corruption

Code:

STACK_TEXT:  
fffff880`009af3c8 fffff800`02cd4169 : 00000000`0000000a 00000000`0a870f28 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009af3d0 fffff800`02cd2de0 : fffffa80`0fb697f0 fffff880`0185a884 fffffa80`0dfa3010 fffffa80`0deee7a0 : nt!KiBugCheckDispatch+0x69
fffff880`009af510 fffff880`01866dfc : fffffa80`0cdc5820 00000000`00000002 fffffa80`0cef2000 fffff880`00000003 : nt!KiPageFault+0x260
fffff880`009af6a0 fffff880`0185aefb : fffffa80`0cef2000 fffffa80`0cdc5820 fffffa80`0cef9490 00000000`00000000 : [COLOR="red"]tcpip[/COLOR]!TcpValidateReceive+0xac
fffff880`009af730 fffff880`0185aa8a : 00000000`00000000 fffff880`0196d9a0 fffff880`009af8f0 fffffa80`0cef2140 : [COLOR="red"]tcpip[/COLOR]!IppDeliverListToProtocol+0x7b
fffff880`009af7f0 fffff880`0185a089 : 00000000`00000000 00000000`00000000 fffff880`009af8a0 fffff880`009af8e0 : [COLOR="red"]tcpip[/COLOR]!IppProcessDeliverList+0x5a
fffff880`009af890 fffff880`01857d2f : 00000000`d8baf280 fffff880`0196d9a0 fffff880`0196d9a0 00000000`00000000 : [COLOR="red"]tcpip[/COLOR]!IppReceiveHeaderBatch+0x23a
fffff880`009af970 fffff880`01857302 : fffffa80`0dfa78b0 00000000`00000000 fffffa80`0dfa3001 fffff800`00000001 : [COLOR="red"]tcpip[/COLOR]!IpFlcReceivePackets+0x64f
fffff880`009afb70 fffff880`0185672a : fffffa80`0dfa3010 fffff880`009afca0 fffffa80`0dfa3010 fffff880`016a0000 : [COLOR="red"]tcpip[/COLOR]!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`009afc50 fffff800`02ce0878 : fffffa80`0deee670 00000000`00004800 fffffa80`0f4b5060 00000000`00000000 : [COLOR="red"]tcpip[/COLOR]!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`009afca0 fffff880`01856e22 : fffff880`01856650 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`009afd80 fffff880`0175f0eb : fffffa80`0dfa5010 00000000`00000000 fffffa80`0dab71a0 00000000`00000000 : [COLOR="red"]tcpip[/COLOR]!FlReceiveNetBufferListChain+0xb2
fffff880`009afdf0 fffff880`01728ad6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`009afe60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6

TCPIP is a set of communications protocols that is used for the internet.. Windows couldn't identify the driver so it pointed to this. I think it is the Realtek driver that is at fault.

If that fails can you try stress testing your graphics card as you do have a couple of system service exception bugchecks which from my experience are graphics related and your graphics driver is up to date.

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Code:

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

[COLOR="red"]SYSTEM_SERVICE_EXCEPTION (3b)[/COLOR]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c8da03, Address of the instruction which caused the bugcheck
Arg3: fffff8800dc42020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Code:

fffff880`04805000 fffff880`053fe000   nvlddmkm   (deferred)             
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Sat Feb 08 15:48:31 2014[/COLOR] (52F651CF)
    CheckSum:         00BC7EE8
    ImageSize:        00BF9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There is a newer graphics driver version which you could download as well. Go to this website to update it.

www.geforce.co.uk/drivers

Thedoctor44 · Mar 22, 2014

If you get any more crashes please upload the dump files.

impjuju · Mar 22, 2014

hi! thank you so much. I updated ventrilo and realtek ethernet drivers, nvidia said my graphics card drivers were up to date using the program at the link you provided. furmark ran OK, temperature evening out at 84c with no artifacts plus 5 minutes to make sure. i'm going to run memtest again tonight when i sleep. weirdly enough, i had a bsod after updating everything but it didn't provide a minidump - it's not in the windows/minidump folder, the most recent one is 3/18 which i know for a fact is not the most recent one. i don't know why they're not there, or if they might be somewhere else, sorry. any ideas? it was a driver_irql_not_less_or_equal, by the way. edit to add: it might be worth noting this happened while playing a game (the sims 3) i'm not sure if i just notice it more when i'm playing games or what but it seems like it MIGHT be triggered by them.

Thedoctor44 · Mar 23, 2014

I've encountered problems before where windows just doesn't want to create a dump file even though it's configured to.
That definitely sounds like a graphics driver issue. Can you please follow these instructions on uninstalling the graphics driver.

Uninstall Device and Device Driver

Then can you install the 314.22 version, then choose custom install, then untick all boxes except for Graphics Driver.

Post the results.

impjuju · Mar 24, 2014

let memtest86 run for 7 passes, no errors.
version 314.22 doesn't support gtx 700 series, so i tried the oldest version available through the site (327.23) with only the graphics driver.
got a system_service_exception just now. no minidump file made. managed to catch win32k.sys on the screen before it rebooted.

Thedoctor44 · Mar 24, 2014

Please configure the dump files if you haven't already.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Can you then please enable driver verifier by following these instructions.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Before enable DV can you go onto start,
Type msconfig
Then go onto boot
Then untick all the programs except for your AV

Then enable DV

impjuju · Mar 24, 2014

Well, that worked in producing a minidump at least. The blue screen came on the Starting Windows screen, didn't even get to logon and was in an infinite loop there for a while. Hope this is of some use!

Thedoctor44 · Mar 25, 2014

I'm at college at the moment but I'll look tonight.

Thedoctor44 · Mar 25, 2014

I'm struggling to find a reliable website for the driver that causing the problem. The driver is for the Logitech camera you have. Can you unplug the camera to see if the BSOD persists?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {6, 103, fffff9800a8b88b0, 0}

Unable to load image [COLOR="red"]lv302a64.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="red"]lv302a64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]lv302a64.sys[/COLOR]
Probably caused by : [COLOR="red"]lv302a64.sys[/COLOR] ( lv302a64+15e1 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 0000000000000103, the status
Arg3: fffff9800a8b88b0, the IRP
Arg4: 0000000000000000

Code:

fffff880`09ead000 fffff880`09eaf380   lv302a64 T (no symbols)           
    Loaded symbol image file: lv302a64.sys
    Image path: lv302a64.sys
    Image name: lv302a64.sys
    Timestamp:        [COLOR="red"]Sat Jul 26 16:06:31 2008[/COLOR] (488B3D77)
    CheckSum:         0000B638
    ImageSize:        00002380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

impjuju · Mar 25, 2014

Should I enable driver verifier again and check it that way or should I try to trigger it with gaming?

Thedoctor44 · Mar 25, 2014

If you've unplugged the camera then just do what you normally do and see if the BSODs persist. In the mean time I will try and find a reliable source for the Logitech Camera Driver.

impjuju · Mar 25, 2014

I'll do that but don't worry about getting a driver for it, it's redundant and I didn't use it and honestly have put off throwing it away for no good reason. thanks though.
i'll report back soon.

impjuju · Mar 25, 2014

well, i ended up getting another bsod. on the bright side, it seems like minidumps are happening again now!

Thedoctor44 · Mar 26, 2014

Driver verifier has been turned off hasn't it? Can you please enable it again as this dump file also contains little information.

impjuju · Mar 26, 2014

hi, i ended up having someone change my RAM from "aggressively clocked" (1600s, not overclocked but might be the highest rated for mine) to 1300s/auto for some and that seems to have fixed the problem, weirdly enough! i left a game running all night with no problem. thank you so much for your help though, i really appreciate it. i'm going to wait a day to make sure it's okay and then tentatively mark this as solved.

edited 4/7/2014: having survived the launch of a game and many, many gaming hours, i'm going to mark this as solved! thank you

Thedoctor44 · Mar 27, 2014

Yeah if the RAM timings are too high they can cause lots if problems.
That's great news

Post back if you have any more problems.

Solved various BSODs, not much of a pattern

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

New member

My Computer My Computer

At a glance

Tardis

My Computer My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer