Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Experiencing a number of BSOD in win 8.1 64


  • Please log in to reply
10 replies to this topic

#1 Jonathan roberts

Jonathan roberts

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 15 September 2014 - 07:11 AM

Hi All,

 

I have always had BSOD at varying degrees over the last couple of years and never really did anything about it.(I know Bad) Previous BSOD have been memory management, paged fault in non paged area, and ntfs file system.  Today I decided I would try and establish the problems and did a memtest (only 2 passes) no errors.

 

Driver verifier identifiied my qualcomm lan driver as a culprit so I installed an updated driver from my motherboard manufacturer and this error disappeared, however all this did was uncover a VerifierExt.sys error  0xC4 and I cant identifiy this driver.

 

Further Info.

 

I recently bought a ATI Radeon R9 290 OC, how can I eliminate the PSU being the problem all the calculator sites say the PSU is adequate. 

 

In this area I am almost certainley a noob, so any help is appreciated.



BC AdBot (Login to Remove)

 


#2 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:10:41 PM

Posted 15 September 2014 - 08:05 AM

Can you upload the dump files for analysis.

Go to

C:\Windows\minidump

Upload all those files by copying them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

#3 Jonathan roberts

Jonathan roberts
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 15 September 2014 - 08:13 AM

 

Can you upload the dump files for analysis.

Go to
 

C:\Windows\minidump
Upload all those files by copying them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

 

 

 

 

Do I need to create the BSOD with driver verifier again, cause the dump file is 1.15gb


Edited by Jonathan roberts, 15 September 2014 - 08:13 AM.


#4 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:10:41 PM

Posted 15 September 2014 - 08:14 AM

No just upload that dump file in a .zip folder to a file sharing site.



#5 Jonathan roberts

Jonathan roberts
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 15 September 2014 - 08:29 AM

No just upload that dump file in a .zip folder to a file sharing site.

 

This is the memory dump;

 

https://onedrive.live.com/redir?resid=8D9FDFF7810CC568%21883

 

These are the minidumps;

 

https://onedrive.live.com/redir?resid=8D9FDFF7810CC568%21882

 

Although the last two at time 11.37 ish are the driver violation problem I cant identify the driver



#6 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:10:41 PM

Posted 15 September 2014 - 11:20 AM

Okay, lets take a look at your Kernel memory dump first.

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: 000000000009200f, ID of the 'NdisTimedDataHang' rule that was violated.
Arg2: fffff801bef27c50, A pointer to the string describing the violated rule condition.
Arg3: ffffcf80365eef20, Address of internal rule state (second argument to !ruleinfo).
Arg4: ffffcf80365eefb8, Address of supplemental states (third argument to !ruleinfo).

This isn't our normal 0xC4 bugcheck, instead it states a an internal rule was violated and therefore bugchecked.

The rule was NdisTimedDataHang which is a rule that states any pending net buffer requests must be completed within 22 seconds by calling the NdisMSendNetBufferListsComplete function to complete any pending requests for NET_BUFFER_LIST structures which sends data over a network.

 

I'm not going to post the information but I can't actually see any NBLs pending, I suspect it was complete or the information wasn't saved but it took longer than 22 seconds.

L1C63x64 L1C63x64.sys Tue Jul 16 07:56:31 2013 (51E4EE9F)

The driver itself is out of date, I suggest you update it.



#7 Jonathan roberts

Jonathan roberts
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 15 September 2014 - 11:27 AM

That's the driver I downloaded from the motherboards site that resolved the irql error, if I update this driver I get irql not equal bsod. I'll go on the manufacturers website and see if I can get the latest driver, I've updated bios ect

Thanks for your help I'll repost if there are any more problems

Edited by Jonathan roberts, 15 September 2014 - 11:28 AM.


#8 Jonathan roberts

Jonathan roberts
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 15 September 2014 - 11:29 AM

Any chance you could look at the memory management error

#9 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:10:41 PM

Posted 15 September 2014 - 01:22 PM

It's an unknown memory management bugcheck, it's also a minidump so there isn't much in the dump file apart from a few query requests to some virtual addresses.

 

Lets see what we can do about this network driver first.



#10 Jonathan roberts

Jonathan roberts
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bradford, UK
  • Local time:05:41 PM

Posted 16 September 2014 - 03:38 AM

