help in bsod crashes in windows 7

[palidanx]

Hi everyone,

I've been having some crazy crashes, and been trying to make some sense out of it... any assitance would be helpful.

I get a mix of errors from SPECIAL_MEMORY_POOL to general memory errors. I'm not sure if it's my drivers or my memory. Memtest x86 seems to be passing when my ram settings are on auto. Recently i just got a bsod.

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000089b3001
Arg3: 00000000000150bc
Arg4: fffff70001080000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002acfa63 to fffff80002a78f00

STACK_TEXT:
fffff880`07871218 fffff800`02acfa63 : 00000000`0000001a 00000000`00041284 00000000`089b3001 00000000`000150bc : nt!KeBugCheckEx
fffff880`07871220 fffff800`02aabb49 : fffffa80`040e2ec8 ffffffff`ffffffff fffffa80`03fc4b60 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`07871260 fffff800`02abf66b : 8bc00000`594e2867 fffff680`00044d98 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`078712a0 fffff800`02aba95e : 00000000`00000002 fffff880`00000000 fffffa80`040e2b30 fffffa80`040e2ec8 : nt!MiDecommitPages+0x20b
fffff880`07871b30 fffff800`02a78153 : ffffffff`ffffffff 00000000`000fe1f0 00000000`000fe1e8 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`07871c20 00000000`778b009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000fe1b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778b009a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`02acfa63 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

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

Uploaded is msinfo and my crash dump.. any insights would be greatly appreciated.

 

[palidanx]

oops forgot to attach mini dump

here is the mini dump.

 

[sullysnet]

you said that Memtest x86 passes the test in Auto but are you overclocking the memory or setting them manually to the correct setting (timing). Have you tried Windows Memory test inside Win7?? I find that I like to use that one and Memtest x86 just to make sure. Sounds like a memory issue from here but could be something else like CPU or Motherboard. I had crashes on a machine that I swore had bad memory and it ended up being the CPU (last time I buy OEM CPU). The memory testing application would still pick up on my error. I had borrowed some memory so I could test to make sure it was the CPU.

 

[palidanx]

Hey Sullsnet.


I have this memory
http://www.corsair.com/_datasheets/twin2x2048-8500c5d.pdf

and for the life of me when I set it to the correct settings i get way more blue screens. Upon reading more forums about that memory, they said that for each motherboard the timings may be different (etc etc).

The memory currently isn't being overclocked. Just auto settings in the bios.

I"ll run the memory diagnostics test in windows and tell you what i get.

 

[sullysnet]

I wonder if this is a NIC driver issue?? Doesn't point to that but it seems that Firefox is triggering the crash, so I question something like that.

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000089b3001
Arg3: 00000000000150bc
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002acfa63 to fffff80002a78f00

STACK_TEXT:  
fffff880`07871218 fffff800`02acfa63 : 00000000`0000001a 00000000`00041284 00000000`089b3001 00000000`000150bc : nt!KeBugCheckEx
fffff880`07871220 fffff800`02aabb49 : fffffa80`040e2ec8 ffffffff`ffffffff fffffa80`03fc4b60 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`07871260 fffff800`02abf66b : 8bc00000`594e2867 fffff680`00044d98 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`078712a0 fffff800`02aba95e : 00000000`00000002 fffff880`00000000 fffffa80`040e2b30 fffffa80`040e2ec8 : nt!MiDecommitPages+0x20b
fffff880`07871b30 fffff800`02a78153 : ffffffff`ffffffff 00000000`000fe1f0 00000000`000fe1e8 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`07871c20 00000000`778b009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000fe1b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778b009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`02acfa63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

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

 

[sullysnet]

You know what is crazy I had that same memory and blue screens with it. I am or was using it with an ASUS Maximus Forumla motherboard and I had issues with that memory two times. I still have a brand new set of that memory from my RMA return. I found out that on my ASUS board that my memory voltage even though set to auto was set to high. It was or needed to be set to (I think) 2.0 but when I reviewed it in the BIOS and with something like CPUz it was set much higher than 2.0. Again I would have to reboot and look at my settings but this was my case with this memory. I opted to buy Gskill 4G kit same speed and set my memory on voltage by hand and get it as close as I could to the correct setting. I went with Gskill because others that had this same issue moved to this memory and I have to say I do like their memory. I will by buying it again (I think) on my next rebuild.

