BSOD

[Pixelpro]

BSOD, this computer is about 12hours old? i've already had 2... (customn built)
it seems Windows 7 is crashing it....

On Sun 10/10/2010 08:22:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A49EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\101010-21996-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 09/10/2010 19:22:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002897EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\100910-19749-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

- x64 ? - the original installed OS on the system? yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system No
- Full Retail = you purchased it from retailer Yes - What is the age of system (hardware)? 1day old (less than)
- What is the age of OS installation (have you re-installed the OS?)No re-install, 1day old.

any help?

 

[lorddenis]

folow this posting instructions:

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[zigzag3143]

BSOD, this computer is about 12hours old? i've already had 2... (customn built)
it seems Windows 7 is crashing it....

On Sun 10/10/2010 08:22:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A49EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\101010-21996-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 09/10/2010 19:22:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002897EC0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\100910-19749-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

- x64 ? - the original installed OS on the system? yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system No
- Full Retail = you purchased it from retailer Yes - What is the age of system (hardware)? 1day old (less than)
- What is the age of OS installation (have you re-installed the OS?)No re-install, 1day old.

any help?

We really need the DMP files but your bug check indicates this
Cause

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.




If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[Pixelpro]

Done,
Error
Symptom:
Device drivers are not installed. Cause: A driver has not been installed for this device preventing it from working properly. Details: The device driver for PCI Simple Communications Controller has not been installed. This device will not be available until the correct device driver is installed. Resolution: 1. Try installing the drivers using Windows Update.
2. Install the drivers that are on the installation media that came with the device.
3. Check with the manufacturer for an updated driver. Related: Explanation of Error Codes Generated by Device Manager Informational
Symptom:
The Security Center has not recorded an anti-virus product. Cause: The Security Center is unable to identify an active anti-virus application. Either there is no anti-virus product installed or it is not recognized. Resolution: 1. Verify that an anti-virus product is installed.
2. If an anti-virus product is installed and functioning configure Security Center to stop monitoring anti-virus status. Related: Anti-virus Basic System Checks

Tests Result Description

OS Checks

Passed Checks for attributes of the operating system Test Groups Tests Failed Description OS Version Check 1 0 Passed

Disk Checks

Passed Checks for disk status Test Groups Tests Failed Description SMART Predict Failure Check 1 0 Passed Logical Disk Dirty Bit Check 1 0 Passed

Security Center Tests

Passed Checks for state of Security Center related information. Test Groups Tests Failed Description User Account Control Enabled Check 1 0 Passed Windows Update Enabled Check 1 0 Passed

System Service Checks

Passed Checks for state of system services Test Groups Tests Failed Description Abnormally Terminated Services Check 1 0 Passed Workstation Service Check 1 0 Passed

Hardware Device and Driver Checks

Failed Survey of Windows Management Infrastructure supported devices.

 

[Pixelpro]

Going to try a re-start i have alot (33) major updates, that might fix it.

 

[zigzag3143]

Going to try a re-start i have alot (33) major updates, that might fix it.

Um, Suspect you are using who crashed us, or similar. Windb says Memory corruption.


Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Again... Would suggest running a memory test.


Ken J


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT_jcgriff2\100610-10342-02.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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9be50
Debug session time: Wed Oct  6 21:36:11.500 2010 (GMT-4)
System Uptime: 0 days 0:00:41.811
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88008136420, 1, fffff80002d8fac3, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

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

1: 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: fffff88008136420, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d8fac3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d060e0
 fffff88008136420 

FAULTING_IP: 
nt!RtlpWow64CtxFromAmd64+c3
fffff800`02d8fac3 418980b0100000  mov     dword ptr [r8+10B0h],eax

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  SlingAgentServ

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008134c50 -- (.trap 0xfffff88008134c50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000010002
rdx=000000000000002b rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d8fac3 rsp=fffff88008134de0 rbp=fffff88008134e70
 r8=fffff88008135370  r9=0000000000000000 r10=0000000000000000
r11=fffff88008134e10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpWow64CtxFromAmd64+0xc3:
fffff800`02d8fac3 418980b0100000  mov     dword ptr [r8+10B0h],eax ds:5b60:fffff880`08136420=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b4ef14 to fffff80002ace740

STACK_TEXT:  
fffff880`08134ae8 fffff800`02b4ef14 : 00000000`00000050 fffff880`08136420 00000000`00000001 fffff880`08134c50 : nt!KeBugCheckEx
fffff880`08134af0 fffff800`02acc82e : 00000000`00000001 fffff880`08135370 00000000`00100000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`08134c50 fffff800`02d8fac3 : 00000000`00000000 00000000`00000000 fffff880`08135b88 fffff880`08135b80 : nt!KiPageFault+0x16e
fffff880`08134de0 fffff800`02d8fc9d : fffff880`08135370 fffff880`08134e70 fffff880`081356b4 00000000`0255f201 : nt!RtlpWow64CtxFromAmd64+0xc3
fffff880`08134e10 fffff800`02d8fff7 : fffff880`08134e70 fffff880`08135660 00000000`0001002f 00000000`0255f240 : nt!RtlpWow64GetContextOnAmd64+0x4d
fffff880`08134e40 fffff800`02d96fce : 00000000`00000000 00000000`00000000 00000000`000002cc 00000000`00000000 : nt!PspWow64GetContextThreadOnAmd64+0x1d7
fffff880`081359e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryInformationThread+0xbdd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002d8fac7 - nt!RtlpWow64CtxFromAmd64+c7
    [ 00:10 ]
1 error : !nt (fffff80002d8fac7)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

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

 

[Pixelpro]

So basically your saying one of my sticks of ram is defective?


i have a desktop gadget, it says my ram is on 43% usage 24/7 it doesn't change, i know it works (gadget) as i have it on my laptop