Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer boot-up BSOD


  • Please log in to reply
4 replies to this topic

#1 klgoist

klgoist

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 10 November 2010 - 11:38 PM

I'm attempting to fix a BSOD on 1 of three identical PC's

Gateway GT5676
AMD Phenom 9600 Quad-Core Processor 2.3 GHz
4 gb memory
Vista Home Premium SP2 64 bit

BSOD occurs when computer is booting up (it is intermittent) seem to only occur when the computer is cold and happens daily (sometimes once every two days). I am including the debugged memory.dmp text. If anyone can help I would be so thankful.

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jeremy\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02212000 PsLoadedModuleList = 0xfffff800`023d6dd0
Debug session time: Tue Nov 9 14:50:58.702 2010 (GMT-8)
System Uptime: 0 days 0:00:36.855
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffda018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff4c00f81e000, 0, fffff80002288882, 7}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
Page 9d419 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffda018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffda018). Type ".hh dbgerr001" for details
Probably caused by : spsys.sys ( spsys!SPVersion+3012f )

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

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

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

Page 9d419 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffda018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffda018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffff4c00f81e000

FAULTING_IP:
nt!MmProbeAndLockPages+112
fffff800`02288882 410fb601 movzx eax,byte ptr [r9]

MM_INTERNAL_CODE: 7

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: SLsvc.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffffa600225feb0 -- (.trap 0xfffffa600225feb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002288882 rsp=fffffa6002260040 rbp=00000000003ba000
r8=fffffa8006435790 r9=fffff4c00f81e000 r10=0000000000000011
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe nc
nt!MmProbeAndLockPages+0x112:
fffff800`02288882 410fb601 movzx eax,byte ptr [r9] ds:a3e1:e000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800022cca6e to fffff8000226c4d0

STACK_TEXT:
fffffa60`0225fdc8 fffff800`022cca6e : 00000000`00000050 fffff4c0`0f81e000 00000000`00000000 fffffa60`0225feb0 : nt!KeBugCheckEx
fffffa60`0225fdd0 fffff800`0226b059 : 00000000`00000000 fffffa60`00000004 fffffa60`02260a00 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x2c3f1
fffffa60`0225feb0 fffff800`02288882 : fffffa60`07c57656 fffffa80`06435760 fffff880`093ddbf7 00000000`00000120 : nt!KiPageFault+0x119
fffffa60`02260040 fffffa60`07c7a39f : fffffa80`06435760 00000000`00000000 fffff4c0`00000002 fffff4c0`0f81e000 : nt!MmProbeAndLockPages+0x112
fffffa60`02260140 fffffa60`07c7deb8 : fffffa60`07c4a30c 00000000`003ba000 00000000`00000000 fffffa80`06435760 : spsys!SPVersion+0x3012f
fffffa60`02260170 fffffa60`07c802e1 : 00350038`00360037 00000000`00000000 fffffa60`022603d0 00000000`00000bf8 : spsys!SPVersion+0x33c48
fffffa60`02260300 fffffa60`07c8e9ac : 00000000`00000000 00000000`00000014 00000000`00000080 fffffa60`07c9082c : spsys!SPVersion+0x36071
fffffa60`022603e0 fffffa60`07c8cf46 : 00000000`00000000 fffff880`0aad2d20 fffff880`00000010 fffff880`00000bf8 : spsys!SPVersion+0x4473c
fffffa60`02260480 fffffa60`07c8663c : fffff880`0aabdaa8 fffff880`00000d08 fffff880`00000d10 00000000`00000d10 : spsys!SPVersion+0x42cd6
fffffa60`022605b0 fffffa60`07c84c87 : 00000000`00000000 00000000`00000000 00000000`00000006 00b2d05e`00000000 : spsys!SPVersion+0x3c3cc
fffffa60`02260720 fffffa60`07c8af26 : 000000b2`d05e0000 00000000`00000000 00000000`000000f0 00000000`00000000 : spsys!SPVersion+0x3aa17
fffffa60`022607a0 fffffa60`07c84be4 : 00000000`ffd85928 fffffa60`02260ca0 00000000`ffd85928 fffffa80`06dce801 : spsys!SPVersion+0x40cb6
fffffa60`02260920 fffffa60`07c6d96a : 00000000`00000000 fffffa60`011ce53b 00000000`00000001 fffffa60`02260ca0 : spsys!SPVersion+0x3a974
fffffa60`02260960 fffffa60`07c80efd : 00000000`ffd85928 fffffa80`06dce950 00000001`06060000 fffffa60`022609a8 : spsys!SPVersion+0x236fa
fffffa60`02260990 fffffa60`011ce368 : 00000000`00000000 fffffa80`06dd4710 00000000`8000a00c fffffa80`0485da70 : spsys!SPVersion+0x36c8d
fffffa60`022609d0 fffff800`024cf70e : fffffa80`06dce900 fffffa80`06dce880 fffffa80`06dd4710 fffffa80`06dce880 : spldr+0x5368
fffffa60`02260a10 fffff800`024d8126 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
fffffa60`02260b40 fffff800`0226bf73 : fffff880`08fe56d0 00000000`00000001 fffffa80`06d2d500 fffffa60`02260ca0 : nt!NtDeviceIoControlFile+0x56
fffffa60`02260bb0 00000000`778d6d8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01def598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778d6d8a


STACK_COMMAND: kb

FOLLOWUP_IP:
spsys!SPVersion+3012f
fffffa60`07c7a39f b801000000 mov eax,1

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: spsys!SPVersion+3012f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: spsys

IMAGE_NAME: spsys.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49b6a07b

FAILURE_BUCKET_ID: X64_0x50_spsys!SPVersion+3012f

BUCKET_ID: X64_0x50_spsys!SPVersion+3012f

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,252 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:24 AM

Posted 11 November 2010 - 12:36 PM

On each PC...

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#3 klgoist

klgoist
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 12 November 2010 - 01:31 PM

Sorry for the slow response, I will not be back infront of the computer with the problem until 6:30 pm(pacific) time. I will download utility and post log then.
Thanks,
Ken

#4 klgoist

klgoist
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 12 November 2010 - 09:28 PM

Hamluis,
Heres the Info you requested....

==================================================
Dump File : Mini111210-01.dmp
Crash Time : 11/12/2010 2:41:55 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f814000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022c5882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini111210-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110910-01.dmp
Crash Time : 11/9/2010 2:52:36 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f81e000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02288882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110910-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110810-01.dmp
Crash Time : 11/8/2010 6:42:01 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f804000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0228e882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110810-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110510-01.dmp
Crash Time : 11/5/2010 5:52:49 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f800000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022c1882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110510-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110410-01.dmp
Crash Time : 11/4/2010 1:40:53 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f810000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022d7882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110410-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110310-01.dmp
Crash Time : 11/3/2010 2:00:27 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0ca82000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022d5882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110310-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110210-02.dmp
Crash Time : 11/2/2010 9:03:43 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f806000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022cb882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110210-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110210-01.dmp
Crash Time : 11/2/2010 2:04:11 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f80a000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022bf882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110210-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini110110-01.dmp
Crash Time : 11/1/2010 2:48:55 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f814000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0227f882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini110110-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini102910-01.dmp
Crash Time : 10/29/2010 1:43:22 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f808000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`022c3882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini102910-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini102610-01.dmp
Crash Time : 10/26/2010 1:50:43 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f800000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0228a882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini102610-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini102510-02.dmp
Crash Time : 10/25/2010 5:21:33 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f81a000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02292882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini102510-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini102510-01.dmp
Crash Time : 10/25/2010 6:01:04 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff4c0`0f800000
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0228a882
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini102510-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

#5 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:24 AM

Posted 13 November 2010 - 04:40 PM

Please do the following:


How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    Posted Image
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    Posted Image

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    Posted Image
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :)

Compliments of Billy O'Neal.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users