Windows 8 and 8.1 Forums

Repeated BSOD events of various types

  1. #11

    Posts : 2,480
    Windows 10 Pro x64

    Please upload a complete 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 Complete memory dump.

    Once a dump is created go to:
    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.

      My System SpecsSystem Spec

  2. #12

    rax=0000000000000000 rbx=00000000000000d0 rcx=00000000000000d0
    rdx=0000000000011000 rsi=ffffc000d129bcc8 rdi=ffffc000ca8c0c40
    rip=fffff801528a911b rsp=ffffd0005e0ec048 rbp=ffffd0005e0ec750
     r8=ffffc000cb58d000  r9=ffffd0005e0ec0b8 r10=ffffe001e84a8240
    r11=ffffd0005e0ebfc0 r12=ffffc000d129bb30 r13=ffffc000ca8c0c40
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    fffff801`528a911b 817908efcdab89  cmp     dword ptr [rcx+8],89ABCDEFh ds:002b:00000000`000000d8=????????
    0: kd> !pte rcx
                                               VA 00000000000000d0
    PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
    contains 00C000000070A867  contains 0B00000008D8B867  contains 0000000000000000
    GetUlongFromAddress: unable to read from fffff802e1bd5104
    pfn 70a       ---DA--UWEV  pfn 8d8b      ---DA--UWEV  not valid
    //Register was invalid, passed a bad pointer
    ffffd000`5e0ec048 fffff801`528a90b9 : 00000000`00000000 00000000`000000b8 ffffc000`d35067d0 ffffc000`d129bcc8 : msrpc!GENERIC_OBJECT::InvalidHandle+0x7 //Invalid handle, access violation
    ffffd000`5e0ec050 fffff801`528a90fc : 00000000`00000000 00000000`00000000 ffffc000`d129bb30 ffffc000`d129bac0 : msrpc!I_RpcAsyncSetHandle+0x1d //Set handle 
    ffffd000`5e0ec080 fffff801`5288a6cb : 00000000`00000000 ffffd000`5e0ec0e8 ffffc000`ca8c0c40 ffffd000`5e0ec750 : msrpc!NdrpRegisterAsyncHandle+0xc //Register asynchronous handle
    ffffd000`5e0ec0b0 fffff960`001fcd64 : ffffc000`d4602010 ffffd000`5e0ec750 ffffd000`5e0ec0e8 ffffc000`ca8c0c40 : msrpc!Ndr64AsyncClientCall+0x15b //Microsoft Remote Procedure Call, client call
    ffffd000`5e0ec620 fffff960`0046b2bd : ffffc000`ca8c0c40 00000000`00000001 ffffd000`5e0ec702 00000000`000007ff : win32k!I_PlaySoundkPostMessage+0x38
    ffffd000`5e0ec680 fffff960`000e1e89 : ffffc000`d0630e30 00000000`00000001 00000000`00000000 ffffc000`ca8c0c40 : win32k!PlaySoundPostMessage+0x9d
    ffffd000`5e0ec6d0 fffff960`000e11c5 : 00000000`00000000 ffffd000`5e0ec750 00000000`ffffffff 00000000`00000000 : win32k!DestroyProcessInfo+0x13d
    ffffd000`5e0ec700 fffff960`000e0f05 : ffffe001`e92b6f90 ffffd000`5e0ec858 ffffe001`e91a51d0 00000000`00000000 : win32k!xxxUserProcessCallout+0x1d1 
    ffffd000`5e0ec790 fffff802`e1c5fe0e : ffffd000`5e0ec8a0 ffffd000`5e0ec840 00000000`00000000 00060030`00010002 : win32k!W32pProcessCallout+0x39 //Internal, undocumented routines
    ffffd000`5e0ec7c0 fffff802`e1c60363 : ffffe001`eafd4970 00000000`00000000 00000000`00000000 ffffe001`e7fd4648 : nt!PsInvokeWin32Callout+0x42 //Invoke Windows Subsystem Kernel driver
    ffffd000`5e0ec800 fffff802`e1d26864 : ffffd000`c0000005 ffffe001`e804b880 ffffd000`5e0ecb00 ffffe001`e804b928 : nt!PspExitThread+0x4d3 //Exit thread
    ffffd000`5e0ec910 fffff802`e18d959d : ffffe001`e804b980 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x18 //Terminate APC routine
    ffffd000`5e0ec940 fffff802`e19d9ec0 : 00000000`00000210 ffffd000`5e0ec9c0 fffff802`e18c5368 00000000`00000000 : nt!KiDeliverApc+0x2ed //Execute APC
    ffffd000`5e0ec9c0 fffff802`e19e085a : ffffe001`e804b880 00000000`00000000 00000000`00000000 ffffe001`ebc02720 : nt!KiInitiateUserApc+0x70 //Start user APC
    ffffd000`5e0ecb00 00000000`76de2772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
    00000000`0541f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76de2772
    0: kd> !chkimg -lo 50 -db !msrpc
    4 errors : !msrpc (fffff801528a9087-fffff801528a90af)
    fffff801528a9080  8b  36  4c  3b  f0  75  8c *4c  8b  0d  9a  2f  ff  ff  e8  41 .6L;.u.L.../...A
    fffff801528a9090  0b  00  00  eb  d5  cc  90 *94  90  90  90  90  48  89  5c  24 ............H.\$
    fffff801528a90a0  08  57  48  83  ec  20  48 *8a  19  48  8b  fa  ba  00  10 *01 .WH.. H..H......
    Not necessarily bad RAM, it doesn't appear to be cause by RAM actually.
    The fact that an invalid handle was passed, caused an access violation, and thus a bugcheck (Because we were executing a system service). It's almost impossible to say what went wrong because we have a minidump. You already appear to have DV enabled, looks like an evasive driver problem.
    As previously suggested, enabling creating a full memory dump, would help.
    That being said, RAM is always a possibility, you could try some new RAM sticks if you wish.
      My System SpecsSystem Spec

  3. #13

    Posts : 15
    Windows 8.1

    I am keeping the old ram sticks and set it to write the complete memory dump as the previous post by softwaremaniac. Hopefully I can then provide the required details. Driver Verifier has so far to my knowledge( which is limited) not reported a bad driver.
      My System SpecsSystem Spec

  4. #14

    Posts : 15
    Windows 8.1

    How would I go about uploading a MEMORY.DMP file. Also my PC bsod'ed with the complete memory dump enabled but I cant seem to find a dmp file with today's date.
      My System SpecsSystem Spec

  5. #15

    Posts : 2,480
    Windows 10 Pro x64

    Upload it nevertheless if it's there.
      My System SpecsSystem Spec

  6. #16

    Posts : 15
    Windows 8.1
      My System SpecsSystem Spec

  7. #17

    Posts : 2,480
    Windows 10 Pro x64

    I must've missed your message before. I'm sorry.
    Run chkdsk /f to fix NTFS file system issues and run sfc /scannow to detect and repair corrupt Windows files.
      My System SpecsSystem Spec

  8. #18

    Posts : 15
    Windows 8.1

    I ran both chkdsk and sfc and no errors were found. I have two more complete dump files. they are like 8GBS tough. Il upload if you require them.
      My System SpecsSystem Spec

  9. #19

    Upload the two complete memory dumps, I'll have a look in the near future when I'm free.
      My System SpecsSystem Spec

  10. #20

    Posts : 15
    Windows 8.1

    Hi, here is a link to one of the memory dumps. The files are large and I have struggled to get them uploaded.
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
Repeated BSOD events of various types
Related Threads
I am using a ASUS UX32LN-R4060H and consistently getting BSOD errors. I getting them about 5 times a week. I am not using it's built in bloatfull Windows. I am using Windows 8.1 x64. Drivers installed from ASUS website (except GPU, downloaded from NVidia) Got two kind of BSOD so far and here the...
BSOD's - Random, various error types - Win 8.1 in BSOD Crashes and Debugging
So.. I bought a computer off of Craigslist, it worked great for over a month.. I get a razer naga mouse and it started crashing all the time maybe a week or so afterwards.. I made sure all my drivers were up to date but after a couple more crashes it said my copy of Windows 7 wasn't genuine.. I...
Hello, I have two BSOD problems. One is random, but mostly when I loaded games like BF4 ( 0x124 ) and one that occurs after start or hybernation ( 0x9F ) CPU : Amd phenom II 965 BE @ stock GPU : Amd Radeon HD6770 from Sapphire @ stock MEM: 2x2GB Kingston Valureram 1333 @ stock and 2x2GB...
It should be two files text files one for apps events and one for the system events. This is an example about how the format of the text files and what content should be inside: Event: Log Name: Application Source: ESENT Date: 2013-02-25T03:18:39.000 Event ID: 105 Task: General
Repeated BSOD Crashing in BSOD Crashes and Debugging
Upgraded Dell XPS L502X from Windows 7 to 8. Now getting constant IRQL_NOT_LESS_THAN_OR_EQUAL and random other BSODs. Have updated all drivers that had updates. Can't figure out whats causing the issue. Any ideas EDIT: Fixed the diagnostic file.. thanks for the heads up. Hope this shows someone...
BSOD- different types in BSOD Crashes and Debugging
I keep getting BSOD. I'm running Windows 8 Pro 32 bit. 2GB RAM. AMD Athlon 64 Processor 4000+ 64GHz Here are the latest ones: MEMORY_MANAGEMENT 0x0000001a Caused by driver: ntoskrnl.exe IRQL_NOT_LESS_OR_EQUAL 0x0000000a Caused by driver: ntoskrnl.exe
Eight Forums Android App Eight Forums IOS App Follow us on Facebook