Random BSOD's, error 0xa

[adrastea]

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

 

[zigzag3143]

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

 

[adrastea]

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.

 

[zigzag3143]

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

 

[adrastea]

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?

 

[adrastea]

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: .

 

[writhziden]

Problem Devices:

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:

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:

AtiPcie	fffff880`01630000	fffff880`01638000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys

AtiPcie.sys

[list=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
---------


[/list]

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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.

 

[adrastea]

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

 

[writhziden]

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  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.

 

[adrastea]

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

 

[writhziden]

In that case, can you post a screenshot of device manager with IDE ATA/ATAPI Controllers expanded. Start Menu -> Right click Computer -> Manage -> Device Manager from the list on the left... Alternatively: Start Menu -> Control Panel -> Hardware and Sound -> Device Manager.


Additionally, download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[adrastea]

Here's the images you asked for. Also, the attached text file contains the report for the disk check. Zipped up for easier attaching.

 

[writhziden]

Windows has made corrections to the file system.

Suggest you run the disk check again. See my previous post about this message.

 

[adrastea]

Thanks. I'll do that. I never even noticed it said that.

 

[adrastea]

Here's the second report:




Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
238848 file records processed. File verification completed.
286 large file records processed. 0 bad file records processed. 0 EA records processed. 46 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
293770 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
238848 file SDs/SIDs processed. Cleaning up 9 unused index entries from index $SII of file 0x9.
Cleaning up 9 unused index entries from index $SDH of file 0x9.
Cleaning up 9 unused security descriptors.
Security descriptor verification completed.
27462 data files processed. CHKDSK is verifying Usn Journal...
35900816 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
238832 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
186508338 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
230166492 KB in 167830 files.
87044 KB in 27463 indexes.
0 KB in bad sectors.
370519 KB in use by the system.
65536 KB occupied by the log file.
746033352 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
186508338 allocation units available on disk.

Internal Info:
00 a5 03 00 e9 fa 02 00 49 9c 05 00 00 00 00 00 ........I.......
67 01 00 00 2e 00 00 00 00 00 00 00 00 00 00 00 g...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[writhziden]

Looks good. See how the system responds for a while and post back how things are going.

 

[adrastea]

My computer stopped working for a bit starting this Monday. I hadn't used it all weekend, and Friday it had been working fine. It turned on, but had no display, which was odd since the monitor was detecting the DVI cable. I ran my PS3 through it no problem, so it wasn't the cable or the monitor. It's not my video card, since no video ports on my computer were sending out a signal. That goes for all 3 DVI's the two HDMI's, and the VGA. After messing around a bit inside the case, I got it to turn on. Then today it wasn't working again. I noticed this time that the Dr. Debug display was showing 2A. Since my motherboard's box and owner's manual is back home and I'm in college, I used my laptop to find a manual online. Apparently 2A means RAM issues. Which is funny since I thought I made sure they were in the slots tight and I ran Prime95 and Memtest86+ both longer than necessary with no errors. So I took out the fan that was blocking one of my RAM sticks and pushed it in pretty hard to make sure it wasn't loose. After that, my computer booted. Could it have been a slightly loose stick of RAM this entire time?
I haven't even given it a chance to blue screen since that, but I'm hoping that it's done, whether it was the RAM or the hard drive errors.

 

[writhziden]

It very well could have been a loose RAM module; I have seen this cause crashes before. Let us know how the system responds over the next few days. Best of luck!