BSOD 0x00000044

[marcodor]

Hello,
Please help, it's main computer recently upgraded from one radio station.
Hangs 2-3 times per week. Sometimes no freeze for 5-6 days, sometimes 2-3 hangs per hour.
Already suspect memory or bios, didn't know.
Usually I read this error is driver related.
There are nothing special: AMD A5800 CPU, 8Gb Ram & Creative Sound Blaster Z.
Video, Audio, Network on board. Also one USB audio, standard MS drivers, all are signed.
Please check attached dumps files. About 10 files.
Big thanks in advice!

 

[Arc]

More info is needed.

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html
____________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa8006e46af0, 1d7b, 0, 0}

Probably caused by : srv2.sys ( srv2!Smb2FreeResponseBufferForAsyncCall+1c )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8006e46af0, Address of the IRP
Arg2: 0000000000001d7b
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


IRP_ADDRESS: fffffa8006e46af0

FOLLOWUP_IP: 
srv2!Smb2FreeResponseBufferForAsyncCall+1c
fffff880`055650ec 488bcb          mov     rcx,rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002e357fc to fffff80002e89bc0

STACK_TEXT:  
fffff880`0319a9c8 fffff800`02e357fc : 00000000`00000044 fffffa80`06e46af0 00000000`00001d7b 00000000`00000000 : nt!KeBugCheckEx
fffff880`0319a9d0 fffff880`055650ec : fffff880`05575d00 00000000`00000246 fffff880`6c32534c 00000000`000003db : nt! ?? ::FNODOBFM::`string'+0x31cdc
fffff880`0319aa10 fffff880`055688fc : 00000000`00000000 fffff880`0319ab10 fffffa80`073a4e20 fffff880`05569016 : srv2!Smb2FreeResponseBufferForAsyncCall+0x1c
fffff880`0319aa40 fffff880`05568c47 : 00000000`00000000 fffffa80`073a4e20 fffffa80`073a4e20 fffff880`0556c961 : srv2!Smb2LeaseFree+0x9c
fffff880`0319aa70 fffff880`055615f4 : 01d02f01`dfa19258 01d02f01`dfa19258 fffff800`0302f200 fffffa80`073a4e20 : srv2!Smb2DereferenceLease+0xa7
fffff880`0319aaf0 fffff800`02e93261 : fffff880`0555a000 fffff800`0302f280 fffffa80`06ce5040 fffff800`00000002 : srv2! ?? ::FNODOBFM::`string'+0x4192
fffff880`0319ab70 fffff800`0312573a : 00000000`00000000 fffffa80`06ce5040 00000000`00000080 fffffa80`06cd1740 : nt!ExpWorkerThread+0x111
fffff880`0319ac00 fffff800`02e7a8e6 : fffff880`02fd7180 fffffa80`06ce5040 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0319ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  srv2!Smb2FreeResponseBufferForAsyncCall+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: srv2

IMAGE_NAME:  srv2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dba2b0a

IMAGE_VERSION:  6.1.7601.17608

FAILURE_BUCKET_ID:  X64_0x44_srv2!Smb2FreeResponseBufferForAsyncCall+1c

BUCKET_ID:  X64_0x44_srv2!Smb2FreeResponseBufferForAsyncCall+1c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x44_srv2!smb2freeresponsebufferforasynccall+1c

FAILURE_ID_HASH:  {bef626ed-25f0-968b-1a6a-50bdcc65c184}

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

 

[marcodor]

Hello, Arc,

Big thanks for trying to help me!
Please, take a look at attached file generated by DM Log collector.

Thanks!

 

[Arc]

Hi marcodor.

A stop 0x44 is usually a driver caused issue; but n specific driver is pointed by the crash dumps and other files.

In this situation it would be better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.