I hope that helps a bit or at least leads you in the correct direction

Oh this was my settings also (5-5-5-15-2T) at 2.1V and I had to set the 5-5-5-15 by hand and the 2.1 is listed but mine was something like 2.5 when I reviewed it with ASUS PC probe and in the BIOS.

Hey Sullsnet.


I have this memory
http://www.corsair.com/_datasheets/twin2x2048-8500c5d.pdf

and for the life of me when I set it to the correct settings i get way more blue screens. Upon reading more forums about that memory, they said that for each motherboard the timings may be different (etc etc).

The memory currently isn't being overclocked. Just auto settings in the bios.

I"ll run the memory diagnostics test in windows and tell you what i get.

 

[palidanx]

for further curiosity here are my cpu-z reports

 

[usasma]

Special Pool and this sort of stuff in the stack text:

fffff880`07871c20 00000000`778b009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000fe1b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778b009a

Indicates to me that it's a 3rd party program that's causing it.
Driver Verifier may force it out in the open - but otherwise it's a matter of getting enough BSOD's to identify the pattern that causes it.

Try these instructions for Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and waitfor it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn offDriver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[palidanx]

cool.. i put in those settings.. lets hope it reappears.

 

[palidanx]

My computer just blew up again and now I got..

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9801e820e90, address trying to free
Arg2: fffff9801e8203b1, address where one bit is corrupted
Arg3: 0000000000dd4170, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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

Unable to load image \SystemRoot\System32\Drivers\avgtdia.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys

BUGCHECK_STR: 0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE: 32

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002b0b593 to fffff80002a7cf00

