sysdata.xml kernel memory dump BSOD problem error 0x000000d1

[fauther]

Accidentally posted this in the Windows Vista forums. Any help would be greatly appreciated. I am getting a BSOD seemingly randomly. I do not notice that I do anything in particular to trigger it. Sometimes I'll just be browsing Yahoo! articles and it will crash, other times I will be gaming. I play Terra and League of Legends. I also have Ventrilo downloaded, but other than that it is pretty clean. I've done everything I've seen online to fix the problem... which pretty much means just downloading/installing any Windows updates, scanning for viruses, and running lots and lots of long diagnostic tests (memory and hard drive mostly.) None of them ever alerted me to anything in particular. However, when I run Check for Solutions I do get names of files that describe the problem: sysdata.xml

 

[koolkat77]

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

Piriform - Speccy

CPUID - HWMonitor​

• :info: For how to upload a screenshot or file, read here

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+​

:info: Pay close attention to part 3 of the tutorial "If you have errors"

   Tip

• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Upload a screenshot using:

CrystalDiskInfo​

:tip: For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure​

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a7b27b, fffff880033e7908, fffff880033e7160}

Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a7b27b, The address that the exception occurred at
Arg3: fffff880033e7908, Exception Record Address
Arg4: fffff880033e7160, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`02a7b27b 418b40d8        mov     eax,dword ptr [r8-28h]

EXCEPTION_RECORD:  fffff880033e7908 -- (.exr 0xfffff880033e7908)
ExceptionAddress: fffff80002a7b27b (nt!ExpScanGeneralLookasideList+0x00000000000000a0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880033e7160 -- (.cxr 0xfffff880033e7160)
rax=0000000000000000 rbx=fffff80002c2c440 rcx=0000000000000000
rdx=fffff80002c2c430 rsi=fffffa8009ce1890 rdi=000000000000ffff
rip=fffff80002a7b27b rsp=fffff880033e7b40 rbp=0000000000000001
 r8=c0fffffa800d0938  r9=0000000000000004 r10=0000000000000000
r11=0000000000000004 r12=0000000000000000 r13=fffff80002c2c430
r14=0000000000000000 r15=fffff880009b7040
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`02a7b27b 418b40d8        mov     eax,dword ptr [r8-28h] ds:002b:c0fffffa`800d0910=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe100
GetUlongFromAddress: unable to read from fffff80002cbe1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`02a7b27b 418b40d8        mov     eax,dword ptr [r8-28h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002a70a70 to fffff80002a7b27b

STACK_TEXT:  
fffff880`033e7b40 fffff800`02a70a70 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02cbec40 : nt!ExpScanGeneralLookasideList+0xa0
fffff880`033e7ba0 fffff800`02a70fbe : 00000000`00000008 fffff880`033e7c10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40
fffff880`033e7bd0 fffff800`02d24ede : fffffa80`09d5cb50 00000000`00000080 fffffa80`09ce1890 00000000`00000001 : nt!KeBalanceSetManager+0x1be
fffff880`033e7d40 fffff800`02a77906 : fffff880`009b2180 fffffa80`09d5cb50 fffff880`009bd0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033e7d80 00000000`00000000 : fffff880`033e8000 fffff880`033e2000 fffff880`033e7700 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

STACK_COMMAND:  .cxr 0xfffff880033e7160 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+a0

BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+a0

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

 

[fauther]

Downloaded Speccy. Here is the screenshot: View attachment 278176

Downloaded Memtest onto USB and rebooted computer using USB. Memtest never even made it through 1 pass. It froze on Test #4. I will try to run it again tomorrow.

If it freezes again, I will remove all but one stick of RAM and start that whole process...

I have not gotten to the rest of your advice.

 

[koolkat77]

You have almost nothing installed on your system which makes me believe the issues lie within hardware.

Heat:
-Only use the laptop on a hard surface with nothing blocking any of the vents.
-Use a laptop cooling pad if possible (if it is a laptop)
-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

If it's a Desktop, ensure that:
- the video card cooler is free of dust/clogs
- the video card has adequate power and that the connectors are firmly seated
- the video card cooler fan is working/moves freely
- the video card has adequate cool airflow (as it passes through the case). You can test this by opening the case and pointing a house fan at the video card.

If it's a Laptop, blow out all vents with canned air (don't use an air compressor or a vacuum as they can cause damage) and ensure that the fan is working. Place the laptop on a hard surface when using it (or use a cooling pad).

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors​

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset​

Enable Driver Verifier to see if it catches any misbehaving driver:

Driver Verifier - Enable and Disable​

• :info: Using Driver Verifier to identify issues with Drivers