Bsod,games crash

[cybercore]

Simply remove 1 stick and run memtest with the other 1 stick in.
Take a screenshot of your CPU-Z tabs, all of them, and attach them here.

 

[lumpikarna]

Simply remove 1 stick and run memtest with the other 1 stick in.
Take a screenshot of your CPU-Z tabs, all of them, and attach them here.

ok posting cpu-z
Memtest try at night when i go sleep first i try 2 rams and see if my pc crash or not.
ok here pict.
Its strange becasue my Games like garrys mod crash or i get bsod crash is everything with error like (memory could be read )

Edit:sorry i forget here it is

 

[cybercore]

Lol, you didn't post all - give me 1 more the SPD tab.

 

[lumpikarna]

ok i post it at previous post

just got bsod when playing gmod

 

[cybercore]

The timings and the voltage look right. Yet, it does look like a memory problem:

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\Mini121510-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Dec 15 10:42:28.609 2010 (UTC - 5:00)
System Uptime: 0 days 0:45:17.343
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {affc995c, 0, 805c0223, 3}


Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!ObCheckObjectAccess+cb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: affc995c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c0223, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000003, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  affc995c 

FAULTING_IP: 
nt!ObCheckObjectAccess+cb
805c0223 ff75f0          push    dword ptr [ebp-10h]

MM_INTERNAL_CODE:  3

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mumble.exe

LAST_CONTROL_TRANSFER:  from 8062ebde to 805c0223

STACK_TEXT:  
afbc996c 8062ebde e4965230 8968ae10 00000001 nt!ObCheckObjectAccess+0xcb
afbc99b8 8062f468 e21f0b60 00c3ac80 00000000 nt!CmpDoOpen+0x256
afbc9bb0 805bf021 00c3ac80 00000000 8968ae10 nt!CmpParseKey+0x558
afbc9c28 805bb9d0 00000048 afbc9c68 00000040 nt!ObpLookupObjectName+0x119
afbc9c7c 80624d07 00000000 8a4ec508 89bb7601 nt!ObOpenObjectByName+0xea
afbc9d50 8054161c 02faec20 00020019 02faea1c nt!NtOpenKey+0x1af
afbc9d50 7c90e4f4 02faec20 00020019 02faea1c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02faea5c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObCheckObjectAccess+cb
805c0223 ff75f0          push    dword ptr [ebp-10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObCheckObjectAccess+cb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

FAILURE_BUCKET_ID:  0x50_nt!ObCheckObjectAccess+cb

BUCKET_ID:  0x50_nt!ObCheckObjectAccess+cb

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

 

[lumpikarna]

The timings and the voltage look right. Yet, it does look like a memory problem:

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\Mini121510-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Dec 15 10:42:28.609 2010 (UTC - 5:00)
System Uptime: 0 days 0:45:17.343
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {affc995c, 0, 805c0223, 3}


Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!ObCheckObjectAccess+cb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: affc995c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c0223, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000003, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  affc995c 

FAULTING_IP: 
nt!ObCheckObjectAccess+cb
805c0223 ff75f0          push    dword ptr [ebp-10h]

MM_INTERNAL_CODE:  3

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mumble.exe

LAST_CONTROL_TRANSFER:  from 8062ebde to 805c0223

STACK_TEXT:  
afbc996c 8062ebde e4965230 8968ae10 00000001 nt!ObCheckObjectAccess+0xcb
afbc99b8 8062f468 e21f0b60 00c3ac80 00000000 nt!CmpDoOpen+0x256
afbc9bb0 805bf021 00c3ac80 00000000 8968ae10 nt!CmpParseKey+0x558
afbc9c28 805bb9d0 00000048 afbc9c68 00000040 nt!ObpLookupObjectName+0x119
afbc9c7c 80624d07 00000000 8a4ec508 89bb7601 nt!ObOpenObjectByName+0xea
afbc9d50 8054161c 02faec20 00020019 02faea1c nt!NtOpenKey+0x1af
afbc9d50 7c90e4f4 02faec20 00020019 02faea1c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02faea5c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObCheckObjectAccess+cb
805c0223 ff75f0          push    dword ptr [ebp-10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObCheckObjectAccess+cb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

FAILURE_BUCKET_ID:  0x50_nt!ObCheckObjectAccess+cb

BUCKET_ID:  0x50_nt!ObCheckObjectAccess+cb

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

So now i must try memtest ok ? if he dont have error what next and if he have error ? Buy news RAMS?

 

[lumpikarna]

NOw i try just prime 95 to test cpu and guees what my pc get bsod after 2-3 minutes i try it again and bsod after 2-3 minutes with error 0.50 so its must be ram or can be cpu ?

 

[cybercore]

I'd recommend again you test the sticks separately 1 in slot at a time. If no errors show up then it is probably your power supply.

If this set of RAM works no issues on another PC, it's good then. Only you can tell 100% for sure.

 

[cybercore]

NOw i try just prime 95 to test cpu and guees what my pc get bsod after 2-3 minutes i try it again and bsod after 2-3 minutes with error 0.50 so its must be ram or can be cpu ?

It still can be your Power Supply or RAM. Does it crash during FFT or Blend?

 

[lumpikarna]

NOw i try just prime 95 to test cpu and guees what my pc get bsod after 2-3 minutes i try it again and bsod after 2-3 minutes with error 0.50 so its must be ram or can be cpu ?

It still can be your Power Supply or RAM. Does it crash during FFT or Blend?

FFT

 

[cybercore]

FFT is CPU heavy emphasis. If the clocks are right, and the memory is good, like it was recently bought and not defective, and you are sure it's indeed this way, then blame the power supply - especially if it crashes on peak load <- memtest, prime95, during gaming. Actually many possible hardware causes are possible. The best way to find out is to try each of these parts on another pc. I would start with the power supply unit.

 

[lumpikarna]

FFT is CPU heavy emphasis. If the clocks are right, and the memory is good, like it was recently bought and not defective, and you are sure it's indeed this way, then blame the power supply - especially if it crashes on peak load <- memtest, prime95, during gaming. Actually many possible hardware causes are possible. The best way to find out is to try each of these parts on another pc. I would start with the power supply unit.

ye looks like its power suppli last night i try run memtest with news RAms and after 2 minutes pc just shutdown and today i got 2 bsod i post here so looks like i try new power suppli somebody pls check this bsod

 

[lumpikarna]

So ye its looks like its power supply but now i dont have money to buy better power suppli so can somebody know how underclock cpu and graphic card ? i need underclock becasue my power suppli looks like shut down pc and now i dont play newest game so i dont need perfomance. can somebody help ?

 

[CarlTR6]

Underclocking will not help a faulty power supply and will likely create more problems.