Windows 8 and 8.1 Forums


Unknown random BSOD problem

  1. #1


    Posts : 11
    Windows 8 Pro Professional 6.2.9200

    Unknown random BSOD problem


    Hi everyone,
    I have experienced random lately random BSOD crashes on my brand new PC.
    The crashes happens sometimes everyday(for few days) and sometimes once a week.
    I tried to change OS to windows 7, 8 pro, 8.1 and every time I have those crashes.

    Thanks for your help!

    Attachment 53251

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffff8a010a741d0, fffff8a0186c3110, fffff8a010a741d0}
    
    *** WARNING: Unable to verify timestamp for avgmfx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
    Probably caused by : Pool_Corruption ( nt!ExFreePool+3ec )
    
    Followup: Pool_corruption
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffff8a010a741d0, the pool entry being checked.
    Arg3: fffff8a0186c3110, the read back flink freelist value (should be the same as 2).
    Arg4: fffff8a010a741d0, the read back blink freelist value (should be the same as 2).
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_3
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  bztransmit64.e
    
    CURRENT_IRQL:  1
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8032107c53c to fffff80320e64540
    
    STACK_TEXT:  
    fffff880`98ab1b18 fffff803`2107c53c : 00000000`00000019 00000000`00000003 fffff8a0`10a741d0 fffff8a0`186c3110 : nt!KeBugCheckEx
    fffff880`98ab1b20 fffff880`013308d7 : 00000000`00000003 00000000`00000017 00000000`00000001 fffff880`00000001 : nt!ExFreePool+0x3ec
    fffff880`98ab1bf0 fffff880`0132a174 : fffffa80`00000061 00000000`00000061 00000000`00000096 00000000`00000000 : fltmgr!FltpExpandShortNames+0x178
    fffff880`98ab1c60 fffff880`01329e39 : fffffa80`1f155010 fffffa80`18830000 00000000`c000009a fffffa80`190298e0 : fltmgr!FltpGetNormalizedFileNameWorker+0x174
    fffff880`98ab1cc0 fffff880`01306e62 : c00000bb`19029800 fffff880`98ab3000 fffff880`98aad000 fffffa80`190298e8 : fltmgr!FltpCreateFileNameInformation+0x388
    fffff880`98ab1d30 fffff880`0130166e : fffffa80`19029880 fffffa80`1f155010 fffff880`01320010 fffff803`21242df9 : fltmgr!HandleStreamListNotSupported+0x102
    fffff880`98ab1d70 fffff880`01304474 : fffffa80`1f3f0001 00000000`00000000 00000000`00000000 fffffa80`29546dd8 : fltmgr!FltpGetFileNameInformation+0xa0e
    fffff880`98ab1df0 fffff880`05276835 : fffffa80`1ab6f8b8 fffffa80`1cf998e0 fffffa80`19060bb0 fffff803`20eb447f : fltmgr!FltGetFileNameInformation+0x1b4
    fffff880`98ab1e70 fffff880`0132a22a : fffffa80`1cf998e0 00000000`00000000 00000000`00000000 00000000`00000001 : luafv!LuafvGenerateFileName+0x55
    fffff880`98ab1ea0 fffff880`0132a034 : 00000000`00140000 00000000`c00000bb fffffa80`1cf998e0 00000000`00000000 : fltmgr!FltpCallOpenedFileNameHandler+0x6a
    fffff880`98ab1ee0 fffff880`01329e39 : fffffa80`1cf998e0 fffff880`01303232 00000000`c000009a fffffa80`190298e0 : fltmgr!FltpGetNormalizedFileNameWorker+0x34
    fffff880`98ab1f40 fffff880`01306e62 : c00000bb`19029800 fffff880`98ab3000 fffff880`98aad000 fffffa80`190298e8 : fltmgr!FltpCreateFileNameInformation+0x388
    fffff880`98ab1fb0 fffff880`0130166e : fffffa80`19029880 fffffa80`1cf998e0 fffff880`01320010 00000000`00000001 : fltmgr!HandleStreamListNotSupported+0x102
    fffff880`98ab1ff0 fffff880`01304474 : f4400006`c6b86921 00000000`00000000 fffffa80`1aafb010 fffffa80`29546dd8 : fltmgr!FltpGetFileNameInformation+0xa0e
    fffff880`98ab2070 fffff880`01d64111 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : fltmgr!FltGetFileNameInformation+0x1b4
    fffff880`98ab20f0 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : avgmfx64+0x4111
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExFreePool+3ec
    fffff803`2107c53c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExFreePool+3ec
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  6.2.9200.16912
    
    MODULE_NAME: Pool_Corruption
    
    BUCKET_ID_FUNC_OFFSET:  3ec
    
    FAILURE_BUCKET_ID:  0x19_3_nt!ExFreePool
    
    BUCKET_ID:  0x19_3_nt!ExFreePool
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x19_3_nt!exfreepool
    
    FAILURE_ID_HASH:  {64549bb1-eb15-58f0-046b-157e9134346a}
    
    Followup: Pool_corruption
    ---------
    This dump says that the cause is AVG. If you are using it, please remove it for the time being. Furthermore, pool corruption might suggest that there is something wrong with your RAM. I suggest you test it using Memtest. One stick at the time(if you have two or more). RAM - Test with Memtest86+ - Windows 7 Help Forums
      My System SpecsSystem Spec

  3. #3


    Posts : 11
    Windows 8 Pro Professional 6.2.9200


    Thanks for the quick reply !

    Actually, I have 4 sticks of RAM. I should test them separately ?
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    Yes.
      My System SpecsSystem Spec

  5. #5


    Posts : 11
    Windows 8 Pro Professional 6.2.9200


    Look, @softwaremaniac, you helped me a lot.

    After I deleted AVG, there were no crashes, but lately I had few more.

    Crashes details from WhoCrashed program:
    Code:
    On Tue 11/11/2014 10:20:55 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\111214-6031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540) 
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8036DAFB05F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    On Tue 11/11/2014 10:20:55 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8036DAFB05F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    On Sun 11/9/2014 7:32:57 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110914-7781-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540) 
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    On Fri 10/31/2014 6:03:43 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\103114-14468-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540) 
    Bugcheck code: 0x19 (0x3, 0xFFFFF8A010A741D0, 0xFFFFF8A0186C3110, 0xFFFFF8A010A741D0)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    I'll be glad if someone will be able to help me with it.
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    Please enable Driver Verifier and wait for a new BSOD to happen. When it does, upload that minidump file.
    Using Driver Verifier to identify issues with Drivers - Windows 7 Help Forums
      My System SpecsSystem Spec

  7. #7


    Posts : 11
    Windows 8 Pro Professional 6.2.9200


    I made it, here is the new dump collection file, after I turned on the verifier and had another crash Attachment 53895
      My System SpecsSystem Spec

  8. #8


    Posts : 2,480
    Windows 10 Pro x64


    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mihael\Desktop\111514-7046-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16912.amd64fre.win8_gdr.140502-1507
    Machine Name:
    Kernel base = 0xfffff801`19610000 PsLoadedModuleList = 0xfffff801`198dcaa0
    Debug session time: Sat Nov 15 22:27:22.685 2014 (UTC + 1:00)
    System Uptime: 0 days 14:05:18.809
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {1010, fffffa801aee4040, fffff980510d8c10, fffffa801a158000}
    
    Probably caused by : volsnap.sys ( volsnap!VspDecrementIrpRefCount+24b )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000001010, Invariant MDL buffer contents for Write Irp were modified.
    Arg2: fffffa801aee4040, Device object to which the Write IRP was issued.
    Arg3: fffff980510d8c10, The address of the IRP.
    Arg4: fffffa801a158000, System-Space Virtual Address for the buffer that the MDL describes.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_1010
    
    DRIVER_DEADLOCK: Deadlock detection not initialized 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801197ce0d0 to fffff8011966a540
    
    STACK_TEXT:  
    fffff880`031968b8 fffff801`197ce0d0 : 00000000`000000c4 00000000`00001010 fffffa80`1aee4040 fffff980`510d8c10 : nt!KeBugCheckEx
    fffff880`031968c0 fffff801`19c58a51 : 00000000`00000000 fffff880`03196a30 fffff980`510d8c10 fffff980`663fef68 : nt!MdlInvariantPreProcessing1+0x1c8
    fffff880`03196930 fffff801`19c56c51 : ffff7701`00000002 fffffa80`1975e340 fffffa80`1aee3030 00000000`00000000 : nt!IovpCallDriver1+0x1cd
    fffff880`03196a90 fffff801`19c4dcde : fffff980`510d8c10 00000000`00000002 fffffa80`1aed84e0 fffff880`01a8e329 : nt!VfBeforeCallDriver+0x141
    fffff880`03196ac0 fffff880`01a9149b : fffff980`510d8c10 fffffa80`1aee4190 fffffa80`20009060 fffffa80`1975e340 : nt!IovCallDriver+0x35e
    fffff880`03196b10 fffff880`01a9259e : fffff980`510d8c10 00000000`00000000 00000000`00000000 fffffa80`2240bae0 : volsnap!VspDecrementIrpRefCount+0x24b
    fffff880`03196b60 fffff880`01a91b4e : fffffa80`1ae63ab8 fffffa80`1aed8200 fffff880`01ab6548 fffffa80`1aed8200 : volsnap!VspWriteVolumePhase35+0xae
    fffff880`03196ba0 fffff880`01a920d3 : fffffa80`1cc75b88 fffffa80`1aed82f0 00000000`00000000 fffffa80`1ae63900 : volsnap!VspWriteTableUpdatesCompletionLoop+0x5e
    fffff880`03196bd0 fffff801`1963d075 : 00000000`00000080 fffff880`00bf5f40 fffff880`01a92010 fffffa80`1ae53b00 : volsnap!VspWorkerThread+0xc4
    fffff880`03196c10 fffff801`196f13b6 : fffff880`00bea180 fffffa80`1ae53b00 fffff880`00bf5f40 fffffa80`18a5e8c0 : nt!PspSystemThreadStartup+0x59
    fffff880`03196c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    volsnap!VspDecrementIrpRefCount+24b
    fffff880`01a9149b eb5d            jmp     volsnap!VspDecrementIrpRefCount+0x2aa (fffff880`01a914fa)
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  volsnap!VspDecrementIrpRefCount+24b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: volsnap
    
    IMAGE_NAME:  volsnap.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b662c0
    
    IMAGE_VERSION:  6.2.9200.17047
    
    BUCKET_ID_FUNC_OFFSET:  24b
    
    FAILURE_BUCKET_ID:  0xc4_1010_VRF_volsnap!VspDecrementIrpRefCount
    
    BUCKET_ID:  0xc4_1010_VRF_volsnap!VspDecrementIrpRefCount
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc4_1010_vrf_volsnap!vspdecrementirprefcount
    
    FAILURE_ID_HASH:  {c21f752a-1ff6-654a-aba7-d7ffebff72e3}
    
    Followup: MachineOwner
    ---------
    Volume Shadow Copy Driver seems to be causing the issue. Please try to disable it and see if the BSOD reccurs

    1. Click on Start, type services and press enter.
    2. Locate the service "Volume Shadow Copy" and right click and click "Stop".
    3. Close Services windows.
      My System SpecsSystem Spec

  9. #9


    Posts : 2,480
    Windows 10 Pro x64


    Also update this driver:
    Code:
    Rt630x64.sys Wed Oct 19 14:12:55 2011 (4E9EBEC7)  
    Realtek PCI/PCIe Adapters
      My System SpecsSystem Spec

  10. #10


    Posts : 11
    Windows 8 Pro Professional 6.2.9200


    I disabled the service and after a few days(today) updated the LAN Realtek Driver.

    So far no BSOD's, seems to be working fine, Thank you !!
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Unknown random BSOD problem
Related Threads
I note that there have been several other posts on this subject but I cannot see one that solves my problem. I was transferring files from one external drive to another, I found a problem with a set of folders that I could not transfer with permission which should have been fine as I have...
Hello guys, I'm a new guy here so please forgive me for my title if it's quite unappropriate. Actually I created this account just to ask you about my ISO mounting error that I encountered awhile ago. I already read the rules about creating a thread of a same old topic in here, but seriously I'm...
Greetings, my first post here is of course an error post, I don't often have much free time for discussion boards anymore, but random babble out of the way and onto the point. I got the BSOD WHEA_UNCORRECTABLE_ERROR, this is the 2nd time in 3 weeks, not sure of the cause, first time it was just...
Hello to everyone at the eightforums community, it is a pleasure and honor to join you here. I bought an MSI GT70 laptop almost a year ago and have had issues with BSOD's ever since. At first they were very rare, only occuring every few days and I mostly ignored them thinking that Windows 8 still...
BSOD crash, unknown reason in BSOD Crashes and Debugging
I have had some trouble with BSOD's lately, but I don't know why. They have happened during different "doings" on my computer (surfing/gaming on Facebook, wathing Youtube-clips, writing in Word etc). Restarting is extremely slow too... 40164 Can anyone find out what is happening please?
Solved BSOD - Unknown Causes in BSOD Crashes and Debugging
Hi there, For quite a while now, my computer has been showing some strange symptoms. I have had one or two BSOD, sometimes I get random and complete freezes, and sometimes it doesn't warn me when the battery is over and it just turns off. However, because it is so rare, and also because I had no...
Random BSOD problem in BSOD Crashes and Debugging
I have encountered random BSOD in recent two days after installing windows 8. Please help me check the problem, thanks! (Just updated the dumped file to include complete diagnostic information.)
Eight Forums Android App Eight Forums IOS App Follow us on Facebook