Random BSOD

Joined
Nov 28, 2010
Messages
4
Reaction score
0
Hello,

I've been having random BSOD issues with no obvious reasons. I'm running Windows 7 on my first home-built PC that I recently built. I've tried to diagnose the problem on my own using the Windows Debugging Tool, and have identified about three different bug check codes that are often cited as a cause of the BSOD:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
PAGE_FAULT_IN_NONPAGED_AREA (50)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Most of my drivers have been kept up to date, but yesterday, I manually verified that all drivers were in fact the latest version, including network, RAID, chipset, BIOS, video, and all peripheral drivers. I have two 1TB hard drives in a RAID 1 configuration, and apparently it was in a degraded state (unknown to me) up until yesterday when I installed the new Intel Matrix Storage Management driver. After the RAID drive rebuilt itself and after installing all these new drivers, I'm still getting a random BSOD happening. Oh yeah, and I have checked the memory using the Windows Memory Diagnostic tool, and everything checked out fine.

So, anyways I'm at a loss. Not sure what to do from here. I've attached the Minidump folder contents. Hopefully, you can gain some further insight into the reason for all of this.

Thanks,
Justin

Here's some parts info on my build:
Intel Core i7-920 Bloomfield
EVGA E758-A1 3-way SLI X58 Intel Mobo
OCZ Gold 6GB (3 x 2GB) 240-pin DDR3
Nvidia 9600GT Video card
Using on board sound and Lan
Windows 7 Home Premium 64-bit
Corsair 650W PS
Western Digital 500GB HD (system disk)
2 x Western Digital 1TB HD (RAID 1 config)
 

Attachments

Ross

Microsoft MVP
Joined
Aug 9, 2009
Messages
117
Reaction score
31
Hi Justwake20,

I'd check your RAM again (as well as settings in the bios) but use the free app found here:

http://www.memtest.org/

Check each stick individually.

Also could you list which security apps your using?
 
Joined
Nov 28, 2010
Messages
4
Reaction score
0
Ross,

Thanks for the reply.

I downloaded the memtest86 tool and its currently still running on its 3rd pass, but it had reported over 1,000 errors by the second pass. I guess this means I have some bad memory sticks?? (This is usually why my lab computers at work are failing too - why can't they make this stuff more reliable??)

Coincidentally, last night, before I ran this memory test, my machine blue screened with a different bug check code, this one citing something about memory failures... (I attached this dump file if you're interested.)

This memory diagnostic tool is pretty nice. It seems way more thorough than the Windows memory test.

I guess I need to try the RMA route to get my memory replaced.

Don't know if it matters now, but I run Symantec Endpoint Protection for my antivirus. That's the only one I have. I think I'm using the windows firewall though, not Symantec's.


Anyways, thanks for taking the time to look into this. Much appreciated.

- Justin
 

Attachments

Joined
Nov 28, 2010
Messages
4
Reaction score
0
I've been researching this memory, and it seems like other people have had issues with it too. I did notice the memory timing showed 8-8-8-18 when running memtest, but the manufacturer calls for 8-8-8-24, so I just changed that and am now in the process of running memtest on each stick individually. I'm not sure how sensitive the system is to these timings as I don't know that much about them. Only things I changed in the BIOS for memory was the timings 8-8-8-24 and the voltage to the recommended 1.65V. Other than that, everything was left as AUTO. This was done only because the mobo or memory didn't default to these settings. I've also been reading something about a multiplier. I'm not sure what that is, but it probably has something to do with overclocking. I'm not really interested in overclocking the memory though. Manufacturer says it can run at 1600MHz, but I just left it alone at the default speed, 1066MHz.

Justin
 
Joined
Sep 19, 2010
Messages
87
Reaction score
12
RAM voltage settings left on 'auto' in the BIOS can cause problems and BSODs. I know this first hand. When I manually configured my RAM voltage settings, the BSODs disappeared completely.
 
Joined
Sep 22, 2010
Messages
613
Reaction score
102
Ross,

Thanks for the reply.

I downloaded the memtest86 tool and its currently still running on its 3rd pass, but it had reported over 1,000 errors by the second pass. I guess this means I have some bad memory sticks??
You do need to replace ram unless the settings in the bios are wrong. If you haven't recently changed anything in the bios, this means you got a bad ram for sure.

If this wasn't caused by bad ram, I'd recommend you uninstall Symantec and update Intel Matrix Storage driver. But in your case it won't help because memtest showing1000 errors means defective RAM. Replace it.




~~~~~~~~~~~~~


Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\112810-28782-01.dmp]

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Debug session time: Sun Nov 28 17:30:45.679 2010 (UTC - 5:00)
System Uptime: 0 days 5:13:46.959

.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d6922c, fffff8800c5ded30, 0}

Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+40 )


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

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!MiApplyCompressedFixups+40
fffff800`02d6922c 0fb603          movzx   eax,byte ptr [rbx]

CONTEXT:  fffff8800c5ded30 -- (.cxr 0xfffff8800c5ded30)
rax=fffff8a005957000 rbx=0000008400000000 rcx=fffffa8009f82580
rdx=fffff8800b9a7000 rsi=0000000001c20000 rdi=fffff8800b9a7000
rip=fffff80002d6922c rsp=fffff8800c5df700 rbp=0000000000000003
 r8=0000008400000001  r9=0000000001c20000 r10=0000000000000fff
r11=fffff8800b9a7000 r12=fffffa8009f82580 r13=000000000000ff7f
r14=fffffa8009f82580 r15=fffffa8009f82580
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiApplyCompressedFixups+0x40:
fffff800`02d6922c 0fb603          movzx   eax,byte ptr [rbx] ds:002b:00000084`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002d6922c

STACK_TEXT:  
fffff880`0c5df700 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiApplyCompressedFixups+0x40


