Blue screen after waking from sleep mode

- Collapse -

Most likely a driver issue.

by Kees Bakker Jan 13, 2010 10:20PM PST

Not all drivers for all devices are happy with coming out of sleep mode.
A common example is the network card. That has to tell the world (well, the router) that it's alive again. It could well be they tested it stand-alone at Puget and then this wouldn't occur. Easy to check by disconnecting the network cable, and see what happens then.
If that's the case another driver (or another network card) might do wonders. Assuming the network connection is on the motherboard, it's a motherboard driver; maybe the motherboard maker has a new driver available. Just a guess, of course.

- Maybe hibernate works. Maybe hibernate doesn't work either. Worth a try.
- What are the details of the crash?

Kees

- Collapse -

What do you mean by details?

by gypsy boy Jan 13, 2010 10:34PM PST

By details, I am assuming you mean what the minidump files say. My problem with opening them is that the Microsoft pages explaining how to do it are too complicated for my fifth-grade mind. What else can I do to help? (and thanks).

- Collapse -

Try the Event Viewer.

by r. proffitt Forum moderator Jan 13, 2010 10:57PM PST

It may tell you which driver or other has failed.

This will be technical and if too much, make it their problem to solve.
Bob

- Collapse -

Great idea, thanks and....

by gypsy boy Jan 14, 2010 2:41AM PST

I didn't know about Event Viewer so, if nothing else works, this thread has been great because I just learned something new. FWIW, the people at Puget also directed me to a free download that may help opening (or making sense of) minidumps. They sent me a link to resplendence.com That site seems worth checking out and the download, in particular, should help me (or, far more likely, them) figure out what's crashing my system. Thanks again for the help.

- Collapse -

Let me share.

by r. proffitt Forum moderator Jan 14, 2010 3:25AM PST

While I'm been on this ride since before DOS those dumps have been useful 1 time. Where as the EVENT VIEWER (see google) has been the gold mine of information about crash city.

I'd google a little then look at the event viewer then share those here.
Bob

- Collapse -

This is probably not what you're looking for, but...

by gypsy boy Jan 14, 2010 5:52AM PST

This seems to be the pertinent text from the Event Viewer.

SUMMARY PAGE EVENTS
Critical 1/13/2010 7:15:33 PM Kernel-Power 41 (63)
Critical 1/13/2010 6:37:47 PM Kernel-Power 41 (63)
Critical 1/12/2010 9:19:25 PM Kernel-Power 41 (63)
Critical 1/12/2010 8:55:03 PM Kernel-Power 41 (63)

Clicking on the Details tab yields this:
+ System

- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002

- TimeCreated
[ SystemTime] 2010-01-14T01:15:33.641623900Z
EventRecordID 8799
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer Puget-65830
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa8008408060
BugcheckParameter3 0xfffffa8008408340
BugcheckParameter4 0xfffff80002d80240
SleepInProgress true
PowerButtonTimestamp 0

There were four "Critical" events. Here are the details for the other three:

#2
+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-01-14T00:37:47.342028400Z

EventRecordID 8702

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Puget-65830

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa80090042b0
BugcheckParameter3 0xfffffa8009004590
BugcheckParameter4 0xfffff80002d98240
SleepInProgress true
PowerButtonTimestamp 0

#3
+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-01-13T03:19:25.853635000Z

EventRecordID 8245

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Puget-65830

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress true
PowerButtonTimestamp 0

#4
+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-01-13T02:55:03.920827300Z

EventRecordID 8142

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Puget-65830

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 122
BugcheckParameter1 0x20
BugcheckParameter2 0xffffffffc000009d
BugcheckParameter3 0xfffffa80084cc7c8
BugcheckParameter4 0x0
SleepInProgress true
PowerButtonTimestamp 0

Thanks!

- Collapse -

Link, comment.

by r. proffitt Forum moderator Jan 30, 2010 10:48PM PST

http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/9e71f600-7c62-4869-8236-964e93d17936
"There are numerous reports of issues with the RC and power-state transitions. If you've got the most recent drivers and the latest BIOS and firmware, it may be that the best you can do until Windows 7 hits GA is to disable the problematic functions."

Bottomline. The maker is on the hook here for BIOS and DRIVERS. Everything points to BIOS and DRIVERS. Everything!

You could forgo SLEEP modes and try HIBERNATE until the maker supplies drivers. This is not your problem to solve as the makers do not provide SOURCE CODE for us to edit and fix.
Bob

- Collapse -

Or this (from whocrashed)

by gypsy boy Jan 14, 2010 6:03AM PST

Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/14/2010 1:15:37 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008408060, 0xFFFFFA8008408340, 0xFFFFF80002D80240)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\011310-14336-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Microsoft

- Collapse -

Good intel.

by r. proffitt Forum moderator Jan 14, 2010 8:18AM PST

http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c00302778&product=18703 and many more point to too many causes.

From bad ram that passes memory test to BIOS settings and of course the link above.

Troubleshooting is unusually hard for this one but the most common hardware issue continues to be these one off made machines with makers that miss the RAM settings a little.

Here's my question. Ready?

Could you verify that the memory voltage and timing in the BIOS meets that of the memory sticks specifications?

That item has paid off for me when tracking down this code too often to not ask you to do this.

-> And sorry that it is very technical but your machine appears to be a home built or something of a clone job so we have to know.
Bob

- Collapse -

Um. Golly. I'd love to answer your question...

by gypsy boy Jan 14, 2010 8:26AM PST

...but you've just exceeded my pay level by about a factor of 100. I understand (in principle, I think) the question. But I have absolutely no idea how to even begin answering it. The only thing that appears to be certain is that it's not a trojan/virus. Other than that, I'm sorry but I'm at a loss to know how to proceed. Thanks for all your time and effort though.

- Collapse -

KERNAL POWER -EVENT ID 41

by Cindyh1226 Jan 30, 2010 10:37PM PST

Hi, I have a new PC with Windows 7 and get the same Event ID 41 (I've had only one blue screen). From other posts, it is not typically hardware related, but power saving related. Common advise has been to DISABLE THE HIBERNATE. I had changed it earlier, but for some odd reason my PC went back to the Dell mode, not the Power Saver mode where I had disabled it originally. I just turned it off again and will see if helps alleviate the problem.

- Collapse -

May have identified the problem

by gypsy boy Jan 30, 2010 11:28PM PST

After working with Puget Systems for a long time now, I may--emphasize "may"--have isolated the problem. It does not appear to be a hardware problem but a software one. And after adding apps one at a time, I think the issue is caused by the Adobe Flash Player plugin. It seems to be an Adobe issue, for some reason, and uninstalling the plugin has--at least for the moment--stopped the blue screens. Keeping my fingers crossed and will report back when I know more.

- Collapse -

So it's as good as an iPad now?

by r. proffitt Forum moderator Jan 30, 2010 11:52PM PST

The iPad gets slammed for no Flash. This seems like an ODD SOLUTION to me since my HP d4999t machine with 64-bit 7 among some thousand other models run flash just fine.

Seriously consider asking them to get this machine fixed.
Bob

- Collapse -

I have

by gypsy boy Jan 31, 2010 2:12AM PST

I have and they asked--reasonably in my opinion--to see if we could troubleshoot it to make certain what the problem is. It was only in the course of following their directions that I discovered what I did. They have also offered, if it can't be fixed, to build me an entire new machine (at no cost). Seems fair to me. Some things can't be helped.

- Collapse -

That's fair.

by r. proffitt Forum moderator Jan 31, 2010 2:26AM PST

You shouldn't be a beta tester for their machines.
Bob

CNET Forums

Other Forums

Forum Info