BSOD After Wake up from Sleep Mode

I

iboumiza

New Member
Hi,

Here is my desktop config :
- Windows Vista x64 Service Pack 2
- NVIDIA GeForce 9500 GS
- Intel Quad Core 2 Q8200 2.33Ghz

I started recently receiving BSOD, so I reformated the PC and installed a fresh and clean Vista x64 SP 2, but nothing has stopped the BSOD from appearng everytime when I wake up to PC from sleep mode.

Attached you will find all the minidump files.

Thank you for your help, greatly appreciated
iboumiza
 

Attachments

My Computer

System One

The problem will then be your Drivers or your Hardware do you Have the Latest Drivers for your Hardware?

Many Thanks,
Josh
 

My Computer

System One

  • Manufacturer/Model
    Custom Built
    CPU
    Intel Core i5 2400 @ 3.10GHz
    Motherboard
    Foxconn H67MP-S/-V/H67MP
    Memory
    8.0GB DDR3 @ 665MHz (2GBx4)
    Graphics card(s)
    AMD HD Radeon 6870
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    SMB1930NW (1440x900@60Hz)
    Screen Resolution
    1280x800
    Hard Drives
    977GB Seagate ST31000524AS ATA Device (SATA) + 250GB WD iSCSI attached Drive
    Case
    Novatech Night
    Mouse
    Dell HID-compliant mouse
    Keyboard
    Standard PS/2 Keyboard
Did your computer come with driver software on a CD? I would install that first and update after. I had the problem of windows downloading the wrong driver automatically when I booted, so I had to go through and disable that and manually update through the website. Also, device manager may show if some drivers are not updated as they may be marked. I would check there as well. It may not just be your display driver, check the others as well as you mentioned this being a clean install, and everything will need updating.
 

My Computer

System One

  • Manufacturer/Model
    Self built home computer
    Graphics card(s)
    Nvidia
    Sound Card
    On board sound
    Cooling
    Fan
    Internet Speed
    5.14Mbps Download Speed, .65Mbps Upload Speed & 5ms Ping
First of all I have only started analysing BSOD's a couple of days ago and My theory could be wrong but winamp.exe or Winamp Media Player is a Possible problem by accessing memory that is Forbidden could you uninstall Winamp Media Player for me and Test your memory see Memtest86+ - Advanced Memory Diagnostic Tool for More information


DUMP CHECK

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

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


Could not read faulting driver name

READ_ADDRESS:  fffff900c06a3000 

FAULTING_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa6009016170 -- (.trap 0xfffffa6009016170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000dffc3 rsp=fffffa6009016300 rbp=fffff900c22a4490
 r8=fffff900c06a3000  r9=fffff900c22a449c r10=00000000ffffa66a
r11=fffff900c24ba208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!RGNOBJ::bMerge+0x117:
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8] ds:6310:fffff900`c06a3000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001d0f8b0 to fffff80001cae4d0

STACK_TEXT:  


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!RGNOBJ::bMerge+117

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1f7191

FAILURE_BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

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


Full Dump Information:


Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Josh\Desktop\Mini081410-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
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`01c54000 PsLoadedModuleList = 0xfffff800`01e18dd0
Debug session time: Sat Aug 14 14:10:53.787 2010 (UTC + 1:00)
System Uptime: 0 days 0:03:56.857
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c06a3000, 0, fffff960000dffc3, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!RGNOBJ::bMerge+117 )

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

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

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


Could not read faulting driver name

READ_ADDRESS:  fffff900c06a3000 

FAULTING_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa6009016170 -- (.trap 0xfffffa6009016170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000dffc3 rsp=fffffa6009016300 rbp=fffff900c22a4490
 r8=fffff900c06a3000  r9=fffff900c22a449c r10=00000000ffffa66a
r11=fffff900c24ba208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!RGNOBJ::bMerge+0x117:
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8] ds:6310:fffff900`c06a3000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001d0f8b0 to fffff80001cae4d0

