New Computer, constant BSOD.

[ArchmageR]

Hi there, i keep getting this Bsod at random intervals while playing games or while multitasking:

Memory_Dump:

Stop: 0x0000001A (0x0000000000041284,0x0000000043455001,0x000000000004F17B,0xFFFFF70001080000)

My system specs are in my profile.

Things I have tried:

Going down to 6gb Ram = Pc works perfectly, though I would like to use all the ram.

Switching around on the ram (testing 3 and 3 different sticks of ram) = Pc works perfectly though like I said would like to use all the ram I paid for.

Memtest 86x+ found no error at one test.

Contacting Netshop.No (which is where I bought the computer) = Only telling me to find out which ram stick is broken and send it in, also the ones who told me that the ram was the fault in the first place. However they will only send me new ram if I find out which of the ram sticks are broken.

Updated to latest drivers for my Graphic card (couldn`t hurt)

Found out that the motherboard was not able to give proper voltage to ram when set to "auto" due to production failure with motherboards bought around "febuary/mars", manually set it in bios to 1.64.

I`m at a loss on what to do, have included my .dmp file in this rar.

Hope you can help!

 

[zigzag3143]

Hi there, i keep getting this Bsod at random intervals while playing games or while multitasking:

Memory_Dump:

Stop: 0x0000001A (0x0000000000041284,0x0000000043455001,0x000000000004F17B,0xFFFFF70001080000)

My system specs are in my profile.

Things I have tried:

Going down to 6gb Ram = Pc works perfectly, though I would like to use all the ram.

Switching around on the ram (testing 3 and 3 different sticks of ram) = Pc works perfectly though like I said would like to use all the ram I paid for.

Memtest 86x+ found no error at one test.

Contacting Netshop.No (which is where I bought the computer) = Only telling me to find out which ram stick is broken and send it in, also the ones who told me that the ram was the fault in the first place. However they will only send me new ram if I find out which of the ram sticks are broken.

Updated to latest drivers for my Graphic card (couldn`t hurt)

Found out that the motherboard was not able to give proper voltage to ram when set to "auto" due to production failure with motherboards bought around "febuary/mars", manually set it in bios to 1.64.

I`m at a loss on what to do, have included my .dmp file in this rar.

Hope you can help!

It appears WAR.exe caused a PTE memory crash. You are on the right path testing the memory sticks one at a time. Coulod also be a heat issue. I would download cpu-z, and gpu-z (both free) to keep an eye on the temps.

I would also run a system file check to verify a nd repair your system files
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results

Ken

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


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

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e55e50
Debug session time: Fri Apr 30 03:29:24.694 2010 (GMT-4)
System Uptime: 0 days 2:41:32.833
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 43455001, 4f17b, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

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

4: 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: 0000000043455001
Arg3: 000000000004f17b
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WAR.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cdedf3 to fffff80002c88600

STACK_TEXT:  
fffff880`0a671928 fffff800`02cdedf3 : 00000000`0000001a 00000000`00041284 00000000`43455001 00000000`0004f17b : nt!KeBugCheckEx
fffff880`0a671930 fffff800`02cb9315 : fffff700`01080000 97b00001`7a21a847 ef300000`7054fc46 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`0a671970 fffff800`02cc9fca : 00000000`00000000 00000000`43540fff fffffa80`00000000 fffffa80`0a131060 : nt!MiDeleteVirtualAddresses+0x4cc
fffff880`0a671b30 fffff800`02c87853 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0a671c20 00000000`7713009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7713009a


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

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

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

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

 

[ArchmageR]

Small update:

Did a Memtest86x+ with alle the ram sticks inside, seven test passes (which is the recommended amount of passes according to a guide I found). = Took 17 hours, and produced no ram errors.

Did a system file check. = No errors found

going to download the programs you mentioned, aswell as test the memory sticks 1 at a time.

thanks for the help so far , i`l report back after im done.

Oh, and do those programs save a log of some kind? Im not that good with computers, and I have no idea how hot/cold the computer should be, and since I have to play to wait for the computer to crash, how do I check the temperature at the moment of the crash?

 

[ArchmageR]

Don`t know if this help, but had the programs running in the background while the pc crashed, this is what Gpu-z recorded:

 

[ArchmageR]

Tested every piece of ram 1 by 1, no errors found. Today I had a different sort of crash, The screen turned completely black, but skype still worked in the background. Nothing helped, and I had to restart the computer. Normal restarting didn`t work, and I had to turn the computer completely off before it wanted to start, and then it started rather slowly.

Tried everything I can think off, got any more suggestions for me?

- thanks

 

[ArchmageR]

Please help, doesen`t anyone have further answers?