FOLLOWUP_IP: 
nt!MiApplyCompressedFixups+40
fffff800`02d6922c 0fb603          movzx   eax,byte ptr [rbx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiApplyCompressedFixups+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800c5ded30 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiApplyCompressedFixups+40

BUCKET_ID:  X64_0x3B_nt!MiApplyCompressedFixups+40




start             end                 module name
fffff880`0464f000 fffff880`0468d000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f6f000 fffff880`00fc6000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`04412000 fffff880`0449c000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0468d000 fffff880`046a3000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0122a000 fffff880`01235000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`099c5000 fffff880`099d0000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`013d0000 fffff880`013d9000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01200000 fffff880`0122a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`00980000 fffff960`009e1000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
fffff880`03e14000 fffff880`03e1b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0479f000 fffff880`047b0000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`057b8000 fffff880`057d6000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`007b0000 fffff960`007d7000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`02f8b000 fffff880`02fb5000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ea0000 fffff880`00f60000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01bcc000 fffff880`01bfc000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cf8000 fffff880`00d56000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`055e6000 fffff880`055f6000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`04400000 fffff880`0440e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04781000 fffff880`0479f000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04772000 fffff880`04781000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01bb6000 fffff880`01bcc000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05d73000 fffff880`05d95000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`02f71000 fffff880`02f84000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`02e55000 fffff880`02f71000   dump_iaStor dump_iaStor.sys Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`015e8000 fffff880`015f4000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`05878000 fffff880`0596c000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0596c000 fffff880`059b2000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`046d7000 fffff880`0474d000   eeCtrl64 eeCtrl64.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`03fd9000 fffff880`03ff9000   ENG64    ENG64.SYS    Wed Sep 15 06:25:35 2010 (4C909F1F)
fffff880`0474d000 fffff880`04772000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD)
fffff880`03e1b000 fffff880`03fd9000   EX64     EX64.SYS     Wed Sep 15 06:33:41 2010 (4C90A105)
fffff880`01281000 fffff880`01295000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01235000 fffff880`01281000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015de000 fffff880`015e8000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01b7c000 fffff880`01bb6000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0168b000 fffff880`016d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`059ef000 fffff880`059fc000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02fed000 fffff800`03036000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`059bf000 fffff880`059e3000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05cda000 fffff880`05d36000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`05db9000 fffff880`05dd2000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05dd2000 fffff880`05dda080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05dab000 fffff880`05db9000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`056f0000 fffff880`057b8000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01b73000 fffff880`01b7c000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`012b4000 fffff880`013d0000   iaStor   iaStor.sys   Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`01079000 fffff880`01197000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`047d6000 fffff880`047ec000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`047ec000 fffff880`047fb000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`01a00000 fffff880`01a0e000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bcd000 fffff800`00bd7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`05c16000 fffff880`05c59000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`015b3000 fffff880`015cd000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05d95000 fffff880`05d9a200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05ddd000 fffff880`05df2000   LHidFilt LHidFilt.Sys Thu Mar 18 04:51:17 2010 (4BA1E985)
fffff880`056c3000 fffff880`056d8000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05c00000 fffff880`05c14000   LMouFilt LMouFilt.Sys Thu Mar 18 04:51:24 2010 (4BA1E98C)
fffff880`0567f000 fffff880`056a2000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`05d9b000 fffff880`05dab000   LUsbFilt LUsbFilt.Sys Thu Mar 18 04:51:28 2010 (4BA1E990)
fffff880`00ca0000 fffff880`00ce4000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`01400000 fffff880`0140e000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`045ee000 fffff880`045fd000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05df2000 fffff880`05dff000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e81000 fffff880`00e9b000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`057d6000 fffff880`057ee000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`05600000 fffff880`0562d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0562d000 fffff880`0567b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`094df000 fffff880`09502000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01a83000 fffff880`01a8e000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fcf000 fffff880`00fd9000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01197000 fffff880`011f5000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`045c8000 fffff880`045d3000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01b61000 fffff880`01b73000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016da000 fffff880`017cc000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`046c7000 fffff880`046d3000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`00c5c000 fffff880`00c8b000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05cc5000 fffff880`05cda000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`04510000 fffff880`0451f000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`0449c000 fffff880`044e1000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01a8e000 fffff880`01a9f000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`045bc000 fffff880`045c8000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a11000 fffff800`02fed000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01410000 fffff880`015b3000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02feb000 fffff880`02ff4000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`055e4000 fffff880`055e5180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffff880`04a0a000 fffff880`055e3a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffff880`044ea000 fffff880`04510000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e6a000 fffff880`00e71000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e71000 fffff880`00e81000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015cd000 fffff880`015de000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`09502000 fffff880`095a8000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05d36000 fffff880`05d73000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00ce4000 fffff880`00cf8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`046a3000 fffff880`046c7000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`045d3000 fffff880`045ee000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`017df000 fffff880`01800000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`01295000 fffff880`012af000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0456b000 fffff880`045bc000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02e43000 fffff880`02e4c000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02e4c000 fffff880`02e55000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02ff4000 fffff880`02ffd000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01b27000 fffff880`01b61000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`056d8000 fffff880`056f0000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`09800000 fffff880`09856000   Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95)
fffff880`095a8000 fffff880`095b3000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`059e3000 fffff880`059ef000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0451f000 fffff880`0453c000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01b1f000 fffff880`01b27000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01a0e000 fffff880`01a83000   SRTSP64  SRTSP64.SYS  Thu Mar 04 22:21:57 2010 (4B9078D5)
fffff880`03e00000 fffff880`03e14000   SRTSPX64 SRTSPX64.SYS Thu Mar 04 22:22:14 2010 (4B9078E6)
fffff880`09883000 fffff880`09919000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`09400000 fffff880`09467000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`095b3000 fffff880`095e0000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`05870000 fffff880`05871480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`02fb5000 fffff880`02feb000   SYMEVENT64x86 SYMEVENT64x86.SYS Wed Jun 24 16:19:12 2009 (4A428A40)
fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`095e0000 fffff880`095f2000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`01abd000 fffff880`01aca000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01a9f000 fffff880`01abd000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`013d9000 fffff880`013ff000   teefer2  teefer2.sys  Mon Dec 28 14:42:21 2009 (4B390A1D)
fffff880`04557000 fffff880`0456b000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00460000 fffff960`0046a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`047b0000 fffff880`047d6000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`05c59000 fffff880`05c6b000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`00fd9000 fffff880`00ff6000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`05ddb000 fffff880`05ddcf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`05856000 fffff880`05867000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05c6b000 fffff880`05cc5000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`05800000 fffff880`05856000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`059b2000 fffff880`059bf000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02e00000 fffff880`02e0e000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02e0e000 fffff880`02e33000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   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`01ad3000 fffff880`01b1f000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0453c000 fffff880`04557000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02e33000 fffff880`02e43000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d56000 fffff880`00dfa000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f60000 fffff880`00f6f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`044e1000 fffff880`044ea000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00030000 fffff960`0033f000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
fffff880`05867000 fffff880`05870000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00fc6000 fffff880`00fcf000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`017cc000 fffff880`017df000   wpsdrvnt wpsdrvnt.sys Sat Apr 10 13:41:34 2010 (4BC0B84E)
fffff880`09919000 fffff880`09954000   WpsHelper WpsHelper.sys Thu Sep 02 21:15:06 2010 (4C804C1A)
fffff880`056a2000 fffff880`056c3000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`09954000 fffff880`099a3000   Rt64win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0004F000
fffff880`09800000 fffff880`09856000   Rt64win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00056000
fffff880`04600000 fffff880`0464f000   Rt64win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0004F000
fffff880`09954000 fffff880`099c5000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`01a00000 fffff880`01a0e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`02e5c000 fffff880`02f78000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0011C000
fffff880`02f78000 fffff880`02f8b000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
 

Ross

Microsoft MVP
Joined
Aug 9, 2009
Messages
117
Reaction score
31
If memtest is still throwing up errors after your changes to the bios settings then the RAM is definitely bad and needs replacing.
 
Joined
Nov 28, 2010
Messages
4
Reaction score
0
Well, I searched reviews of this memory on Newegg and read some posts in the OCZ forum and found that I still had a couple of other timing values and voltages to change to match OCZ's recommended settings. But, after changing those manually, I reran each of the sticks through memtest and one stick repeatedly gives me buttloads of errors. The other two sticks always seem to check out just fine.

I've submitted a support ticket through OCZ's website to RMA the memory. Hopefully, this process won't be too painful. I'm thinking about just outright purchasing a new set of the same memory. Surely, I could get 3 out 6 sticks to work, right? (Maybe could even have a spare stick or two). Someone really needs to crack down on the poor quality of memory manufacturing processes these days, you know? Anyways - enough griping.

Thanks for everyone's help. Forums like these are nice for guys like me who has little experience with this stuff.

- Justin
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top