BSOD Issues

zigzag3143 · 09 Oct 2010

Bain said:

As you suspected booting normally with those options set resulted in a smooth load and no crash, however booting normally with all drivers resulted in a bsod with the dump attached. A sincere thank you to all of those who have helped me so far - far more help here than Cyberpower wants to give me.

Continuing, this one was caused by hardware. Probably a device driver causing a memory exception.

Either the memory caused the hardware or the reverse.

If you havent yet

1-rum memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-Run a system file check

SFC /SCANNOW Command - System File Checker

3-If you are overclocking stop. If you are running a raid re-install its driver.

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\100910-29484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sat Oct  9 17:21:57.755 2010 (GMT-4)
System Uptime: 0 days 0:02:05.471
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002fbe007, 1, 79}

Probably caused by : hardware ( nt!NtAllocateVirtualMemory+f27 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fbe007, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000079, Parameter 1 of the exception

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!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000079

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
 0000000000000079 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88007793508 -- (.exr 0xfffff88007793508)
ExceptionAddress: fffff80002fbe007 (nt!NtAllocateVirtualMemory+0x0000000000000f27)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000079
Attempt to write to address 0000000000000079

TRAP_FRAME:  fffff880077935b0 -- (.trap 0xfffff880077935b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fbe007 rsp=fffff88007793740 rbp=fffff80002fbe260
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80039f70c0
r11=fffff88007793660 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!NtAllocateVirtualMemory+0xf27:
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h] ds:d540:00000000`00000074=????????
Resetting default scope

MISALIGNED_IP: 
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

LAST_CONTROL_TRANSFER:  from fffff80002cf5a39 to fffff80002cbb740

STACK_TEXT:  
fffff880`07792d38 fffff800`02cf5a39 : 00000000`0000001e ffffffff`c0000005 fffff800`02fbe007 00000000`00000001 : nt!KeBugCheckEx
fffff880`07792d40 fffff800`02cbad82 : fffff880`07793508 00000000`00000005 fffff880`077935b0 fffffa80`060814a0 : nt!KiDispatchException+0x1b9
fffff880`077933d0 fffff800`02cb98fa : 00000000`00000001 00000000`00000005 fffff880`0107ea00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`077935b0 fffff800`02fbe007 : 00000000`00000005 fffff800`02fbe260 fffffa80`060814a0 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`07793740 fffff880`07793801 : fffffa80`00000040 fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 : nt!NtAllocateVirtualMemory+0xf27
fffff880`077938f0 fffffa80`00000040 : fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 00000000`00000000 : 0xfffff880`07793801
fffff880`077938f8 fffff880`07793a30 : fffff880`07793940 fffffa80`060814a0 00000000`00000000 fffff880`07793928 : 0xfffffa80`00000040
fffff880`07793900 fffff880`07793940 : fffffa80`060814a0 00000000`00000000 fffff880`07793928 fffff801`00000104 : 0xfffff880`07793a30
fffff880`07793908 fffffa80`060814a0 : 00000000`00000000 fffff880`07793928 fffff801`00000104 00000000`00000000 : 0xfffff880`07793940
fffff880`07793910 00000000`00000000 : fffff880`07793928 fffff801`00000104 00000000`00000000 00000000`00000000 : 0xfffffa80`060814a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!NtAllocateVirtualMemory+f27

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Bain · 09 Oct 2010

I have not run memtest however I don't have a CD to burn it to so I won't be able to. I have tried each of my sticks individually before as well to see if it was a RAM and the errors persisted(also tried different slots on the mobo to see if that made a difference - it did not). I did run the windows memory diagnostics program but I have little faith in it.

Question: if it is bad ram, or a bad mobo, wouldn't I get the same errors in safe mode? I am in safe mode at the moment and I have never had any issues, even after 4+ hours, where with a normal boot I crash within minutes.

Another note, I recently formatted this PC and the old windows installation was saved on the machine as windows.old - is this significant?

The SFC /scannow did not find any integrity violations.

CarlTR6 · 09 Oct 2010

You can run Memtest from a USB stick: RAM - Test with Memtest86+

Bain · 09 Oct 2010

The only USB drive I have here isn't registering with memtest. :S

Bain · 09 Oct 2010

It just occurred to me that I could have been having a blue screen because of a bad driver and bad ram. I just took out one of my memory sticks so lets see if my problems keep up. Thanks again for all your hard work!

CarlTR6 · 09 Oct 2010

That did not surprise me. Now to find the problem.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Code:

Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sat Oct  9 17:21:57.755 2010 (GMT-4)
System Uptime: 0 days 0:02:05.471
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002fbe007, 1, 79}

