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.



  • Please log in to reply
2 replies to this topic

#1 jappenzeller


  • Members
  • 2 posts
  • Local time:02:48 PM

Posted 15 November 2014 - 09:33 PM

I've been trying to diagnose this BSOD for a few days now with no luck.  Memory passed multiple runs of memtest.  New SSD drive and new install of windows.  The error generally happens while playing a game, but we've seen it I think on boot once or twice as well.  

Attached Files

BC AdBot (Login to Remove)


#2 blueelvis


    Bleep Blop Bleep

  • Malware Response Team
  • 1,666 posts
  • Gender:Male
  • Location:India
  • Local time:01:18 AM

Posted 16 November 2014 - 08:12 AM

Hi jappenzeller & Welcome to the forums ^_^,


I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

3: kd> .trap 0xffffd00022c6e120
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0400000000000020 rbx=0000000000000000 rcx=0200000000000000
rdx=fffff8017973a1e2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8017973a227 rsp=ffffd00022c6e2b0 rbp=0000000000000000
 r8=0000000000146c23  r9=022000000012f66b r10=24001d0e02420000
r11=0000000000000042 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff801`7973a227 4d8b3e          mov     r15,qword ptr [r14] ds:00000000`00000000=????????????????

As we can see from the above analysis, the function MiIdentifyPfn() which is a part of the NT Kernel Module is moving data from register r14 to r15 but it seems that both are NULL and this is not a valid operation.

There is function call in the stack which was not saved by the Minidump. I would suggest you to run Driver Verifier according to this guide -



Make sure you let the system crash for few times and then upload the latest Dump files ^_^


Let me know how it goes ^_^

Member of the Bleeping Computer A.I.I. early response team!

In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/

#3 jappenzeller

  • Topic Starter

  • Members
  • 2 posts
  • Local time:02:48 PM

Posted 16 November 2014 - 09:30 PM

Here are some more dmp files.  I believe the verifier was setup for all of these.  We thought we had narrowed down to a usb wifi adapter because we had some network drops and noticed there was a new driver for 8.1, but after we installed the new driver it actually seemed to get worse.  We switched to another realtek adapter we had, which worked somewhat better but also had issues.  I saw some other people complaining about realtek support for windows 8.1 so we ordered another adapter.  We also had some issues with having to unplug and reinster the mouse and keyboard a couple of times.  After these dump files we went and installed the latest chipset driver for the motherboard but didn't seem to make a difference.  Thanks a bunch for your help.

Attached Files

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users