STACK_TEXT:  
fffffa60`09016088 fffff800`01d0f8b0 : 00000000`00000050 fffff900`c06a3000 00000000`00000000 fffffa60`09016170 : nt!KeBugCheckEx
fffffa60`09016090 fffff800`01cad059 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff900`c4200078 : nt! ?? ::FNODOBFM::`string'+0x2d3dc
fffffa60`09016170 fffff960`000dffc3 : fffff900`c24ba358 fffffa60`090163d0 00000000`00000000 00000000`08041249 : nt!KiPageFault+0x119
fffffa60`09016300 fffff960`000da0b0 : 00000000`00000001 00000000`00000001 00000000`000000a0 fffff960`00168808 : win32k!RGNOBJ::bMerge+0x117
fffffa60`09016350 fffff960`000d8707 : 00000000`00000000 00000000`08041249 00000000`08041249 fffff960`0012224c : win32k!RGNOBJ::iCombine+0x1cc
fffffa60`090163b0 fffff800`01cadf73 : 00000000`08041249 fffffa60`09016530 fffff960`0028184c 00000000`00000001 : win32k!GreCombineRgn+0x363
fffffa60`090164b0 00000000`75303d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`003ae158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75303d09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!RGNOBJ::bMerge+117

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1f7191

FAILURE_BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

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

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

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


Could not read faulting driver name

READ_ADDRESS:  fffff900c06a3000 

FAULTING_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa6009016170 -- (.trap 0xfffffa6009016170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000dffc3 rsp=fffffa6009016300 rbp=fffff900c22a4490
 r8=fffff900c06a3000  r9=fffff900c22a449c r10=00000000ffffa66a
r11=fffff900c24ba208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!RGNOBJ::bMerge+0x117:
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8] ds:6310:fffff900`c06a3000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001d0f8b0 to fffff80001cae4d0

STACK_TEXT:  
fffffa60`09016088 fffff800`01d0f8b0 : 00000000`00000050 fffff900`c06a3000 00000000`00000000 fffffa60`09016170 : nt!KeBugCheckEx
fffffa60`09016090 fffff800`01cad059 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff900`c4200078 : nt! ?? ::FNODOBFM::`string'+0x2d3dc
fffffa60`09016170 fffff960`000dffc3 : fffff900`c24ba358 fffffa60`090163d0 00000000`00000000 00000000`08041249 : nt!KiPageFault+0x119
fffffa60`09016300 fffff960`000da0b0 : 00000000`00000001 00000000`00000001 00000000`000000a0 fffff960`00168808 : win32k!RGNOBJ::bMerge+0x117
fffffa60`09016350 fffff960`000d8707 : 00000000`00000000 00000000`08041249 00000000`08041249 fffff960`0012224c : win32k!RGNOBJ::iCombine+0x1cc
fffffa60`090163b0 fffff800`01cadf73 : 00000000`08041249 fffffa60`09016530 fffff960`0028184c 00000000`00000001 : win32k!GreCombineRgn+0x363
fffffa60`090164b0 00000000`75303d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`003ae158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75303d09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!RGNOBJ::bMerge+117
fffff960`000dffc3 418b08          mov     ecx,dword ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!RGNOBJ::bMerge+117

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1f7191

FAILURE_BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

BUCKET_ID:  X64_0x50_win32k!RGNOBJ::bMerge+117

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



Make a Restore point before Doing anything

Hope This Helps,
Josh
 

My Computer

System One

  • Manufacturer/Model
    Custom Built
    CPU
    Intel Core i5 2400 @ 3.10GHz
    Motherboard
    Foxconn H67MP-S/-V/H67MP
    Memory
    8.0GB DDR3 @ 665MHz (2GBx4)
    Graphics card(s)
    AMD HD Radeon 6870
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    SMB1930NW (1440x900@60Hz)
    Screen Resolution
    1280x800
    Hard Drives
    977GB Seagate ST31000524AS ATA Device (SATA) + 250GB WD iSCSI attached Drive
    Case
    Novatech Night
    Mouse
    Dell HID-compliant mouse
    Keyboard
    Standard PS/2 Keyboard
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
This is just the last File that you posted.


Josh has given you good advice. With memtes86, run for 6 passes and then take a known good stick and test the MB slots. I would wait a while before uninsalling Media Player.

If after completing the above step, you continue to get BSOD, uninstall your antivirus and install MSE, Micrsoft Security Essentials, at least for test purposes.

Check your hard drive, at the HD Manufacturer website.

Uninstall your virtualization programs: Daemnon or Alcohol 120%. KNown cause of BSODs. This driver SPTD is the cause and must be removed with the uninstall tool.
http://www.duplexsecure.com/en/downloads

Remove SPTD Do this now now.
sptd sptd.sys Sun Oct 11 16:55:14 2009
 
Last edited:

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Mouse
    Dell USB 4 button optical
    Keyboard
    Dell USB
    Other Info
    DSL provided by ATT
You must log in or register to reply here.
Back
Top