STACK_TEXT:
fffff880`031c4538 fffff800`02b0b593 : 00000000`000000c1 fffff980`1e820e90 fffff980`1e8203b1 00000000`00dd4170 : nt!KeBugCheckEx
fffff880`031c4540 fffff800`02b82613 : 00000000`00000003 fffff800`02f0867c 00000000`00000293 fffff800`02f0761a : nt!MiCheckSpecialPoolSlop+0x83
fffff880`031c4580 fffff800`02bae356 : 00000000`000004ca 00000000`55677641 00000000`00036160 fffff980`1e820e90 : nt!MmFreeSpecialPool+0x1d3
fffff880`031c46b0 fffff880`0196b150 : fffff980`1e820e90 fffff980`1e820e90 fffff980`224e6ea0 fffff980`1e820e90 : nt!ExFreePool+0x9f3
fffff880`031c4760 fffff980`1e820e90 : fffff980`1e820e90 fffff980`224e6ea0 fffff980`1e820e90 fffffa80`04cf6990 : avgtdia+0x1150
fffff880`031c4768 fffff980`1e820e90 : fffff980`224e6ea0 fffff980`1e820e90 fffffa80`04cf6990 fffff880`0196f007 : 0xfffff980`1e820e90
fffff880`031c4770 fffff980`224e6ea0 : fffff980`1e820e90 fffffa80`04cf6990 fffff880`0196f007 fffff980`00000001 : 0xfffff980`1e820e90
fffff880`031c4778 fffff980`1e820e90 : fffffa80`04cf6990 fffff880`0196f007 fffff980`00000001 fffffa80`04cf6990 : 0xfffff980`224e6ea0
fffff880`031c4780 fffffa80`04cf6990 : fffff880`0196f007 fffff980`00000001 fffffa80`04cf6990 fffffa80`05857cf0 : 0xfffff980`1e820e90
fffff880`031c4788 fffff880`0196f007 : fffff980`00000001 fffffa80`04cf6990 fffffa80`05857cf0 fffff980`224e6ea0 : 0xfffffa80`04cf6990
fffff880`031c4790 fffff980`00000001 : fffffa80`04cf6990 fffffa80`05857cf0 fffff980`224e6ea0 fffffa80`05d1b6b0 : avgtdia+0x5007
fffff880`031c4798 fffffa80`04cf6990 : fffffa80`05857cf0 fffff980`224e6ea0 fffffa80`05d1b6b0 fffff880`0196f116 : 0xfffff980`00000001
fffff880`031c47a0 fffffa80`05857cf0 : fffff980`224e6ea0 fffffa80`05d1b6b0 fffff880`0196f116 fffff980`224e6ea0 : 0xfffffa80`04cf6990
fffff880`031c47a8 fffff980`224e6ea0 : fffffa80`05d1b6b0 fffff880`0196f116 fffff980`224e6ea0 00000000`00000002 : 0xfffffa80`05857cf0
fffff880`031c47b0 fffffa80`05d1b6b0 : fffff880`0196f116 fffff980`224e6ea0 00000000`00000002 fffffa80`05857cf0 : 0xfffff980`224e6ea0
fffff880`031c47b8 fffff880`0196f116 : fffff980`224e6ea0 00000000`00000002 fffffa80`05857cf0 fffffa80`05d1b6b0 : 0xfffffa80`05d1b6b0
fffff880`031c47c0 fffff980`224e6ea0 : 00000000`00000002 fffffa80`05857cf0 fffffa80`05d1b6b0 fffff980`224e6ea0 : avgtdia+0x5116
fffff880`031c47c8 00000000`00000002 : fffffa80`05857cf0 fffffa80`05d1b6b0 fffff980`224e6ea0 fffff800`02f22c16 : 0xfffff980`224e6ea0
fffff880`031c47d0 fffffa80`05857cf0 : fffffa80`05d1b6b0 fffff980`224e6ea0 fffff800`02f22c16 fffff980`224e6ea0 : 0x2
fffff880`031c47d8 fffffa80`05d1b6b0 : fffff980`224e6ea0 fffff800`02f22c16 fffff980`224e6ea0 00000000`00000002 : 0xfffffa80`05857cf0
fffff880`031c47e0 fffff980`224e6ea0 : fffff800`02f22c16 fffff980`224e6ea0 00000000`00000002 fffffa80`05857cf0 : 0xfffffa80`05d1b6b0
fffff880`031c47e8 fffff800`02f22c16 : fffff980`224e6ea0 00000000`00000002 fffffa80`05857cf0 00000000`00000000 : 0xfffff980`224e6ea0
fffff880`031c47f0 fffff800`02d9068f : fffff980`224e6ea0 fffffa80`039ee040 00000000`00000000 fffffa80`05d1b6b0 : nt!IovCallDriver+0x566
fffff880`031c4850 fffff800`02d76304 : 00000000`00000000 fffffa80`039ee040 fffff8a0`00001a60 00000000`00000000 : nt!IopCloseFile+0x11f
fffff880`031c48e0 fffff800`02d90181 : fffffa80`039ee040 fffffa80`00000001 fffff8a0`00001a60 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`031c4960 fffff800`02d90094 : 00000000`00002320 fffffa80`039ee040 fffff8a0`00001a60 00000000`00002320 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`031c49f0 fffff800`02a7c153 : fffffa80`0460b040 fffff880`031c4ac0 fffff880`02cb8c90 fffffa80`0460b148 : nt!ObpCloseHandle+0x94
fffff880`031c4a40 fffff800`02a786f0 : fffff880`02ce7847 fffffa80`046b8570 fffff880`02cc97f0 fffff880`02cb8c90 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031c4bd8 fffff880`02ce7847 : fffffa80`046b8570 fffff880`02cc97f0 fffff880`02cb8c90 fffff800`02a87ac1 : nt!KiServiceLinkage
fffff880`031c4be0 fffff880`02c95357 : fffffa80`046b8570 fffff880`02cb8c90 fffff880`031c4c48 00000000`00000018 : afd! ?? ::GFJBLGFE::`string'+0x3a59
fffff880`031c4c20 fffff880`02c94ff7 : fffffa80`04ad0bc0 fffff880`02cb8c90 fffff880`02cc97f0 fffffa80`0460b040 : afd!AfdFreeConnectionEx+0x27
fffff880`031c4c50 fffff800`02d76527 : fffff980`02604fc0 fffffa80`05b788c0 fffff800`02c205f8 fffffa80`0460b040 : afd!AfdDoWork+0x67
fffff880`031c4c80 fffff800`02a8a161 : fffff800`02c20500 fffff800`02d76504 fffffa80`0460b040 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031c4cb0 fffff800`02d20166 : 00000000`00000000 fffffa80`0460b040 00000000`00000080 fffffa80`039ee040 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02a5b486 : fffff880`02f64180 fffffa80`0460b040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
avgtdia+1150
fffff880`0196b150 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: avgtdia+1150

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avgtdia