It's an unknown memory management bugcheck, it's also a minidump so there isn't much in the dump file apart from a few query requests to some virtual addresses.

 

Lets see what we can do about this network driver first.

 

I have investigated this driver thoroughly and this is the latest driver.  I have updated all the motherboard chipset drivers, updated bios, and audio and gpu drivers and I will try driver verifier again to see if it resolves the issue.  I also got a amd ati gpu driver BSOD last night which I have hopefully resolved.

 

*UPDATE*

I have ran driver verifier and I am no longer getting the driver violation, however I am now getting system_service_exception.

 

Here is a link to the latest BSOD.

 

https://onedrive.live.com/redir?resid=8D9FDFF7810CC568%21105
 


Edited by Jonathan roberts, 16 September 2014 - 04:57 AM.


#11 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:10:41 PM

Posted 16 September 2014 - 03:03 PM

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 0000000080000003, Exception code that caused the bugcheck
Arg2: fffff8011875f8d8, Address of the instruction which caused the bugcheck
Arg3: ffffd0002395f3f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

So we have our 0x3B but it is different to the usual 0x3Bs in that it wasn't caused by an access violation but rather one of more arguments were invalid.

1: kd> !error 0000000080000003
Error code: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
ffffd000`2395fe28 fffff801`1880c461 : ffffd000`2395ff80 fffff801`186b6198 fffff800`ad772bb0 00000000`00000000 : nt!DebugPrompt+0x17
ffffd000`2395fe30 fffff800`ad79cae2 : fffff800`ad772bb0 00000000`00000000 fffff800`ad79c060 00000000`00000007 : nt!DbgPrompt+0x35
ffffd000`2395fe80 fffff800`ad79d0c0 : ffffd000`0000003c ffffe000`492fc010 ffffe000`4abf4c58 00000000`00000004 : fltmgr!FltpvPrintErrors+0x14e
ffffd000`239600f0 fffff800`ad79eec5 : 00000000`00000004 ffffd000`23960209 00000000`00000001 00000000`00000000 : fltmgr!FltpvVerifyPreOperationStatus+0xa4
ffffd000`23960140 fffff800`ad75028a : ffffd000`23960319 00000000`00000000 ffffe000`48938080 ffffe000`4ae1ba70 : fltmgr!FltvPreOperation+0x275
ffffd000`23960270 fffff800`ad7517bc : ffffd000`239603f0 ffffd000`23960400 00000000`eced4b00 00000000`00000000 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`23960380 fffff800`ad77932d : ffffe000`49468210 00000000`00000040 00000000`00000040 ffffd000`23960568 : fltmgr!FltpPassThroughInternal+0x8c
ffffd000`239603b0 fffff801`18c6e911 : ffffcf81`eced4b00 ffffcf81`eced4bd0 ffffe000`4ae1ba70 fffff801`18653a65 : fltmgr!FltpCreate+0x32e
ffffd000`23960460 fffff801`189db513 : 00000000`00000085 ffffd000`239607b0 00000000`00000000 ffffe000`4dacf010 : nt!IovCallDriver+0x3cd
ffffd000`239604b0 fffff801`189e1478 : ffffc001`4a615978 ffffc001`4a615978 ffffc001`4aa4c560 ffffe000`493dd820 : nt!IopParseDevice+0x7b3
ffffd000`239606b0 fffff801`189dedd3 : 00000000`00000000 ffffd000`239608a8 00000000`00000040 ffffe000`47af2080 : nt!ObpLookupObjectName+0x6d8
ffffd000`23960830 fffff801`189a7b52 : 00000000`00000001 ffffe000`4ae2aba8 0000000e`5008b4b0 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
ffffd000`23960960 fffff801`189a77d8 : 0000000e`5008b498 00000000`80100080 0000000e`5008b4f0 00000000`00000000 : nt!IopCreateFile+0x372
ffffd000`23960a00 fffff801`187644b3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x78
ffffd000`23960a90 00007fff`147d1bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000000e`5008b418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`147d1bca

I'm not too familiar with the debugprompt function, do you have a debugger attached to your machine by any chance?

 

Anyway, it seems a filter driver is calling a lot of functions as well as I/Os.

 

I'd say it's your anti virus, can I suggest removing Mcafee as a test.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users