Probably caused by : hardware ( nt!NtAllocateVirtualMemory+f27 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fbe007, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000079, Parameter 1 of the exception

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!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000079

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
 0000000000000079 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88007793508 -- (.exr 0xfffff88007793508)
ExceptionAddress: fffff80002fbe007 (nt!NtAllocateVirtualMemory+0x0000000000000f27)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000079
Attempt to write to address 0000000000000079

TRAP_FRAME:  fffff880077935b0 -- (.trap 0xfffff880077935b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fbe007 rsp=fffff88007793740 rbp=fffff80002fbe260
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80039f70c0
r11=fffff88007793660 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!NtAllocateVirtualMemory+0xf27:
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h] ds:d540:00000000`00000074=????????
Resetting default scope

MISALIGNED_IP: 
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

LAST_CONTROL_TRANSFER:  from fffff80002cf5a39 to fffff80002cbb740

STACK_TEXT:  
fffff880`07792d38 fffff800`02cf5a39 : 00000000`0000001e ffffffff`c0000005 fffff800`02fbe007 00000000`00000001 : nt!KeBugCheckEx
fffff880`07792d40 fffff800`02cbad82 : fffff880`07793508 00000000`00000005 fffff880`077935b0 fffffa80`060814a0 : nt!KiDispatchException+0x1b9
fffff880`077933d0 fffff800`02cb98fa : 00000000`00000001 00000000`00000005 fffff880`0107ea00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`077935b0 fffff800`02fbe007 : 00000000`00000005 fffff800`02fbe260 fffffa80`060814a0 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`07793740 fffff880`07793801 : fffffa80`00000040 fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 : nt!NtAllocateVirtualMemory+0xf27
fffff880`077938f0 fffffa80`00000040 : fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 00000000`00000000 : 0xfffff880`07793801
fffff880`077938f8 fffff880`07793a30 : fffff880`07793940 fffffa80`060814a0 00000000`00000000 fffff880`07793928 : 0xfffffa80`00000040
fffff880`07793900 fffff880`07793940 : fffffa80`060814a0 00000000`00000000 fffff880`07793928 fffff801`00000104 : 0xfffff880`07793a30
fffff880`07793908 fffffa80`060814a0 : 00000000`00000000 fffff880`07793928 fffff801`00000104 00000000`00000000 : 0xfffff880`07793940
fffff880`07793910 00000000`00000000 : fffff880`07793928 fffff801`00000104 00000000`00000000 00000000`00000000 : 0xfffffa80`060814a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74        dec     dword ptr [rbx+rcx*4+74h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!NtAllocateVirtualMemory+f27

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

0: kd> lmtsmn
start             end                 module name
fffff880`0415e000 fffff880`0419c000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00ee9000 fffff880`00f40000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03d00000 fffff880`03d8a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`041d5000 fffff880`041eb000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03f6d000 fffff880`03f82000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e2a000 fffff880`00e35000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00fee000 fffff880`00ff7000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`008b0000 fffff960`00911000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
fffff880`03c54000 fffff880`03c5b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03f36000 fffff880`03f47000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`05800000 fffff880`0581e000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00700000 fffff960`00727000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`03c21000 fffff880`03c4b000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d22000 fffff880`00de2000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0103a000 fffff880`0106a000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cc4000 fffff880`00d22000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01129000 fffff880`0119c000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`041c5000 fffff880`041d5000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05ab8000 fffff880`05ac6000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03f18000 fffff880`03f36000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03f09000 fffff880`03f18000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05a90000 fffff880`05ab2000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05ad2000 fffff880`05adb000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05ac6000 fffff880`05ad2000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05adb000 fffff880`05aee000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05aee000 fffff880`05afa000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`148a8000 fffff880`1499c000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`1499c000 fffff880`149e2000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`010b7000 fffff880`010cb000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0106b000 fffff880`010b7000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013ed000 fffff880`013f7000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`00c5c000 fffff880`00c96000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c02000 fffff800`02c4b000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0413a000 fffff880`0415e000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05b08000 fffff880`05b21000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05b21000 fffff880`05b29080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05afa000 fffff880`05b08000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`046cb000 fffff880`04793000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015e4000 fffff880`015ed000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`040b5000 fffff880`040c4000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05b64000 fffff880`05b72000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb6000 fffff800`00bc0000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03e00000 fffff880`03e43000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013c2000 fffff880`013dc000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05ab2000 fffff880`05ab7200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05bc4000 fffff880`05bd9000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05b80000 fffff880`05ba3000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00ca3000 fffff880`00cb0000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`05b72000 fffff880`05b80000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`040c4000 fffff880`040d3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05b2a000 fffff880`05b37000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00fd4000 fffff880`00fee000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04793000 fffff880`047ab000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`047ab000 fffff880`047d8000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0522c000 fffff880`0527a000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0527a000 fffff880`0529d000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`03cb9000 fffff880`03cc4000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f49000 fffff880`00f53000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010cb000 fffff880`01129000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03efe000 fffff880`03f09000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015d2000 fffff880`015e4000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014d8000 fffff880`015ca000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04024000 fffff880`04030000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04030000 fffff880`0405f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`046b6000 fffff880`046cb000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03c00000 fffff880`03c0f000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03d8a000 fffff880`03dcf000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`03cc4000 fffff880`03cd5000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03ef2000 fffff880`03efe000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c4b000 fffff800`03227000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0121f000 fffff880`013c2000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`03c4b000 fffff880`03c54000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`04645000 fffff880`0465c000   nusb3hub nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)
fffff880`03f8b000 fffff880`03fbb000   nusb3xhc nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61)
fffff880`148a6000 fffff880`148a7180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`13c14000 fffff880`148a5e00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`03dd8000 fffff880`03dfe000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`041a8000 fffff880`041c5000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00f93000 fffff880`00fa8000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f53000 fffff880`00f86000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fbd000 fffff880`00fc4000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fc4000 fffff880`00fd4000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013dc000 fffff880`013ed000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0529d000 fffff880`05343000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05b37000 fffff880`05b47000   point64  point64.sys  Tue Jun 29 04:54:31 2010 (4C29B4C7)
fffff880`05a53000 fffff880`05a90000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cb0000 fffff880`00cc4000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04000000 fffff880`04024000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0405f000 fffff880`0407a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0407a000 fffff880`0409b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0409b000 fffff880`040b5000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03ea1000 fffff880`03ef2000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`03c9e000 fffff880`03ca7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03ca7000 fffff880`03cb0000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03cb0000 fffff880`03cb9000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`05bd9000 fffff880`05bf1000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03fbb000 fffff880`03ffa000   Rt64win7 Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
fffff880`05835000 fffff880`05a52300   RTKVHD64 RTKVHD64.sys Tue Dec 08 05:20:05 2009 (4B1E2855)
fffff880`05343000 fffff880`0534e000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`0419c000 fffff880`041a8000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03e55000 fffff880`03e72000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015ca000 fffff880`015d2000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`05efd000 fffff880`05f93000   srv      srv.sys      Mon Jun 21 23:21:11 2010 (4C202C27)
fffff880`0538d000 fffff880`053f5000   srv2     srv2.sys     Mon Jun 21 23:20:47 2010 (4C202C0F)
fffff880`0534e000 fffff880`0537b000   srvnet   srvnet.sys   Mon Jun 21 23:20:32 2010 (4C202C00)
fffff880`041eb000 fffff880`041ec480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`0537b000 fffff880`0538d000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`03cf3000 fffff880`03d00000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03cd5000 fffff880`03cf3000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03e8d000 fffff880`03ea1000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00570000 fffff960`0057a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03f47000 fffff880`03f6d000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`041ed000 fffff880`041ff000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05b47000 fffff880`05b64000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`149e2000 fffff880`149e3f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04129000 fffff880`0413a000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0465c000 fffff880`046b6000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`149e4000 fffff880`149ef000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`040d3000 fffff880`04129000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f86000 fffff880`00f93000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`03c5b000 fffff880`03c69000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`03c69000 fffff880`03c8e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00fa8000 fffff880`00fbd000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0119c000 fffff880`011e8000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03e72000 fffff880`03e8d000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`03c8e000 fffff880`03c9e000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e36000 fffff880`00eda000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00eda000 fffff880`00ee9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03dcf000 fffff880`03dd8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000b0000 fffff960`003bf000   win32k   win32k.sys   Sat Jun 19 00:31:59 2010 (4C1C483F)
fffff880`03f82000 fffff880`03f8b000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f40000 fffff880`00f49000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`05ba3000 fffff880`05bc4000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`015ed000 fffff880`015fb000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`011e8000 fffff880`011f4000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01216000 fffff880`0121f000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`00de2000 fffff880`00df5000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

The dump blames hardware and points to memory corruption. All of your drivers are up to date. I suggest that you test your RAM using Memtest. Read the instructions in the tutorial below. Let Memtest run for at least seven passes. Any errors wills how up in red. Let us know your results.

https://www.sevenforums.com/tutorials...-memtest86.htm

Bain · 09 Oct 2010

Since I am unable to run memory test(It won't accept the USB drive I have here, and I have no CDs lying around), I have taken out one stick to test it. So far I've been going for seven hours with no blue screens. Thanks for all your help, folks! I think this stick is another culprit so I'll get it out for RMA on Monday. :)

Bain · 14 Oct 2010

I thought I had everything solved however my computer just decided to restart again this morning after installing the most recent windows updates. I've attached my dump once again, thanks in advance!

CarlTR6 · 14 Oct 2010

This is another error code Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Code:

Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Thu Oct 14 13:49:43.376 2010 (GMT-4)
System Uptime: 0 days 4:49:41.077
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002f97a41, 1, 0}

Probably caused by : hardware ( nt!TmpFindResourceManagerTm+11 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f97a41, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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!TmpFindResourceManagerTm+11
fffff800`02f97a41 4f0019          add     byte ptr [r9],r11b

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ead0e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  SteamService.e

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880083e8728 -- (.exr 0xfffff880083e8728)
ExceptionAddress: fffff80002f97a41 (nt!TmpFindResourceManagerTm+0x0000000000000011)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

