BSOD System_Service_Exception

[JerryS]

Hi!

I have had MANY BSOD issues since installing Win7 and have slowly worked through most of the issues. This last one has me stumped. My system specs:

Win7 x64 - clean install new HD
Intel Core 2 Duo E6600
Asus Striker Extreme MB lates bios (1505)
4 GB Crucial DDR2 PC2-6400
NVIDIA GeForce8800 gts - latest driver from NVIDIA site (9107)
Microsoft wireless keyboard and mouse

​

I keep getting BSOD crashes after the system has been runnig for a few hours. BlueScreenView shows the following:

111609-30388-01.dmp 11/16/2009 7:08:10PM SYSTEM_SERVICE_EXCEPTION 0x0000003b
00000000`c0000005 fffff960`00166276 fffff880`09f841a0 00000000`00000000
win32k.sys win32k.sys+126276 x64
C:\Windows\minidump\111609-30388-01.dmp

Detail view hi-lights ntoskrnl.exe and Win32k.sys as the drivers that caused the crash.
​

I have been able to reproduce this error several times simply by using the scroll wheel on my mouse while browing a web page. When this error occurs it takes many reboot attempts and system startup repairs to get back up and running. Usually boots to a black screen with a mouse pointer only.

Additional information. Initial blue screens were related to memory errors. THese were solved by increasing the voltage to the RAM in the bios. No more memory related errors once that was done. Win 7 appars to be much more memory intensive than Vista was. This system was running Vista Ultimate x32 for a long time w/o any problems and all default MB settings.

Thanks for any advice.

-Jerry

 

[zigzag3143]

Hi!

I have had MANY BSOD issues since installing Win7 and have slowly worked through most of the issues. This last one has me stumped. My system specs:

Win7 x64 - clean install new HD
Intel Core 2 Duo E6600
Asus Striker Extreme MB lates bios (1505)
4 GB Crucial DDR2 PC2-6400
NVIDIA GeForce8800 gts - latest driver from NVIDIA site (9107)
Microsoft wireless keyboard and mouse

​

I keep getting BSOD crashes after the system has been runnig for a few hours. BlueScreenView shows the following:

111609-30388-01.dmp 11/16/2009 7:08:10PM SYSTEM_SERVICE_EXCEPTION 0x0000003b
00000000`c0000005 fffff960`00166276 fffff880`09f841a0 00000000`00000000
win32k.sys win32k.sys+126276 x64
C:\Windows\minidump\111609-30388-01.dmp

Detail view hi-lights ntoskrnl.exe and Win32k.sys as the drivers that caused the crash.
​

I have been able to reproduce this error several times simply by using the scroll wheel on my mouse while browing a web page. When this error occurs it takes many reboot attempts and system startup repairs to get back up and running. Usually boots to a black screen with a mouse pointer only.

Additional information. Initial blue screens were related to memory errors. THese were solved by increasing the voltage to the RAM in the bios. No more memory related errors once that was done. Win 7 appars to be much more memory intensive than Vista was. This system was running Vista Ultimate x32 for a long time w/o any problems and all default MB settings.

Thanks for any advice.

-Jerry

Jerry Hi and welcome

We can give you much more info if you can upload the dump file to us. can you go into c:\windows\minidump, zip the dump file (*.dmp) and upload it to us using the attachment icon (shaped like a peper clip) in the reply form

Thanks

Ken J+

 

[JerryS]

I was trying to attach the file...there seems to be something else going on as well...it tells me I need administrator permission to copy the file or to zip it, even though I am an administrator. I had to leave for work, I will try again tonight.

 

[JerryS]

Here are the contents of my dump file directory. Thanks for the assist!

-Jerry

 

[torrentg]

Hey Jerry. It looks like almost positively that the RAM is defective.

Run Memtest overnight to see if it picks up errors. This one seems good for x64 but you can use any other.

What you can also do is go to Corsair's site to check on your specific modules. Then set the motherboard bios to use the correct VDimm (Ram voltage) and timings.

Let us know how it goes.

I also noticed these drivers. Try to Google them and update if you can:

