Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Blue screen problem More Help Needed (SOLVED)
New Posts  All Forums:Forum Nav:

Blue screen problem More Help Needed (SOLVED)

post #1 of 138
Thread Starter 
Hi all i need some advice on the blue screen error.
think it may be memory related but not completely sure.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C000001D
BCP2: FFFFF80003441D2F
BCP3: FFFFF88007410F20
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020912-21637-01.dmp
C:\Users\Bajanboy\AppData\Local\Temp\WER-35942-0.sysdata.xml
Edited by bajanboy - 3/9/12 at 2:23am
post #2 of 138
I believe 3B normally means you should up your Vcore.
Beestje 2.0
(20 items)
 
Beestje 1.5
(16 items)
 
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3820 Sabertooth X79 ASUS GeForce GTX 680 ASUS GeForce GTX 680 
RAMHard DriveHard DriveHard Drive
Samsung low profile x4 OCZ Vertex 3 Crucial M4 Samsung HD103SJ 
Optical DriveCoolingCoolingOS
Lite-On BD drive Megahalems rev. B Cooler Master Excalibur Windows 7 home premium x64 
MonitorKeyboardPowerCase
ASUS VG278H Logitech G710+ Corsair TX750 Silverstone Raven 2 Evolution 
MouseMouse PadAudioAudio
Corsair M60 Razer Kabuto Echo Audiofire 2 Sennheiser HD515 
CPUMotherboardGraphicsRAM
i7 920 Asus P6T Club3d HD7870 royalKing Corsair Dominator 3x4GB 
Hard DriveHard DriveOptical DriveCooling
Crucial V4 128GB Seagate Barracuda LP 2TB LG GH22LS Scythe Mugen 2b 
CoolingCoolingMonitorKeyboard
CM Excalibur x2 CM R4 x3 Samsung BX2450 Microsoft Sidewinder X6 
PowerCaseMouseMouse Pad
Seasonic M12 II 520 Antec 600 Microsoft Intellimouse Razer Kabuto 
  hide details  
Reply
Beestje 2.0
(20 items)
 
Beestje 1.5
(16 items)
 
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3820 Sabertooth X79 ASUS GeForce GTX 680 ASUS GeForce GTX 680 
RAMHard DriveHard DriveHard Drive
Samsung low profile x4 OCZ Vertex 3 Crucial M4 Samsung HD103SJ 
Optical DriveCoolingCoolingOS
Lite-On BD drive Megahalems rev. B Cooler Master Excalibur Windows 7 home premium x64 
MonitorKeyboardPowerCase
ASUS VG278H Logitech G710+ Corsair TX750 Silverstone Raven 2 Evolution 
MouseMouse PadAudioAudio
Corsair M60 Razer Kabuto Echo Audiofire 2 Sennheiser HD515 
CPUMotherboardGraphicsRAM
i7 920 Asus P6T Club3d HD7870 royalKing Corsair Dominator 3x4GB 
Hard DriveHard DriveOptical DriveCooling
Crucial V4 128GB Seagate Barracuda LP 2TB LG GH22LS Scythe Mugen 2b 
CoolingCoolingMonitorKeyboard
CM Excalibur x2 CM R4 x3 Samsung BX2450 Microsoft Sidewinder X6 
PowerCaseMouseMouse Pad
Seasonic M12 II 520 Antec 600 Microsoft Intellimouse Razer Kabuto 
  hide details  
Reply
post #3 of 138
just found this for ya mate. Hope it helps you out

The Stop 0x3B (SYSTEM_SERVICE_EXCEPTION) indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
According to the documentation provided by Microsoft, this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code; the first parameter value (00000000C0000005) seems to indicate that an access violation occurred.

Based on the above, I would completely remove your graphics drivers and try again, or try different ones. thumb.gif
post #4 of 138
Thread Starter 
ok thabks for the quick reply
that was the latest of the nvidia web site but i will uninstall and reinstall
thought it was one my memory sticks because it only started happening after the new one was installed
thanks again
post #5 of 138
Thread Starter 
ok I remove and reinstall the drivers and got 2 more blue screens sense then
using latest driver 285.62

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF87FC6D14F44
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80003093C90
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\021512-21668-01.dmp
C:\Users\Bajanboy\AppData\Local\Temp\WER-38345-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt




Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: 00000000611B6DE4
BCP2: 0000000000000000
BCP3: 000000006097E176
BCP4: 0000000000000008
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\021512-27783-01.dmp
C:\Users\Bajanboy\AppData\Local\Temp\WER-49171-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
post #6 of 138

Odp: Blue screen problem Help!!!

