Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD's, error 0xa

02 Mar 2012   #21
adrastea

Windows 7 Home Premium x64 OEM
 
 

I wish you were here. So far no more blue screens. Driver verifier is still running, but everything is working fine as of now.


My System SpecsSystem Spec
.
02 Mar 2012   #22
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by adrastea View Post
I wish you were here. So far no more blue screens. Driver verifier is still running, but everything is working fine as of now.
Fingers crossed
My System SpecsSystem Spec
04 Mar 2012   #23
adrastea

Windows 7 Home Premium x64 OEM
 
 

Another one happened today as soon as my computer loaded up. It never loaded the desktop, just said starting windows then blue screened after trying to load the desktop.
Here's the dump file.
My System SpecsSystem Spec
.

04 Mar 2012   #24
zigzag3143

Win 8 Release candidate 8400
 
 

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files
My System SpecsSystem Spec
04 Mar 2012   #25
adrastea

Windows 7 Home Premium x64 OEM
 
 

So I ran the uninstaller for that driver, but it didn't detect it on my computer. I also checked where it said it's located in the registry and it wasn't listed there. What's that all about?
My System SpecsSystem Spec
16 Mar 2012   #26
adrastea

Windows 7 Home Premium x64 OEM
 
 

It happened again. I got tired of things not working and formatted/redid my computer this past Sunday. Since I let Windows install all the drivers last time, I did it manually this time to see if that fixed anything. It seemed to until today when it blue screened again. I noticed a pattern though. It does it sometimes when input devices change. For example, it did it when I plugged in speakers while it was running, again later when I plugged in headphones, a different time when I bumped the dvi cable loose, and just now when I plugged in an Xbox 360 controller. It's not always the case, but I have noticed that it is sometimes seemingly the cause.

I just realized that it said it couldn't produce a dump file. Here's the bug report from the event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000004, 0x0000000000000002, 0x0000000000000001, 0xfffff80002b07932). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
My System SpecsSystem Spec
18 Mar 2012   #27
writhziden

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Standard PS/2 Keyboard	ACPI\PNP0303\4&8AB8035&0	This device is not present, is not working properly, or does not have all its drivers installed.
Do not worry about the above if you have a USB keyboard.