TRAP_FRAME:  fffff880083e87d0 -- (.trap 0xfffff880083e87d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000102 rbx=0000000000000000 rcx=fffffa8001cbd2e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f97a41 rsp=fffff880083e8960 rbp=fffff880083e8ca0
 r8=fffffa8002490bb8  r9=0000000000000000 r10=fffffffffffffffd
r11=00000000002f9d00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!TmpFindResourceManagerTm+0x11:
fffff800`02f97a41 4f0019          add     byte ptr [r9],r11b ds:00000000`00000000=??
Resetting default scope

MISALIGNED_IP: 
nt!TmpFindResourceManagerTm+11
fffff800`02f97a41 4f0019          add     byte ptr [r9],r11b

LAST_CONTROL_TRANSFER:  from fffff80002cafa39 to fffff80002c75740

STACK_TEXT:  
fffff880`083e7f58 fffff800`02cafa39 : 00000000`0000001e ffffffff`c0000005 fffff800`02f97a41 00000000`00000001 : nt!KeBugCheckEx
fffff880`083e7f60 fffff800`02c74d82 : fffff880`083e8728 00000000`00000001 fffff880`083e87d0 00000000`0054f118 : nt!KiDispatchException+0x1b9
fffff880`083e85f0 fffff800`02c738fa : 00000000`00000001 00000000`00000001 fffff880`083e8900 fffff800`02c80f59 : nt!KiExceptionDispatch+0xc2
fffff880`083e87d0 fffff800`02f97a41 : fffff880`083e8901 fffff800`02f6657a fffffa80`00000001 fffffa80`01bb9200 : nt!KiPageFault+0x23a
fffff880`083e8960 fffff800`02f66a01 : 00000000`00000003 ffffffff`fff885f0 00000000`00000140 00000000`00000178 : nt!TmpFindResourceManagerTm+0x11
fffff880`083e8990 00000000`00000000 : 00000000`005435a8 00000001`00000000 001f0001`00000000 00000000`001f0001 : nt!ObpGrantAccess+0x65


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!TmpFindResourceManagerTm+11
fffff800`02f97a41 4f0019          add     byte ptr [r9],r11b

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!TmpFindResourceManagerTm+11

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

The dump blames hardware. Did this crash occur with one stick of RAM or did you have both sticks in? You really need to test your RAM.

Bain · 14 Oct 2010

This occurred with just the one stick of ram in. I haven't had any issues since then, and I did run a check before I posted here originally with the only software I knew I could use(the windows memory diagnostics). It came up with no issues, which must have been incorrect.

Edit: I did try putting the other stick of ram in just to see if it would run, but it immediately crashed(and generated no dump file).