Need help FAST

Dragon41673 · 06 May 2010

Hello Guys...

I need some help fast...I'm getting married Saturday and leaving Sunday for my honeymoon...and my HTPC has decided to cause me to rip my hair out and I can't figure out why.

When watching recorded TV shows in Media Center, Win 7 Home Premium crashes. While I was trying to back up my shows, WHILE IN SAFE MODE, Win 7 Crashed!!!

Please see the Debug files attached...help me PLEASE!!!

I've checked & made sure ALL drivers are up to date. Prior to 5/4...I had no problems with my Win 7 Media Center.

Memtest version 3.5 ran for almost 9 hours overnight, no problems found.

Dump files from 5/4 are before the Memtest..Dump files from 5/6 are after Memtest.

Thank you to everyone that can & will help out...you'll be a life saver!!!

zigzag3143 · 06 May 2010

Dragon41673 said:

Hello Guys...

I need some help fast...I'm getting married Saturday and leaving Sunday for my honeymoon...and my HTPC has decided to cause me to rip my hair out and I can't figure out why.

When watching recorded TV shows in Media Center, Win 7 Home Premium crashes. While I was trying to back up my shows, WHILE IN SAFE MODE, Win 7 Crashed!!!

Please see the Debug files attached...help me PLEASE!!!

I've checked & made sure ALL drivers are up to date. Prior to 5/4...I had no problems with my Win 7 Media Center.

Thank you to everyone that can & will help out...you'll be a life saver!!!

Most if not all of these are caused by memory corruption (see below). I would download memtestx86 and run it for 5 passes to test yours.

Let us know if you need help

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\Crashes\050410-33306-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01c68000 PsLoadedModuleList = 0xfffff800`01ea5e50
Debug session time: Tue May  4 23:33:03.310 2010 (GMT-4)
System Uptime: 0 days 0:07:08.137
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002060e03, 1, 10}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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: fffff80002060e03, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000010, 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!PfpRpRehashIfNeeded+3
fffff800`02060e03 40895b10        mov     dword ptr [rbx+10h],ebx

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000010

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f100e0
 0000000000000010 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88007fb2658 -- (.exr 0xfffff88007fb2658)
ExceptionAddress: fffff80002060e03 (nt!PfpRpRehashIfNeeded+0x0000000000000003)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000010
Attempt to write to address 0000000000000010