x10ufx2 x10ufx2.sys Thu Nov 30 18:18:51 2006 <<< probably for remote control, this is alright I suppose
adfs adfs.SYS Mon Nov 03 11:48:14 2008
ctac32k ctac32k.sys Wed Jul 02 04:38:22 2008
ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005
nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008
SiRemFil SiRemFil.sys Wed Jun 20 15:42:10 2007
SiWinAcc SiWinAcc.sys Thu Jun 14 20:02:02 2007
SI3132 SI3132.sys Wed Oct 03 14:39:29 2007

 

[zigzag3143]

Here are the contents of my dump file directory. Thanks for the assist!

-Jerry

Hi jerry and welcome

You think you have ahd enough crashes? 18 in 10 days. I took a quick look at 5 of them and they are almost identical. They all refer to memory corruption.

You also have some fairly old drivers, so its obvious that you didnt do a clean install.

I would downlaod and rrun memtestx86. run it for several hours (preferably overnight)

I would also run a system file checker to verify and fix your system files
type cmd in search>right click and run as admin>SFC /SCANNOW
let us know the results

Also if you are overclocking stop, if you have a raid upgrade its driver.

Hope this helps

Ken J+


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


Loading Dump File [C:\Users\K\Desktop\111709-30950-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Tue Nov 17 09:06:02.010 2009 (GMT-5)
System Uptime: 0 days 0:01:41.288
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600025327c, fffff8800a25ede0, 0}

Probably caused by : memory_corruption

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!DEVLOCKOBJ::bTightBoundsToRegion+18c
fffff960`0025327c 00488d add byte ptr [rax-73h],cl

CONTEXT: fffff8800a25ede0 -- (.cxr 0xfffff8800a25ede0)
rax=00000000c65b4fd8 rbx=fffff8800a25f8f8 rcx=fffff900c28a0f50
rdx=fffff900c0930c80 rsi=fffff900c28a0f20 rdi=0000000000000001
rip=fffff9600025327c rsp=fffff8800a25f7c8 rbp=0000000000f00021
r8=fffff960002a5de8 r9=fffff900c28a0f20 r10=0000000000000000
r11=fffff900c28a0f50 r12=0000000000000117 r13=0000000001900010
r14=000000000000f0f0 r15=fffff900c075b380
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
win32k!DEVLOCKOBJ::bTightBoundsToRegion+0x18c:
fffff960`0025327c 00488d add byte ptr [rax-73h],cl ds:002b:00000000`c65b4f65=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x3B

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9600025327c

STACK_TEXT:
fffff880`0a25f7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DEVLOCKOBJ::bTightBoundsToRegion+0x18c


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
fffff96000253276 - win32k!DEVLOCKOBJ::bTightBoundsToRegion+186
[ 74:54 ]
1 error : !win32k (fffff96000253276)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .cxr 0xfffff8800a25ede0 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

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

 

[TanS]

I'm having the same problem help!

Hi Jerrys,

It seems to me like i'm having almost the exact same problem. When i browse the net it restarts and give me the same error. I was wondering if zigzag3143 can help me out with mines. This is happening to often 8 times already since installing windows 7 64bit.

 

[torrentg]

Hi Jerrys,

It seems to me like i'm having almost the exact same problem. When i browse the net it restarts and give me the same error. I was wondering if zigzag3143 can help me out with mines. This is happening to often 8 times already since installing windows 7 64bit.

Hey.

Please start your own thread so as not to confuse things with the OP.

Thanks.

 

[JerryS]

I think my issue is motherboard related. I have been doing some research on the Striker Extreme board and it looks like the culprit. I tried manually setting the memory timing and voltages, different combinations of DIMMS, brand new memory, fresh BIOS flashes, resetting CMOS and carefully setting everything 1 step time. At this point I can no longer boot into the OS, it hangs on the black screen. Settings that previously would get me into the OS no longer work. I am installing a new board and new memory tonight and we will see what happens. It would appear from all of the memory related crashes that I see reported that WIN 7 is a lot more demanding of the memory settings and voltages.

Things to note...memory test showed no errrors at any time. Trying to run the sfc / scannow caused an immediate crash. THere were frequent permissions errors and other odd behavior trying to run items from shortcuts to crashes with Explorer. I will do another complete re-format in install with the new board and we will see what happens.

-Jerry

 

[JerryS]

Probably need to close this thread. I replaced the motherboard and new memory. I will be opening a new thread on my new board next. 3 BSOD's tonight after a fresh install.

Jerry