[SOLVED] Windows 8 SYSTEM_SERVICE_EXCEPTION BSODs

Status
Not open for further replies.
E

elephantnut

Member
Joined
Jan 13, 2013
Posts
6
View attachment Echo.zip

Hi,

First time I've done something like this, so let me know if I attached the file right.

· OS - Windows 8 64-bit
· Originally installed OS - Windows 7 64-bit
· Upgraded to Windows 8, straight onto a new Sandisk SSD. (The Windows 7 installation was on the HDD the laptop came with)
· Age of system (hardware) - ~2 weeks
· Age of OS installation - 3 or 4 days. I've installed Windows three times now on this SSD. After it BSODed the first time, I used the first reset option in Windows 8, that deletes all programs + resets all the settings. After the BSODs kept happening, I used the other option, that erases the SSD completely and then reinstalls Windows (installed off of a USB every time).

· CPU - AMD E-450
· Video Card - in-built
· MotherBoard - not sure

· System Manufacturer - HP
· Exact model number - HP Pavilion dm1-4108AU





Other info: I've upgraded the RAM from 2GB to 4GB too. Initially I left both sticks in. After the first BSOD, I took out the 2GB one. After the BSODs kept happening, I ran Memtest86+ for 12 hours (4 passes, 0 errors). Windows 7 on the HDD never crashed, the BSODs only happened after I installed the SSD + Windows 8. I think they always start happening after 3-4 days of running completely error-free. The first couple happened immediately after waking from sleep, a couple happened after restarting, and it's happened once while installing Sandisk's SSD software (to check for drivers - there were none), and once when surfing the web.

I've tested the RAM, I've updated the graphics drivers, and the Synaptic touchpad drivers. But the crashes seem really inconsistent - it hasn't happened while typing this. One time, it happened, then restarted, then crashed again, and Windows said it couldn't boot and had to system restore to a previous version.

I think it's either the Windows 8 installation, the SSD, or some other unrelated drivers. I might try upgrading the old installation (on the HDD) to Windows 8, and see if it crashes, but I don't want to do that until someone with more knowledge has taken a look at these attached files.

Oh, and all it ever says it SYSTEM_SERVICE_EXCEPTION, it's never been anything but that.

Thanks. :D
 
Hi -

The bugcheck on all dumps -

0x3b (0xc0000005,,,) = system service threw an exception;
excep = 0xc0000005 = memory access violation

The dumps name win32k.sys as the probable cause in the BSODs; it is a default of sorts and not the actual cause -
Code: 
win32k.sys    Wed Nov 07 22:59:09 2012 (509B2E0D)
http://www.sysnative.com/drivers/driver.php?id=win32k.sys

RAM or SSD should be check out first.

System files show a single 4 GB stick. Are there others?

Why do you think SSD may be involved? Check for firmware upgrade.

Since all bugchecks are the same and 0xc0000005 excp can be caused by a rogue 3rd party driver, run Driver Verifier first -

https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2


BSOD SUMMARY

