 | |
| |
| 28 Oct 2012 | #1 |
| | BSOD - Random timing / situations 0x50 As the title states, random BSOD. Started a few weeks ago. "On Mon 10/29/2012 3:28:36 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\102812-28563-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x50 (0xFFFFF30012816930, 0x1, 0xFFFFF8000317818D, 0x7) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time." Last edited by RandomGuy09123; 28 Oct 2012 at 11:18 PM.. Reason: Name of zip file |
My System Specs | |
| 29 Oct 2012 | #2 |
| | Welcome Problematic software: Code: Start Menu\Programs\AVG Public:Start Menu\Programs\AVG Public Recommended antivirus program for Windows 7 based on stability compared to others:-
Quote: STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff30012816930, 1, fffff8000317818d, 7}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
7: 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: fffff30012816930, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8000317818d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ca100
GetUlongFromAddress: unable to read from fffff800030ca1c0
fffff30012816930 Nonpaged pool
FAULTING_IP:
nt!IopAllocateMiniCompletionPacket+7d
fffff800`0317818d 4889440420 mov qword ptr [rsp+rax+20h],rax
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: FlashPlayerPlu
CURRENT_IRQL: 0
TRAP_FRAME: fffff880071a7980 -- (.trap 0xfffff880071a7980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800b66ee00 rbx=0000000000000000 rcx=fffffa800bc12881
rdx=fffffa800b66ee01 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000317818d rsp=fffff880071a7b10 rbp=00000000005a6de0
r8=fffffa800b66ee00 r9=0000000000000000 r10=fffff80003017980
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na pe nc
nt!IopAllocateMiniCompletionPacket+0x7d:
fffff800`0317818d 4889440420 mov qword ptr [rsp+rax+20h],rax ss:0018:fffff300`12816930=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e41837 to fffff80002e9afc0
STACK_TEXT:
fffff880`071a7818 fffff800`02e41837 : 00000000`00000050 fffff300`12816930 00000000`00000001 fffff880`071a7980 : nt!KeBugCheckEx
fffff880`071a7820 fffff800`02e990ee : 00000000`00000001 fffff300`12816930 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x43741
fffff880`071a7980 fffff800`0317818d : 00000000`000ce8c0 00000000`000cfd20 00000000`730081f8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`071a7b10 fffff800`03126d07 : 00000000`00000000 fffffa80`06f58060 00000000`005a6de0 00000000`00000000 : nt!IopAllocateMiniCompletionPacket+0x7d
fffff880`071a7b50 fffff800`02e9a253 : fffffa80`06f58060 fffff880`071a7ca0 00000000`000cdf68 00000000`00000000 : nt!NtSetIoCompletion+0x67
fffff880`071a7bb0 00000000`7782297a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000cdf48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7782297a
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80003178190 - nt!IopAllocateMiniCompletionPacket+80
[ 24:04 ]
1 error : !nt (fffff80003178190)
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
--------- Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes. Quote: The goal is to test all the RAM sticks and all the motherboard slots. Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed. If you get errors, stop the test and continue with the next step. 1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes. Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot. If this stick passes the test then go to step #3. 2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot. If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot. If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings. 3. Test the next stick of RAM (stick #2) in the next motherboard slot. If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick. If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot. 4. If you find a stick that passes the test, test it in all the other motherboard slots. If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem. In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks. Code: BIOS Version/Date Dell Inc. A01, 8/11/2009 Quote: STOP 0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY Usual causes: Device driver Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FC, {fffff880031aea80, 800000021c2d1963, fffff880031ae8c0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+4e17da )
Followup: MachineOwner
--------- Code: 7: kd> lmvm nvlddmkm
start end module name
fffff880`0f076000 fffff880`0fd5e000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Thu Aug 30 21:50:16 2012 (503F8BB8)
CheckSum: 00CCA304
ImageSize: 00CE8000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 First uninstall from control panel, Click on the Start  ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to ATI. Delete remnants of its older driver using Driver Sweeper. Then get the latest drivers from the manufacturers website or from a reliable source like Filehippo.comRun Disk Check on your hard disk for file system errors and bad sectors on it: Let us know the results |
| My System Specs |
| 29 Oct 2012 | #3 |
| | Thank you for the prompt response. Starting from the top. |
| My System Specs |
| . |
| |
| 29 Oct 2012 | #4 |
| | Good luck  |
| My System Specs |
| 29 Oct 2012 | #5 |
| | Uninstalled AVG Ran MSE - No problems Ran MalwareBytes - No problems Updated BIOS to A03 - Latest from Dell About to run CHKDSK The memtest will have to wait until I can get to the office tomorrow, forgot my USB stick over the weekend. |
| My System Specs |
| 29 Oct 2012 | #6 |
| | Okay, update the thread when you're able to run memtest. |
| My System Specs |
| 29 Oct 2012 | #7 |
| | Updating: Can't run memtest due to hurricane interference but I ran chkdsk last night and it didn't show any errors or having to fix anything. |
| My System Specs |
| 29 Oct 2012 | #8 |
| | Thanks for the update, I hope everything is OK at your end. Have you encountered any blue screens since making the other changes on your computer? |
| My System Specs |
| 29 Oct 2012 | #9 |
| | My system seems more stable and is booting up much more quickly now. I really wish I had a USB stick, nothing to do today but sit at home and watch movies. |
| My System Specs |
| 29 Oct 2012 | #10 |
| | 
Quote: Originally Posted by RandomGuy09123  My system seems more stable and is booting up much more quickly now. I really wish I had a USB stick, nothing to do today but sit at home and watch movies. |
| My System Specs |
 |
BSOD - Random timing / situations 0x50 problems?
| Thread Tools | |
| Similar help and support threads for: BSOD - Random timing / situations 0x50 | ||||
| Thread | Forum | |||
 BSOD Error Code 0x0000003B Random Timing | BSOD Help and Support | |||
| Random BSOD Error's 0x50 PAGE FAULT IN NON PAGES AREA | BSOD Help and Support | |||
| Random BLSC 0x50 New Computer, New Install; Random Program Crashes. | BSOD Help and Support | |||
| Random BSOD, 0x50, 0xd1 0x7e, 0x3b | BSOD Help and Support | |||
| BSOD, timing seems random to my un-trained eye. Stop Error: 0x000000F4 | BSOD Help and Support | |||
All times are GMT -5. The time now is 05:57 PM.