IMAGE_NAME: avgtdia.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4aeeddf5

FAILURE_BUCKET_ID: X64_0xC1_32_VRF_avgtdia+1150

BUCKET_ID: X64_0xC1_32_VRF_avgtdia+1150

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

1: kd> lmvm avgtdia
start end module name
fffff880`0196a000 fffff880`019df000 avgtdia T (no symbols)
Loaded symbol image file: avgtdia.sys
Image path: \SystemRoot\System32\Drivers\avgtdia.sys
Image name: avgtdia.sys
Timestamp: Mon Nov 02 05:26:13 2009 (4AEEDDF5)
CheckSum: 0007DE20
ImageSize: 00075000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

I have avg free anti virus installed. Could this be the bugger causes my problems?

 

[sullysnet]

have you tried removing AVG?? In your dump it shows avgtdia.sys
Seems strange thought that you have so many memory errors but no issue with your memory.

What is your full system specs

thanks

 

[torrentg]

Always completely uninstall AVG. AVG is worse than a virus, seriously.

 

[palidanx]

hm.. i ran memtest again just for kicks now its barfing all over the place.. let me get some new memory and retest this thing.. growl.....

 

[sullysnet]

hm.. i ran memtest again just for kicks now its barfing all over the place.. let me get some new memory and retest this thing.. growl.....

trust me friend I had the same issue, RMA it and once you get it we can see if your RAM voltage settings are too high or correct. Let me know once you have spares

If you can give me your full specs that would be great, thanks

 

[fmlydde101]

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
its being caused by: ntoskrnl.exe

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

 

[palidanx]

Just wanted to provide an update. I got some cheapy crucial ram temporarily to see what was going on, and so far no bsod for a couple of days (albeit the system is slow). I ordered some gskill memory and it should be coming in today so hopefully is good *crosses fingers*

 

[palidanx]

My computer is starting to barf again.. is this pointing to general memory issues (installed 4gig gskill ram)

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800242e7d0
Arg3: fffffa8001fa8800
Arg4: 0000000000000504

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


BUGCHECK_STR: 0x1a_8884

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002b7fdf6 to fffff80002ad2f00

STACK_TEXT:
fffff880`060ab8b8 fffff800`02b7fdf6 : 00000000`0000001a 00000000`00008884 fffffa80`0242e7d0 fffffa80`01fa8800 : nt!KeBugCheckEx
fffff880`060ab8c0 fffff800`02bde5f5 : fffffa80`04763438 fffffa80`04764000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`060ab930 fffff800`02ee4064 : fffffa80`04762000 fffff880`060abca0 fffff880`060aba08 00000000`000cff01 : nt!MmSetPfnListPriorities+0x175
fffff880`060ab980 fffff800`02f44d7a : 00000000`00000020 00000000`00000000 fffffa80`04762000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`060ab9d0 fffff800`02f494be : 00000000`00000000 00000000`01a4b490 00000000`0000004f 00000000`00000001 : nt!PfSetSuperfetchInformation+0x199
fffff880`060abab0 fffff800`02ad2153 : fffffa80`065d5b60 00000000`03065f28 00000000`00000000 00000000`0307ef30 : nt!NtSetSystemInformation+0xb91
fffff880`060abc20 00000000`779515aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a4b418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779515aa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+c6
fffff800`02b7fdf6 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1a_8884_VRF_nt!MiRelinkStandbyPage+c6

BUCKET_ID: X64_0x1a_8884_VRF_nt!MiRelinkStandbyPage+c6

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

In addition to setting cas settings, do i need to bump up my NB voltage?

 

[torrentg]

Post the actual .dmp in a rar attached to a post.

 

[palidanx]

Hey guys,

I just ran memtest x86 on my new gskill ram last night and I set it to

5-5-5-15, pc1066 2.02v

I noticed thought when reading memtest it said the settings were

8-5-5-15

is There any reason the cl is off?

Thanks

 

[sullysnet]

Hey guys,

I just ran memtest x86 on my new gskill ram last night and I set it to

5-5-5-15, pc1066 2.02v

I noticed thought when reading memtest it said the settings were

8-5-5-15

is There any reason the cl is off?

Thanks

Not sure why memtest would read it that way but I would trust your BIOS settings and CPU-Z. Mine is set to 5-5-5-15 and it reads it correctly in CPU-z.