Bluescreen errors

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

lolman70

Thread Starter
Joined
Mar 21, 2015
Messages
7
I've been receiving consistent bluescreen errors for over a month. I've tried multiple things with no success. Here are the latest dump files:
==================================================
Dump File : 032115-22308-01.dmp
Crash Time : 3/21/2015 9:14:50 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff880`02c469ff
Parameter 3 : fffff880`0b9f0dd0
Parameter 4 : 00000000`00000000
Caused By Driver : afd.sys
Caused By Address : afd.sys+29ff
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+74ec0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032115-22308-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 305,216
Dump File Time : 3/21/2015 9:15:57 PM
==================================================
==================================================
Dump File : 031315-18829-01.dmp
Crash Time : 3/13/2015 3:25:12 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74e90
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18717 (win7sp1_gdr.150113-1808)
Processor : x64
Crash Address : ntoskrnl.exe+74e90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031315-18829-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 315,896
Dump File Time : 3/13/2015 3:26:52 PM
==================================================




==================================================
Dump File : 031515-20451-01.dmp
Crash Time : 3/15/2015 5:45:57 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`035a71a0
Parameter 3 : fffff880`0d6fe080
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74ec0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18717 (win7sp1_gdr.150113-1808)
Processor : x64
Crash Address : ntoskrnl.exe+74ec0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031515-20451-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 346,952
Dump File Time : 3/15/2015 5:46:57 PM
==================================================
 

blues_harp28

Moderator
Joined
Jan 9, 2005
Messages
19,448
Hi. 'Caused By Driver : afd.sys'
'Ancillary Function Driver from Microsoft Corporation'
http://www.systemlookup.com/Drivers/4512-afd_sys.html
======
However, where the blue screen error is reported, is not necessarily where it first started and may not be the cause.
======
Create a new folder on the desktop and call it dumpfiles [or something similar]
Look in c:\windows\minidump
Copy the last 5 minidump files to that folder.
Close the folder and right click on it and select Send To Compressed [zipped] Folder.
Windows will compress the file and then save the new zipped file in the same location.

Use the 'manage attachments' in the 'Go Advanced' reply window below to upload that zip file here as an attachment.
======
Check and post
TSG System Information Utility - found here.
http://static.techguy.org/download/SysInfo.exe
 

blues_harp28

Moderator
Joined
Jan 9, 2005
Messages
19,448
Minidump scan result - in part.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800852b000, 1, fffff88009133a54, 0}

Could not read faulting driver name
Probably caused by : usbaudio.sys ( usbaudio!memcpy+64 )

Followup: MachineOwner
---------
0: kd> !analyze -v

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.

Could not read faulting driver name
FAULTING_IP:
usbaudio!memcpy+64
fffff880`09133a54 488901 mov qword ptr [rcx],rax

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_COMMAND: kb

FOLLOWUP_IP:
usbaudio!memcpy+64
fffff880`09133a54 488901 mov qword ptr [rcx],rax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbaudio!memcpy+64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME: usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51dfdd3a

FAILURE_BUCKET_ID: X64_0x50_usbaudio!memcpy+64

BUCKET_ID: X64_0x50_usbaudio!memcpy+64

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880073f211e, fffff8800d8225d0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b411e )

Followup: MachineOwner
---------
0: kd> !analyze -v

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

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: ShadowOfMordor

CURRENT_IRQL: 0

FOLLOWUP_IP:
nvlddmkm+1b411e
fffff880`073f211e 4c8b7e08 mov r15,qword ptr [rsi+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvlddmkm+1b411e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54d3b001

STACK_COMMAND: .cxr 0xfffff8800d8225d0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+1b411e

BUCKET_ID: X64_0x3B_nvlddmkm+1b411e

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2fae3e )

Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+5d322faf039cdda8
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: uTorrent.exe

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54d3b001

FAILURE_BUCKET_ID: X64_0x1E_0_nvlddmkm+2fae3e

BUCKET_ID: X64_0x1E_0_nvlddmkm+2fae3e

Followup: MachineOwner
======
nvlddmkm.sys
http://www.systemlookup.com/Drivers/54-nvlddmkm_sys.html
http://www.nvidia.com/download/scan.aspx?lang=en-us
usbaudio.sys
http://www.systemlookup.com/Drivers/198-usbaudio_sys.html
Go to the pc's manufacturers website and check for drivers that may need updating.
 

lolman70

Thread Starter
Joined
Mar 21, 2015
Messages
7
I attempted to update both drivers. i think i successfully updated the usbaudio, but the nvidia website said my drivers were up to date. Maybe i have a faulty gpu?
 

blues_harp28

Moderator
Joined
Jan 9, 2005
Messages
19,448
Minidump file check x 3 - in part.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80003331d4e}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+7e )

Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Cities.exe

STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+7e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13

FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::Free+7e

BUCKET_ID: X64_0xA_dxgmms1!VIDMM_PROCESS_HEAP::Free+7e

Followup: MachineOwner
======
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88002fcc6c8, fffff88002fcbf20, fffff88001357564}

Probably caused by : Ntfs.sys ( Ntfs!NtfsDereferenceQuotaControlBlock+24 )

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

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff8800134d8ee to fffff88001357564

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsDereferenceQuotaControlBlock+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52e1be8a

STACK_COMMAND: .cxr 0xfffff88002fcbf20 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsDereferenceQuotaControlBlock+24

BUCKET_ID: X64_0x24_Ntfs!NtfsDereferenceQuotaControlBlock+24

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000005020103, Memory contents of the pool block
Arg4: fffff8a0000098f0, Address of the block of pool being deallocated