TRAP_FRAME:  fffff88007fb2700 -- (.trap 0xfffff88007fb2700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80001e79c00
rdx=fffff88007fb28c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002060e03 rsp=fffff88007fb2898 rbp=6267730b4cb4314a
 r8=0000000000000000  r9=fffff8a008a87140 r10=ffffffffffffffff
r11=fffff88007fb2898 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!PfpRpRehashIfNeeded+0x3:
fffff800`02060e03 40895b10        mov     dword ptr [rbx+10h],ebx ds:4001:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001d12929 to fffff80001cd8600

STACK_TEXT:  
fffff880`07fb1e88 fffff800`01d12929 : 00000000`0000001e ffffffff`c0000005 fffff800`02060e03 00000000`00000001 : nt!KeBugCheckEx
fffff880`07fb1e90 fffff800`01cd7c42 : fffff880`07fb2658 00000000`00000000 fffff880`07fb2700 fffff800`01e79c00 : nt!KiDispatchException+0x1b9
fffff880`07fb2520 fffff800`01cd67ba : 00000000`00000001 00000000`00000000 fffff8a0`00001a00 00000000`000008c8 : nt!KiExceptionDispatch+0xc2
fffff880`07fb2700 fffff800`02060e03 : fffff800`0212517a fffff8a0`0bfa4000 00000000`00000000 fffffa80`06bea800 : nt!KiPageFault+0x23a
fffff880`07fb2898 fffff800`0212517a : fffff8a0`0bfa4000 00000000`00000000 fffffa80`06bea800 00000000`000007ff : nt!PfpRpRehashIfNeeded+0x3
fffff880`07fb28a0 fffff800`01df94f1 : fffffa80`06be0045 00000000`00000000 fffffa80`00000001 fffff8a0`08a87140 : nt!PfpRpFileKeyUpdate+0x39a
fffff880`07fb2930 fffff880`0114355d : 00000000`00000000 00000000`00000000 fffff880`07fb2ac8 fffffa80`06bea910 : nt!PfFileInfoNotify+0x5a1
fffff880`07fb29c0 fffff880`01143ba8 : fffffa80`05d50010 fffff8a0`08bfe510 fffff880`07fb2ba0 fffff880`07fb2ba0 : fileinfo!FIStreamLog+0x89
fffff880`07fb2a90 fffff880`011433c8 : fffff8a0`08bfe510 00000000`00000000 fffff880`07fb2ba0 fffff880`07fb2ba0 : fileinfo!FIStreamSetFileInfo+0x14c
fffff880`07fb2b00 fffff880`01141bdb : 00000000`00000000 fffff880`00000001 00000000`00000000 00000000`0000431e : fileinfo!FIStreamGetInfo+0x17c
fffff880`07fb2b80 fffff880`010f2242 : 00000000`00000000 fffff8a0`08bfe510 fffffa80`067ac3b0 00000000`00000000 : fileinfo!FIPostCreateCallback+0x1c7
fffff880`07fb2c10 fffff880`010f138b : fffffa80`04707030 fffffa80`068abd70 fffffa80`051076b0 fffffa80`051078d0 : fltmgr!FltpPerformPostCallbacks+0x392
fffff880`07fb2ce0 fffff880`011102b9 : fffffa80`067ac010 fffffa80`05d50010 fffffa80`067ac000 fffffa80`05d3da30 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
fffff880`07fb2d70 fffff800`01fdc777 : 00000000`00000060 fffff800`02000370 fffffa80`055e0708 fffff8a0`05120120 : fltmgr!FltpCreate+0x2a9
fffff880`07fb2e20 fffff800`01fd280f : fffffa80`05d3da30 00000000`00000000 fffffa80`06811560 fffff8a0`07a5fa00 : nt!IopParseDevice+0x5a7
fffff880`07fb2fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupObjectName+0x32f


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
229 errors : !nt (fffff8000206000b-fffff80002060fbb)
fffff80002060000  3d  0b  02  00  00  75  e7  48  8b  77  30 *42  03  8b  77  34 =....u.H.w0B..w4
fffff80002060010  4c  8d  4c *04  20  41  b8  05  00  00  00 *12  01  49  8b  cc L.L. A.......I..
fffff80002060020  e8  8b  72 *44  ff  48  3b  c3  74  34  8b *44  24  20  3b  eb ..rD.H;.t4.D$ ;.
fffff80002060030  74  2c  49 *02  fc  48  2b  fe  8b  50  04 *02  08  4c  8d  40 t,I..H+..P...L.@
...
fffff80002060080  8b  5c  24  40  48  83  c4  30  41  5c  c3 *10  90  90  90  90 .\$@H..0A\......
fffff80002060090  90  90  90 *10  90  90  90  90  90  90  90 *10  90  90  90  90 ................
fffff800020600a0  48  83  ec *10  4c  8b  c2  45  33  c9  33 *52  c7  44  24  28 H...L..E3.3R.D$(
fffff800020600b0  7b  00  00 *40  c7  44  24  20  18  00  00 *40  e8  ff  fe  ff {..@.D$ ...@....
...
fffff80002060100  41  b8  90 *00  00  00  e8  85  a6  c7  ff *12  d2  48  8b  cb A............H..
fffff80002060110  c7  83  cc *00  00  00  01  00  00  00  e8 *00  f4  ff  ff  8b ................
fffff80002060120  f0  3b  c5 *06  84  1a  01  00  00  8b  d0 *40  8b  cb  e8  3d .;.........@...=
fffff80002060130  93  ff  ff *10  02  78  00  00  66  3b  c1 *06  85  02  01  00 .....x..f;......
...
fffff80002060180  cb  e8  4a *52  ff  ff  8b  4b  2c  41  b8 *02  38  00  00  48 ..JR...K,A..8..H
fffff80002060190  8d  14  89 *40  8b  cb  66  89  44  d3  34 *02  d7  e8  ae  fa ...@..f.D.4.....
fffff800020601a0  ff  ff  3b *44  0f  84  99  00  00  00  45 *12  c0  8b  d0  48 ..;D......E....H
fffff800020601b0  8b  cb  e8 *10  f3  ff  ff  8b  4b  2c  41 *10  16  40  00  00 ........K,A..@..
...
fffff80002060200  00  00  8b *56  48  8b  cb  e8  44  fa  ff *56  3b  c5  74  27 ...VH...D..V;.t'
fffff80002060210  8b  4b  2c  44  8b  c7  48  8d  14  89  48 *02  cb  89  44  d3 .K,D..H...H...D.
fffff80002060220  30  ff  43 *04  8b  d6  e8  95  f9  ff  ff *02  f8  3b  c5  0f 0.C..........;..
fffff80002060230  85  22  ff *56  ff  eb  0c  8b  43  2c  48 *04  0c  80  66  89 .".V....C,H...f.
...
fffff80002060280  b7  e8  44 *06  b7  e2  48  8b  d9  41  8b *54  44  39  a9  cc ..D...H..A.TD9..
fffff80002060290  01  00  00 *54  05  e8  36  fe  ff  ff  41 *02  cd  4d  8b  cd ...T..6...A..M..
fffff800020602a0  48  8d  43 *14  66  44  39  28  74  3b  66  44  39  20  75  06 H.C.fD9(t;fD9 u.
fffff800020602b0  66  39  68  02  74  11  49  ff  c1  ff  c1 *40  83  c0  28  49 f9h.t.I....@..(I
...
fffff80002060300  90  90  90 *10  90  90  90  90  90  90  90 *10  90  90  90  90 ................
fffff80002060310  48  89  5c *04  08  48  89  74  24  10  57 *40  83  ec  20  33 H.\..H.t$.W@.. 3
fffff80002060320  db  8b  f2 *40  8b  f9  48  3b  cb  75  04 *12  c0  eb  4b  e8 ...@..H;.u....K.
fffff80002060330  3c  91  ff *56  b9  00  f0  00  00  66  23 *40  b9  00  80  00 <..V.....f#@....
...
fffff80002060380  8b  74  24 *10  48  83  c4  20  5f  c3  90 *10  90  90  90  90 .t$.H.. _.......
fffff80002060390  48  8b  c4 *40  89  58  08  48  89  70  10 *40  89  78  18  4c H..@.X.H.p.@.x.L
fffff800020603a0  89  60  20 *40  55  41  56  41  57  48  83 *44  30  33  db  33 .` @UAVAWH.D03.3
fffff800020603b0  ff  33  f6 *44  8b  e1  4d  8b  e8  4c  8b *52  4c  8b  f9  89 .3.D..M..L.RL...
...
fffff80002060400  fa  ff  ff *04  ff  75  04  85  c0  74  05 *16  01  00  00  00 .....u...t......
fffff80002060410  ff  c3  ff *46  89  5c  24  20  3b  74  24 *50  72  aa  48  8b ...F.\$ ;t$Pr.H.
fffff80002060420  5c  24  50 *40  8b  74  24  58  4c  8b  64 *04  68  8b  c7  48 \$P@.t$XL.d.h..H
fffff80002060430  8b  7c  24 *40  48  83  c4  30  41  5f  41 *56  41  5d  c3  90 .|$@H..0A_AVA]..
...
fffff80002060480  01  00  00 *40  b6  c0  41  0f  b6  cd  41 *12  cf  0f  84  a7 ...@..A...A.....
fffff80002060490  07  00  00 *00  e9  fb  00  00  00  0f  84 *10  07  00  00  83 ................
fffff800020604a0  e9  01  0f *04  b0  05  00  00  83  e9  01 *06  84  6d  07  00 .............m..
fffff800020604b0  00  83  e9 *00  0f  84  3b  01  00  00  83 *50  01  8b  cb  0f ......;....P....
...
fffff80002060500  83  e9  7f *06  84  59  05  00  00  83  e9  40  0f  84  0c  07 .....Y.....@....
fffff80002060510  00  00  83 *40  01  0f  85  1e  05  00  00 *40  8b  cf  e8  fd ...@.......@....
fffff80002060520  15  d1  ff  44  8b  c3  48  8b  ce  8b  d0 *40  30  51  fe  ff ...D..H....@0Q..
fffff80002060530  44  8b  f0 *40  3b  c7  0f  84  60  03  00  00  48  8b  cf  e8 D..@;...`...H...
...
fffff80002060580  d0  ff  41 *12  c7  0f  85  ff  05  00  00 *02  cb  e8  be  4a ..A............J
fffff80002060590  d0  ff  41 *12  c7  0f  85  c2  05  00  00 *00  fb  5a  11  00 ..A..........Z..
fffff800020605a0  00  7c  08 *00  fb  5e  11  00  00  7e  ba *00  fb  a3  11  00 .|...^...~......
fffff800020605b0  00  7c  08 *00  fb  a7  11  00  00  7e  aa *00  fb  fa  11  00 .|.......~......
...
fffff80002060600  0f  85  52  04  00  00  48  8b  47  10  0f *16  08  48  83  c0 ..R...H.G....H..
fffff80002060610  02  48  89 *46  10  b8  00  dc  00  00  66 *12  c8  0f  82  35 .H.F......f....5
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Dragon41673 · 06 May 2010

I should have noted...lastnight I ran memtest version 3.5 on multi core overnight for almost 9 hours...everything passed

Editing post now...

Any other ideas?

zigzag3143 · 06 May 2010

Dragon41673 said:

I should have noted...lastnight I ran memtest version 3.5 on multi core overnight for almost 9 hours...everything passed

Editing post now...

Any other ideas?

Was this DMP before of after? As you can see it is still pointing to memory. You may need to test the ram one stick at a time and one slot at a time.

Are you overclocking? running a RAID? Have you run a sfc /scannow?

Ken

Dragon41673 · 06 May 2010

The dump files from 5/4 were before...

Dump files from 5/6 are from after

Pulled one memory module now & re-running Memtest...

Let me make sure I'm using the correct one...here is where I went...
http://www.memtest86.com/ - Downloaded the version 3.5

Now I'm noticing that maybe that wasn't the correct one. There is also a Memtest 85 v4.10 here - http://www.memtest.org/

What one is correct???

Dragon41673 · 06 May 2010

Sorry...have to bump for edited content on Memtest Options

zigzag3143 · 06 May 2010

Dragon41673 said:

Sorry...have to bump for edited content on Memtest Options

You also in this one seem to have some sort of hardware issue. use these to find out what to try. https://www.sevenforums.com/crash-loc...-what-try.html

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\Crashes\050410-24757-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01c02000 PsLoadedModuleList = 0xfffff800`01e3fe50
Debug session time: Tue May  4 23:43:26.103 2010 (GMT-4)
System Uptime: 0 days 0:02:53.946
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000153131, fffff88009864450, 0}

Probably caused by : hardware ( win32k!xxxDCEWindowHitTest2+95 )

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

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

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

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


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

FAULTING_IP: 
win32k!xxxDCEWindowHitTest2+95
fffff960`00153131 0000            add     byte ptr [rax],al

CONTEXT:  fffff88009864450 -- (.cxr 0xfffff88009864450)
rax=0000000000000000 rbx=fffff900c0800b90 rcx=0000000000000000
rdx=0000000000000200 rsi=0000000000000001 rdi=00000000000003bf
rip=fffff96000153131 rsp=fffff88009864e20 rbp=00000000fffffffe
 r8=0000000000000000  r9=00000000018103bf r10=00000181000003bf
r11=fffff88009864ef8 r12=fffff88009864ff0 r13=0000000000000200
r14=0000000000000000 r15=00000000018103bf
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
win32k!xxxDCEWindowHitTest2+0x95:
fffff960`00153131 0000            add     byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!xxxDCEWindowHitTest2+95
fffff960`00153131 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff96000153053 to fffff96000153131

STACK_TEXT:  
fffff880`09864e20 fffff960`00153053 : 00000000`00000001 fffff900`c1debc30 00000000`00000000 00000000`00000001 : win32k!xxxDCEWindowHitTest2+0x95
fffff880`09864f00 fffff960`000afbd8 : 00000000`00000001 fffff880`09865520 00000000`000003bf 00000000`00000000 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`09864f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxScanSysQueue+0x115c


FOLLOWUP_IP: 
win32k!xxxDCEWindowHitTest2+95
fffff960`00153131 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!xxxDCEWindowHitTest2+95

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88009864450 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Dragon41673 · 06 May 2010

1) Ensure that none of the hardware components are overclocked.- Nothing is overclocked

2) Ensure that the machine is adequately cooled. -Definitely cooled, 120mm Scythe on the back of the case, 120mm Scythe on the Thermalrite Ultra 120 Extreme, and 140mm Aerocool on the side

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... - Already done

4) Update the motherboard BIOS according to the manufacturer's instructions. - Newest BIOS was installed last month

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). - I hope this is it

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. Will do... - Running Memtest again as we speak on 1 of 2 modules

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: - Unfortunately this would have to wait until after the honeymoon...just no time to do it

zigzag3143 · 06 May 2010

Dragon41673 said:

1) Ensure that none of the hardware components are overclocked.- Nothing is overclocked

2) Ensure that the machine is adequately cooled. -Definitely cooled, 120mm Scythe on the back of the case, 120mm Scythe on the Thermalrite Ultra 120 Extreme, and 140mm Aerocool on the side

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... - Already done

4) Update the motherboard BIOS according to the manufacturer's instructions. - Newest BIOS was installed last month

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). - I hope this is it

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. Will do... - Running Memtest again as we speak on 1 of 2 modules

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: - Unfortunately this would have to wait until after the honeymoon...just no time to do it

The one easy thing you can do to verify your system files if you already havent is a system file check (type cmd in search>right click and run as admin>
sfc /scannow)

Ken Good luck

Dragon41673 · 06 May 2010

Awesome...I will try that when I'm done with the Memtest...am I using the correct version? I was going to stop the test & use the other Memtest v4.10...but I'm already 30 min into the v3.5 from the other site. The screen that is displayed right now says Memtest-86 v3.5

Nice...I just checked the screen to make sure I'm typing it correctly...Screen says Pass #1...but I swear I've seen it run though tests 2 times already. Test 5 has 2 errors already and it's currently on test 7.

Would it be safe to say I should pull that module as it IS bad and start on the other module???