Have you tried reseting the CMOS? If that fails and if I were you I'd just back up all data and reinstall the entire system
post #7 of 138
Thread Starter 
redid the system already but will try the cmos option
post #8 of 138
Hello bajanboy, can you please navigate to C:/Windows/Minidump. Once you're there, zip up your latest dump files and attach them to your next post here. I'll take a look at them for you and do my best to solve your pesky BSOD issue smile.gif
post #9 of 138
Thread Starter 
post #10 of 138
Before we begin, I ask you do the following:

1. If any of your hardware is overclocked, PLEASE reset it to stock settings / optimized defaults whilst trying to diagnose BSOD related issues. You're absolutely more than welcome to re-overclock your hardware after we've gone through your issues.

2. If you have RAID, please update its driver. If you're unsure of how to do this or where to download the drivers, please don't hesitate to ask and I will do my best to point you in the right direction.

I have taken a look at your dump, and here's what I've found:

First off, the first bugcheck code is SYSTEM_SERVICE_EXCEPTION (3b). Nine times out of ten this is at the fault of video card drivers, so that's what we're going to do first.

Uninstall your video card drivers and then update your video card drivers to the latest version:

STAY AWAY FROM BETA DRIVERS WHILE DIAGNOSING BSOD RELATED ISSUES!

Intel
AMD
nVidia


Drivers in need of update (do note that although drivers listed may not be the cause of your related issues, it is always best to have up to date drivers):
Quote:
secdrv.SYS - secdrv fffff880`06e9f000 fffff880`06eaa000 Wed Sep 13 09:18:38 2006 (4508052e) 00010b40

(Can be updated via Windows Upate)
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff80003493cfe, Address of the instruction which caused the bugcheck
Arg3: fffff880090c2c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nt!EtwpPsProvTraceImage+2e
fffff800`03493cfe 450fb7d1        movzx   r10d,r9w

CONTEXT:  fffff880090c2c60 -- (.cxr 0xfffff880090c2c60)
rax=fffff880090c3718 rbx=0000000000000000 rcx=fffffa8007638658
rdx=000000000000128c rsi=000000000000128c rdi=fffffa8007638658
rip=fffff80003493cfe rsp=fffff880090c3640 rbp=fffff80003287d00
 r8=fffff880090c3958  r9=0000000000001401 r10=fffffa8003d96d40
r11=fffffa8003ef0f78 r12=fffffa8007638658 r13=fffff880090c3958
r14=000000000000128c r15=fffffa8007638658
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!EtwpPsProvTraceImage+0x2e:
fffff800`03493cfe 450fb7d1        movzx   r10d,r9w
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  kldw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003493cfe

STACK_TEXT:  
fffff880`090c3640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwpPsProvTraceImage+0x2e


FOLLOWUP_IP: 
nt!EtwpPsProvTraceImage+2e
fffff800`03493cfe 450fb7d1        movzx   r10d,r9w

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!EtwpPsProvTraceImage+2e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff880090c2c60 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!EtwpPsProvTraceImage+2e

BUCKET_ID:  X64_0x3B_nt!EtwpPsProvTraceImage+2e

Followup: MachineOwner

The second bugcheck code was ATTEMPTED_WRITE_TO_READONLY_MEMORY, which again, nine times out of ten is related to a device driver (update your drivers), a service or incompatible firmware. However, it could be RAM as well.

As I've said earlier, let's try uninstalling the video card drivers and then reinstalling the latest version.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff900c0081000, Virtual address for the attempted write.
Arg2: 0e6000009932f021, PTE contents.
Arg3: fffff880099f2490, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880099f2490 -- (.trap 0xfffff880099f2490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00ffffff00000000 rbx=0000000000000000 rcx=fffff900c0081000
rdx=00000000021538e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000154b34 rsp=fffff880099f2628 rbp=fffff880099f2920
 r8=0000000000000008  r9=0000000000000001 r10=fffffa80060af8b0
r11=fffff900c0081000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k+0xc4b34:
fffff960`00154b34 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000302b5d2 to fffff8000307fc40

STACK_TEXT:  
fffff880`099f2328 fffff800`0302b5d2 : 00000000`000000be fffff900`c0081000 0e600000`9932f021 fffff880`099f2490 : nt!KeBugCheckEx
fffff880`099f2330 fffff800`0307dd6e : 00000000`00000001 fffff900`c0081000 00000000`00000100 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x45c6e
fffff880`099f2490 fffff960`00154b34 : fffff960`0011b155 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`099f2628 fffff960`0011b155 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k+0xc4b34
fffff880`099f2630 fffff880`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k+0x8b155
fffff880`099f2638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+c4b34
fffff960`00154b34 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k+c4b34

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10ff25

FAILURE_BUCKET_ID:  X64_0xBE_win32k+c4b34

BUCKET_ID:  X64_0xBE_win32k+c4b34

Followup: MachineOwner

Edited by pjBSOD - 2/16/12 at 3:10pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Blue screen problem More Help Needed (SOLVED)