Code: 
[font=lucida console]
Debug session time: Sat Jan 12 16:02:17.802 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011313-16707-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:09:23.854
Probably caused by : win32k.sys ( win32k!SURFACE::bRedirHooked+250 )
BugCheck 3B, {c0000005, 2dd17000, fffff8801b37cbf0, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 000000002dd17000, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8801b37cbf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SURFACE::bRedirHooked+250
BiosVersion = F.16
BiosReleaseDate = 05/29/2012
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dm1 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Jan 12 15:52:31.862 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011313-20358-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:19:44.892
Probably caused by : win32k.sys ( win32k!SURFACE::bRedirHooked+250 )
BugCheck 3B, {c0000005, 22098000, fffff8801bb1cbf0, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000022098000, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8801bb1cbf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SURFACE::bRedirHooked+250
BiosVersion = F.16
BiosReleaseDate = 05/29/2012
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dm1 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Jan  9 10:18:04.073 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011013-19890-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:00:33.127
Probably caused by : win32k.sys ( win32k!SURFACE::bRedirHooked+250 )
BugCheck 3B, {c0000005, 7660000, fffff880051ccbf0, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000007660000, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880051ccbf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SURFACE::bRedirHooked+250
BiosVersion = F.16
BiosReleaseDate = 05/29/2012
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dm1 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u][url]https://mvp.support.microsoft.com/profile/Griffith[/url][/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]
 
jcgriff2 said:
System files show a single 4 GB stick. Are there others?

Why do you think SSD may be involved? Check for firmware upgrade.
Click to expand...

Thanks for the quick reply!

I have the original 2GB stick that came in the laptop. I'll run Driver Verifier, and then if it's still crashing, I'll switch out the 4GB stick for the 2GB one (and maybe use the other slot and see if that makes a difference). I don't think it's the RAM, because memtest86+ didn't show up any errors, and that's reliable, right? :S

If it's not the drivers, then it'll have to be either the SSD or the Windows 8 installation, because the laptop ran fine on the HDD with Windows 7. Unless I somehow damaged the internals while switching the RAM/harddrive. :/

And there have also been reports of BSODs after waking from sleep with this particular laptop, when using SSDs with sandforce controllers. But I'm not sure whether or not this SSD has a sandforce controller or not, because it's relatively new, and there's not too much documentation on it. And also, the BSODs aren't consistently occuring when waking it from sleep - they've been happening all over the place (though mainly right after turning on or waking from sleep - but very infrequently).

Oh and there's no firmware update for this SSD either yet, because it was released pretty recently. I might see if I can find the stock firmware and manually install it later, if the driver verifier software doesn't work. I'll go try that now and see what happens.

Thanks!
 
I've run Driver Verifier for 24 hours - no BSODs. I might try find a stress tester, and see if I can force a BSOD. If I manage to, I'll switch out the RAM and try again, otherwise I'm not sure what to do. :/
 
No BSODs over the last 24 hours -- are you still having problems?

RAM swap is a good idea.
 
Most of the BSODs occur in around a 5 minute windows after restarting/turning on/waking from sleep. Sometimes two might happen immediately after one another, and then Windows says it can't boot and system restores. :/

I'm hoping for the best, but I haven't changed anything as of yet, so I doubt they'll stop.
 
elephantnut said:
I'm hoping for the best, but I haven't changed anything as of yet, so I doubt they'll stop.
Click to expand...

I asked if 'problems continue' because of your Driver Verifier post - no BSODs during a 24 hour period.

Maybe because no restarts during Driver Verifier run, no BSODs..? Your last post seems to indicate that may be the case:
elephantnut said:
Most of the BSODs occur in around a 5 minute windows after restarting/turning on/waking from sleep.
Click to expand...

elephantnut said:
Sometimes two might happen immediately after one another, and then Windows says it can't boot and system restores. :/
Click to expand...
When you get "Windows can't boot" - does it ask for the Windows DVD, e.g. "Insert Windows disc into drive a:" - or similar?

If so, that message is seen when Windows can't find the HDD, which brings your SSD back into focus as the likely culprit.

Did you experience BSODs when Windows 7 was on HDD on this system?

Regards. . .

jcgriff2
 
elephantnut said:
· OS - Windows 8 64-bit
· Originally installed OS - Windows 7 64-bit
· Upgraded to Windows 8, straight onto a new Sandisk SSD. (The Windows 7 installation was on the HDD the laptop came with)
Click to expand...


Is Windows 8 activated & validated?

Clicking on this link will begin Windows Validation - www.microsoft.com/genuine/validate

Did you install Windows 8 upgrade onto SSD like this:

https://www.sysnative.com/forums/windows-8-|-windows-rt/4282-windows-8-upgrade-blank-hard-drive.html

Regards. . .

jcgriff2
 
I'm not sure if there's a correlation between the activation/validation of Windows and the BSODs - I've noticed the BSODs only occur (again, not that often), after Windows says it needs to be activated.

I've used this method to get rid of the activation message (the "most helpful reply" method): Windows 8 Pro Upgrade Product Key can't be used to activate - Microsoft Community
Could it have caused any errors?

Oh, I just looked at the link again, and it's the same method as the second post from your link.
___

I can't recall 100%, but I don't think it's needed additional files while repairing Windows. But I'm not entirely sure, one time it may have asked to insert the USB, but I can't remember if that was after a BSOD, or when I was reinstalling Windows. :/

I ran Prime95, and did the blend test for about an hour - no issues.

Could it be something to do with the SSD not responding quickly enough when Windows starts up/wakes up? Hence the BSODs occurring right after boot?

I haven't used the laptop much in the past day, but I'll come back if the issues persist. Thanks!
___

I just had a thought - could the issue be caused by apps downloaded from the Windows Store? The crashes seemed to only start after installing the Skype and Evernote apps. These apps were removed after the system restore, so currently they're not installed, and I'm receiving no crashes.

This is all really frustrating because there's no concrete information about what's causing these.

I've also found these two posts:
System_Service_Exception Windows 8 - Microsoft Community
SYSTEM_SERVICE_EXCEPTION BSOD, possibly caused by using many apps at - Microsoft Community
which makes me suspect it could be something wrong with Windows 8. :/
 
Hi -

Based on entries in the Event Viewer logs, I would say reinstall Windows to help determine

The Event Viewer entries are confusing and contradictory.

During Windowsd 8 installation, NTFS reports c: is healthy; <1 sec later VOLMGR reports "Crash dump initialization failed" -
Read More:


Each boot-up:
Code: 
The following boot-start or system-start driver(s) did not load: 
cdrom
dam
EhStorClass


Errors likely related to your sleep problem:
Code: 
Event[652]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-01-07T19:04:17.629
  Event ID: 137
  Level: Error
  Description: 
Hardware has changed from previous boot.
  
The system firmware has changed the processor's memory type 
range registers (MTRRs) across a sleep state transition (S4). 
This can result in reduced resume performance.


Does Device Manager show red/yellow flags?
This is one of several driver install failures:
Installation Failure: Windows failed to install the following update with error 0x800F020B: SAMSUNG Electronics Co., Ltd. - Other hardware - SAMSUNG Mobile MTP Device.
Click to expand...


Unknown app pop-up errors - no clue as to what these are:
Code: 
Event[304]:
  Log Name: System
  Source: [COLOR="#FF0000"]Application Popup[/COLOR]
  Date: 2013-01-10T02:12:17.577
  Event ID: 56
  Task: N/A
  Level: [COLOR="#FF0000"]Error[/COLOR]
  Description: 
[COLOR="#FF0000"]N/A[/COLOR]

Where did the Windows 8 upgrade disc come from?

A bad Windows ISO could be to blame here, assuming hardware failure is ruled out.

Regards. . .

jcgriff2
 
I got the ISO using the Windows Updater thing from the Microsoft website.

I'll keep using it until/if it BSODs again. If it does, I'll redownload the Windows 8 ISO, and possibly use a different USB, and completely reinstall Windows.

Thanks for all your help so far! I'll report back.
 
Glad you got it solved.

Thanks for posting back.

Regards. . .

jcgriff2
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top