Debugging Details:
------------------
POOL_ADDRESS: fffff8a0000098f0

FREED_POOL_TAG: Pp

BUGCHECK_STR: 0xc2_7_Pp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LOCK_ADDRESS: fffff8000347dda0 -- (!locks fffff8000347dda0)

Resource @ nt!PiEngineLock (0xfffff8000347dda0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
1 total locks

PNP_TRIAGE:
Lock address : 0xfffff8000347dda0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff800033acbf9 to fffff80003277ec0

STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!CmpFreeKeyControlBlock+123

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff

FAILURE_BUCKET_ID: X64_0xc2_7_Pp___nt!CmpFreeKeyControlBlock+123

BUCKET_ID: X64_0xc2_7_Pp___nt!CmpFreeKeyControlBlock+123

Followup: MachineOwner
---------
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`0269ce38 fffff800`033acbf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`05020103 : nt!KeBugCheckEx
fffff880`0269ce40 fffff800`0355fe13 : fffff8a0`10db3038 fffff880`0269d490 00000000`00000011 fffff8a0`00022820 : nt!ExFreePool+0xcb1
fffff880`0269cef0 fffff800`034cbb18 : 00000000`00000000 fffff880`0269d501 fffff8a0`10db3008 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`0269cf20 fffff800`03544678 : fffff8a0`00024010 fffff8a0`00024010 fffff880`0269d100 fffff880`0269d580 : nt! ?? ::NNGAKEGL::`string'+0x1e5d3
fffff880`0269d020 fffff800`03575738 : fffffa80`0a2421c8 fffff800`03203000 fffffa80`0a242010 fffff800`00000000 : nt!CmpParseKey+0x948
fffff880`0269d320 fffff800`03576956 : 00000000`00000000 fffffa80`0a242010 fffff8a0`16ce9574 fffffa80`06ae3650 : nt!ObpLookupObjectName+0x588
fffff880`0269d410 fffff800`0352dfa8 : fffff880`009ea180 00000000`00000000 00000000`00000000 fffff880`0269d5e8 : nt!ObOpenObjectByName+0x306
fffff880`0269d4e0 fffff800`0352e84e : fffff880`0269d8f8 fffff880`000f003f fffff880`0269d910 fffff800`034b4600 : nt!CmCreateKey+0x2e1
fffff880`0269d650 fffff800`03277153 : ffffffff`ffffffff 00000000`00000000 fffff6fc`500c52e0 fffff800`0329ac28 : nt!NtCreateKey+0x2e
1: kd> kc
Call Site
nt!KeBugCheckEx
nt!ExFreePool
nt!CmpFreeKeyControlBlock
nt! ?? ::NNGAKEGL::`string'
nt!CmpParseKey
nt!ObpLookupObjectName
nt!ObOpenObjectByName
nt!CmCreateKey
nt!NtCreateKey
nt!KiSystemServiceCopyEnd
nt!KiServiceLinkage
nt!IopCreateRegistryKeyEx
nt!IopGetDeviceInterfaces
nt!PiGetInterfaceDeviceList
nt!PiControlGetInterfaceDeviceList
nt!NtPlugPlayControl
nt!KiSystemServiceCopyEnd
0x0
1: kd> kn
# Child-SP RetAddr Call Site
00 fffff880`0269ce38 fffff800`033acbf9 nt!KeBugCheckEx
01 fffff880`0269ce40 fffff800`0355fe13 nt!ExFreePool+0xcb1
02 fffff880`0269cef0 fffff800`034cbb18 nt!CmpFreeKeyControlBlock+0x123
03 fffff880`0269cf20 fffff800`03544678 nt! ?? ::NNGAKEGL::`string'+0x1e5d3
04 fffff880`0269d020 fffff800`03575738 nt!CmpParseKey+0x948
05 fffff880`0269d320 fffff800`03576956 nt!ObpLookupObjectName+0x588
06 fffff880`0269d410 fffff800`0352dfa8 nt!ObOpenObjectByName+0x306
07 fffff880`0269d4e0 fffff800`0352e84e nt!CmCreateKey+0x2e1
=======
Where the blue screen error is reported, is not necessarily where it first started and may not be the cause.
Some reasons for Blue Screens
New hardware - software installed.
Device driver - Video driver - corrupted - faulty.
Faulty Ram - Overheating - Dying hard drive etc.

I would do the following - starting with the MemTest.
Run a Mem Test.
http://www.memtest.org/
Scroll down to 'Download (Pre-built & ISOs)'
'Download - Pre-Compiled Bootable ISO (.zip)'

Download the ISO file - then burn the ISO to a Cd.
Start the Pc using the Cd and run the memory test overnight or for at least 8 passes.

It is best to run a full scan on individual Ram sticks if you can - as it may pass the test with all sticks remaining in the pc but fail the test on individual sticks of Ram.
Guide to using Memtest86+
http://www.bleepingcomputer.com/forums/topic207910.html
======
Hard drive test.
SeaTools for DOS tutorial - ISO to CD
http://knowledge.seagate.com/articles/en_US/FAQ/201271en?language=en_US
======
Check for overheating.
http://www.piriform.com/speccy
http://www.cpuid.com/softwares/hwmonitor.html
======
======
Also run System File Checker.
Click on Start - Search
Type
cmd
Right click on cmd.exe - select Run as Administrator.
At the Command Prompt - Type
sfc /scannow
(Note space after sfc)

Press Enter.
Let it run to completion - but do not close the Command Prompt window
To save the log file.
Copy and Paste the following in Command Prompt.

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

Press Enter

On your desktop you will see a text file called sfcdetails.txt
Copy and Paste into your next post.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top