Security Software:
Code:
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	852	8	200	1380	3/16/2012 1:13 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2276	8	200	1380	3/16/2012 1:13 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3016	8	200	1380	3/16/2012 1:13 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Possible out of date driver:
Code:
AtiPcie	fffff880`01630000	fffff880`01638000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
AtiPcie.sys


Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\adrastea\Windows_NT6_BSOD_jcgriff2\031612-19702-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c9b650 Debug session time: Fri Mar 16 12:07:33.704 2012 (UTC - 6:00) System Uptime: 0 days 0:05:32.264 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {80000a, 2, 0, fffff88002d0fe27} Probably caused by : afd.sys ( afd!AfdSetupReceiveDatagramIrp+67 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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. If kernel debugger is available get stack backtrace. Arguments: Arg1: 000000000080000a, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88002d0fe27, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d05100 000000000080000a CURRENT_IRQL: 2 FAULTING_IP: afd!AfdSetupReceiveDatagramIrp+67 fffff880`02d0fe27 f6430a05 test byte ptr [rbx+0Ah],5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: svchost.exe TRAP_FRAME: fffff88008293020 -- (.trap 0xfffff88008293020) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff88000a00f1c rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88002d0fe27 rsp=fffff880082931b0 rbp=fffffa80046eef40 r8=00000001d467c000 r9=0000000000000000 r10=0000000000000000 r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc afd!AfdSetupReceiveDatagramIrp+0x67: fffff880`02d0fe27 f6430a05 test byte ptr [rbx+0Ah],5 ds:ca80:00000000`0000000a=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ad32e9 to fffff80002ad3d40 STACK_TEXT: fffff880`08292ed8 fffff800`02ad32e9 : 00000000`0000000a 00000000`0080000a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`08292ee0 fffff800`02ad1f60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00800000 : nt!KiBugCheckDispatch+0x69 fffff880`08293020 fffff880`02d0fe27 : fffffa80`05bb4a60 00000000`00000000 00000000`00000001 fffffa80`046eef40 : nt!KiPageFault+0x260 fffff880`082931b0 fffff880`02cbe849 : fffffa80`06924100 00000000`00000000 fffffa80`000004c0 fffffa80`053da170 : afd!AfdSetupReceiveDatagramIrp+0x67 fffff880`08293280 fffff880`02d007d9 : 00000000`00000000 00000000`00000001 fffffa80`05f64220 00000000`00000000 : afd!AfdReceiveDatagramEventCommonHandler+0x389 fffff880`08293320 fffff880`0172fc75 : fffffa80`000004c0 fffffa80`045c8b10 00000000`00000000 fffffa80`059c1d10 : afd!AfdTLDgramReceiveEventHandler+0xe9 fffff880`082933b0 fffff880`0172984d : fffffa80`00000028 fffffa80`059c1d10 fffffa80`00000000 fffffa80`04358fe8 : tcpip!UdpDeliverDatagrams+0x155 fffff880`08293540 fffff880`01708227 : fffffa80`04727380 fffffa80`0668ca80 00000000`00000017 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x1ed fffff880`08293650 fffff880`01707d3a : 00000000`00000000 fffff880`01822800 fffff880`08293810 fffffa80`045c8b10 : tcpip!IppDeliverListToProtocol+0xf7 fffff880`08293710 fffff880`01707339 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`08293800 : tcpip!IppProcessDeliverList+0x5a fffff880`082937b0 fffff880`016ec26f : fffffa80`066b9080 00000000`00000001 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a fffff880`08293890 fffff800`02adfa88 : fffff880`01822800 fffffa80`045b6911 fffff880`00000001 fffffa80`04358d50 : tcpip!IppLoopbackTransmit+0x38f fffff880`08293940 fffff880`016ec90f : fffff880`01738c70 fffffa80`06667ca0 fffff880`08293b02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8 fffff880`08293a20 fffff880`0170974a : fffffa80`066b9080 00000000`00000000 fffffa80`06667c00 fffff880`016f0592 : tcpip!IppLoopbackEnqueue+0x22f fffff880`08293ad0 fffff880`0170b895 : 00000000`00000000 fffffa80`04358e00 fffff880`08293c00 fffff800`00000000 : tcpip!IppDispatchSendPacketHelper+0x38a fffff880`08293b90 fffff880`01709fd3 : fffffa80`04945411 fffffa80`00000000 fffffa80`00000028 fffffa80`00000000 : tcpip!IppPacketizeDatagrams+0x2d5 fffff880`08293cb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppSendDatagramsCommon+0x753 STACK_COMMAND: kb FOLLOWUP_IP: afd!AfdSetupReceiveDatagramIrp+67 fffff880`02d0fe27 f6430a05 test byte ptr [rbx+0Ah],5 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: afd!AfdSetupReceiveDatagramIrp+67 FOLLOWUP_NAME: MachineOwner MODULE_NAME: afd IMAGE_NAME: afd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4efa9418 FAILURE_BUCKET_ID: X64_0xD1_afd!AfdSetupReceiveDatagramIrp+67 BUCKET_ID: X64_0xD1_afd!AfdSetupReceiveDatagramIrp+67 Followup: MachineOwner ---------
  1. Possible cause is Drivers... The driver being blamed is a system driver, but it is related to your network.


Use the subsequent steps to determine the cause of your crashes:
  • If you are overclocking any hardware, please stop.

  • Update your network adapter drivers or re-install the latest if you already have the latest. Your current drivers may be out of date or corrupted.
    AR922X is the driver you want to choose, and click on the blue check mark under Windows 7 64-bit.
    Realtek PCIe GBE Family Controller Win7 and WinServer 2008 R2 Auto Installation Program (SID:1483418) is the link you should choose.
    Do your normal routine for a few days and see how the system responds. Report back afterward. If you have any crashes, proceed to the next step and upload your crash reports.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec
20 Mar 2012   #28
adrastea

Windows 7 Home Premium x64 OEM
 
 

Just had two blue screens right in a row. The first was while I was on Facebook using Google chrome, steam running in the background. The second was right after my computer restarted when I was collecting the dump files. Both drivers from the previous post were updated as suggested. I'll continue running driver verifier.
Here's the dump files.
This bug report was 0x24
My System SpecsSystem Spec
20 Mar 2012   #29
writhziden

Windows 7 Home Premium 64 Bit
 
 

032012-15584-01.dmp shows a 0x24 crash related to NTFS.sys; this often means data corruption. It can also mean Memory problems... Drivers... corrupted SCSI or IDE Drivers...

Begin by checking for data corruption/hard disk errors.
  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.
My System SpecsSystem Spec
20 Mar 2012   #30
adrastea

Windows 7 Home Premium x64 OEM
 
 

I've already run the disk check with both boxes checked, and nothing came up wrong. I can always try it again I guess.
My System SpecsSystem Spec
Reply

 Random BSOD's, error 0xa




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD's at random times often error 0x0000001E
Hello, after searching through many forums and Windows help sites i still can't help myself to find, why i am getting these bluescreens. I even installed Windows completely new, but after installing the Realtek GBE network driver (manually, cause Windows didn't find it) the 'fun' began again. I...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
Random BSOD stop error 0x0000001E, hardware error?
Hello, A few days ago I got a random BSOD with the 0x0..1E stop error. Now my computer will rarely boot and when it does it still randomly gets the same BSOD. I once got a 1D stop error but its mostly 1E that keeps happening. I run Windows 7 Professional 64-bit and this time I used a Windows DVD...
BSOD Help and Support
Random BSOD's random error codes
Recently had my computer open and lying on it's side for around 5 days, put the cover back on and booted it up to play some WoW and started having BSOD's, constantly at windows log in, or 5-30 mins sitting at desktop or playing games. Including zipped folder of eventvwr files. Thanks in advance!
BSOD Help and Support
Random BSOD during Random times, error 0x8000000000000002
Hey everyone, Im new here on this forum. I've been having this extremely frustrating problem ever since i swapped out my Motherboard for a new one. I reformatted my computer multiple times, yet my computer seems to BSOD randomly. What happenes is that everything becomes unresponsive; cant...
BSOD Help and Support
Random BSOD's with random error messages after a new setup
Hey! I recently upgraded my setup with an Asus M4A78LT-M mobo, Athlon II X4 640 processor and TakeMS 2x2GB 1333MHz DDR3 memory. After installing the parts I tried to boot to Windows but it always resulted in the same BSOD so I reinstalled my system. After installing Windows for the first time...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App