Sign-in / Sign-up
Your question
Solved

Random unexpected shutdowns

Tags:
  • Drivers
  • Error Message
  • Windows 7
Last response: in Windows 7
February 21, 2010 4:52:53 PM

Hey everyone i noticed if i keep my system on overnight i will find an error message saying "windows has recovered from an unexpected shutdown" with this on it

Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.768.3
Locale ID:1033
Additional information about the problem:
BCCode:3b
BCP1:00000000C0000005
BCP2:FFFFF80002C82105
BCP3:FFFFF88007C5AA20
BCP4:0000000000000000
OS Version:6_1_7600
Service Pack:0_0
Product:768_1

Its only seems to happen when i leave the system on over night, i also had a problem with the system coming out of sleep mode so i disabled sleep and hibernation
i feel like the 2 may be related...can anyone help?

More about : random unexpected shutdowns

Best solution

a c 224 $ Windows 7
a b \ Driver
February 21, 2010 5:59:44 PM

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Parameters

The following parameters are displayed on the blue screen.
Parameter Description
1 The exception that caused the bug check
2 The address of the exception record for the exception that caused the bug check
3 The address of the context record for the exception that caused the bug check
4 0

Cause

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.

--------------------------------

In layman terms, update your video driver and see if you keep getting bluescreens.
Share
February 21, 2010 9:02:59 PM

Best answer selected by adroc31.
m
0
l
Related resources
February 21, 2010 9:03:23 PM

will do thnx
m
0
l
a b $ Windows 7
February 22, 2010 9:33:30 AM

ummm TEST YOUR HARDWARE
m
0
l
February 22, 2010 11:10:28 AM

spoke 2 soon....i left the system on over night to make sure that updating my video card drivers would work but it didnt i got this message this morning.......

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002CEC35F
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\022210-13525-01.dmp
C:\Users\Sal\AppData\Local\Temp\WER-16598-0.sysdata.xml

How would i go about testing my hardware?
m
0
l
February 22, 2010 12:22:47 PM

go to power options, from the left panel click "choose when to turn off the display" and set "turn off the display" to "never"
m
0
l
February 22, 2010 2:00:18 PM

You think its my monitor going into sleep mode thats causing it?
I would rather solve the problem than just work around it, if i dont have to keep everything powered up when it sits idle.

m
0
l
February 22, 2010 4:22:10 PM

Try this first, and see if the problem persists.

and a little more details about your system specs would be a good idea too!
m
0
l
a c 224 $ Windows 7
a b \ Driver
February 22, 2010 4:23:28 PM

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

----------------------

At this point, I would say test your RAM with MemTest86+. Let it run though at least one complete pass (pass, not test) and see if any errors appear.
m
0
l
February 23, 2010 12:00:04 PM

The_Prophecy said:
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

----------------------

At this point, I would say test your RAM with MemTest86+. Let it run though at least one complete pass (pass, not test) and see if any errors appear.


I used the built in windows mem test and it said it was fine..not sure if thats the same kind of thing..im not familiar with memtest86, im pretty green when it comes to this stuff but i think it needs to be run from a disk?
m
0
l
a b $ Windows 7
a b \ Driver
February 23, 2010 1:26:46 PM

Usually, a 'best answer' means the topic is closed.
Have you fixed the problem?

You can build a bootable CD with memtest86. You'd burn the ISO image for creating bootable CD (Windows - zip) (un-zipped of course) from http://www.memtest86.com/

m
0
l
February 23, 2010 3:15:40 PM

WR2 said:
Usually, a 'best answer' means the topic is closed.
Have you fixed the problem?

You can build a bootable CD with memtest86. You'd burn the ISO image for creating bootable CD (Windows - zip) (un-zipped of course) from http://www.memtest86.com/

I know im sorry i spoke to sson and the problem is still there.
i will try and run memtest86 tonight after work
thanks for the help everyone
also .... should i start a new thread with the results? or cont. here i dont want to mess up the format
m
0
l
a b $ Windows 7
a b \ Driver
February 24, 2010 3:49:28 PM

I think its best to start a new thread, and include what trouble shooting steps you've taken - like running memtest86.
m
0
l
June 10, 2010 6:51:41 AM

I am having the same problem, and I've tracked it down to NVIDIA's nvlddmkm.sys driver. Updating to the latest has not helped thus far.

To identify the cause of a BSOD, download Microsoft Debug Tools from http://www.microsoft.com/whdc/devtools/debugging/defaul...

Install and run the dumpchk.exe utility from the command line, with the filename of the minidump as the parameter, e.g.:
dumpchk c:\windows\minidump\06120-123302-1.dmp

It will look at where each driver was loaded in the memory, cross-reference that with the address that caused the crash, and finally spit out the likely driver file that was responsible.
m
0
l