BSOD in Sleep Mode

[SethT]

Also have BSOD on sleep & hibernate

Clean install of Windows 7 64-bit and have updated all drivers from Device Manager. Still get bsod after sleep and hibernate mode. Have disabled all startup items except Microsoft Defender. Upgraded to latest GeForce driver released a couple of weeks ago.

Seems like a lot of people are getting bsod on Windows 7 64-bit systems. Maybe this is a Microsoft problem?

 

[kcburgie]

Geo64
The msmxsdk.sys is a modem driver and I can't find anything newer that 06/07 version, So I am using the MS version dated 5/6/09.
Advira AntiVIR is on the MS compatablity list and also been reccommended here on this forum. I'll see if it helps, but ...
kcburgie

 

[kcburgie]

Clean install of Windows 7 64-bit and have updated all drivers from Device Manager. Still get bsod after sleep and hibernate mode. Have disabled all startup items except Microsoft Defender. Upgraded to latest GeForce driver released a couple of weeks ago.

Seems like a lot of people are getting bsod on Windows 7 64-bit systems. Maybe this is a Microsoft problem?

SethT
MS has told me its a hardware problem and HP says its an upgrade issue. The only options are sistematicly narrow down the source and fix it, or revert back to Vista, which I dread.
The only thing that has worked for so far, is to set the computer sleep setting to never and then test the ideas as they come along.

kcburgie

 

[kcburgie]

Geo64
Uninstalled AV and ran tests today . It didn't help, two blue screens, 0x0...F4. The first time the screen went black with only the cursor. The second time all the icons disappeared. Returned the sleep settings the never and let it run for a couple hours. When I came back the screen was frozen.
Dump files attached

kcburgie

 

[usasma]

Both were caused by wininit.exe - which I haven't seen in a long, long time.
In the old days it was a symptom of a malware infection. Please try scanning for malware in order to rule it out.

Then try running SFC.EXE /SCANNOW from an elevated (Run as administrator) Command Prompt.

Also, as you get time, please run these 2 tests:
Memory Diagnostics
HD Diagnostic

Let us know the results and we'll move on from there.

 

[kcburgie]

usasma

I ran sfc.exe/scannow twice and there were no integrity violations.

Virus scanned with TrendMicro House call 7.1, Avira, no detections. And Windowsecurity trojanscan, 6 cookies, no other warnings.

Downloaded Seatools for Windows, ran long drive test and generic long test and passed both.

Memtest86+ v4.0 is on its 7th pass now, no errors. Yesterday I had swapped memory cards with some I had removed from my main computer when I replaced the processor last week, didn't make any difference that I could tell.

Wininit.exe may have come from my DSL provider, hard to tell, old install disc. If you Google it its like the mdmxsdk modem driver, some say its a nescesary part of the operating system, where others say its a trojan / malware and should be removed. Got a coin ?
Is there a prefered method of removal ? One site lists the path through registery, TrendMicro has a trojan cleaner, not sure if its free, or if it works. If removed, could it cause more issues ?

No crashes ( not hybernating ) or freeze-ups today. Tomorrow will reset sleep setting and see what happens as I wait for your insight on the wininit issue.

Thanks for all your help on this.

kcburgie

 

[usasma]

wininit.exe is a critical part of the OS. During startup it's what starts SERVICES.EXE, LSASS.EXE, and LSM.EXE. Then it initializes a part of the registry, and does some user-mode initialization. These are involved in security of the OS, so that's why they're frequently seen with infections.

If you're unsure of it, submit it to Jotti's malware scan for testing. Don't remove it unless it's in the wrong place.

 

[kcburgie]

usamsa

I've spent the last several days testing some different power setting combinations and nothing seemed to work. I'm still running minimum programs and have not tranfered any of my previous files. This install freezes randomly, as well as blue screens if I let it go into sleep mode. Monday the screen was froze nearly every time I tried to use the computer, sometimes for just a few minutes and twice I had to do a hard restart. Three seperate installs and three slightly different sets of problems. I'll atach the dump files.

Today I see that MS has released a hot fix for errors 0x0...F4 and 0x0....7A, could this the the fix ? Is it better to wait for the official update ?

Keep me posted
kcburgie

 

[usasma]

Have you got a link to the hot fix release?

The link that you posted isn't the dump file - it's just a shortcut to it on your hard drive:

C:\Windows\Minidump\122309-20607-01.dmp

 

[kcburgie]

usasma
The hot fix is referenced in a reply from Tews in Destroyer1990's post " Please refer " HERE " for just released hotfixes for your issues.." Not sure if I can copy the link. It's dated 12/22/09.

Sorry for the dump file mishap. I have company and was in a hurry. Try this one

Thanks and Merry Xmas
kcburgie

 

[usasma]

Link's here (found it by accident!): http://www.sevenforums.com/crashes-debugging/48955-hotfix-3-stop-errors-resuming-sleep-hiberate.html

Does this error occur when you resume from sleep? If so, then the hotfix is for you.
Not going into sleep - but coming out of sleep. It does this because larger hard drives take so long to check when coming out of sleep.

I'm at the point here that I think it's either a hardware problem or a deep seated Windows corruption.
The "fix" for either is a clean, plain vanilla install of Win7. Get the Windows Updates, but don't get any drivers. Install an antivirus to protect you and nothing else. If it still crashes, then it's likely to be hardware.

Not much info from the attached dump files.

 

[kcburgie]

usasma

I've been running a semi vanilla install for the past two weeks now, only Nvidia updates and Realtek and modem. No other programs but AV and DSL. Seatools for windows to check the HDD. No old files have been transfered.

I've yet to try the hot fix for error codes F4 and 7A because of the freezing issue. Kind of waiting form the official update to be released. Tried setting the hard drive to never sleep, but that hasn't helped either. In the meantime I just let the computer run and found if I keep the monitor from going to standby it doesn't freeze. I'll have to live with that for now.

I read in one of your replies to another thread that you had the same blue screen on wake up problem. Did you try the hot fix, and if so did it help?

One dump file, just in case the Lock Ness monster was swimming by.

Thanks for all your help
kcburgie

 

[GoldenOrb]

For what it is worth, I was running Media Center under Vista (successfully) and upgraded to Windows 7 (x64) by installing it on a newly installed 1.5TB HDD.

When my Win7 system came out of Sleep mode, particularly when I was running Media Center, I often ended up with the BSOD. I reinstalled Win7, updated drivers, etc on numerous occassions, all to no avail.

I then happened to come across the Win7 hotfix mentioned above, installed it, and had no further problems with the BSOD to date - touch wood.

 

[SethT]

BSOD - no hotfix, just upgraded motherboard bios

I fixed my BSOD problem by just upgrading to the latest motherboard BIOS. I did not try the MS hotfix which appears to be limited to fixing a very specific setup.

 

[zigzag3143]

usasma

I've been running a semi vanilla install for the past two weeks now, only Nvidia updates and Realtek and modem. No other programs but AV and DSL. Seatools for windows to check the HDD. No old files have been transfered.

I've yet to try the hot fix for error codes F4 and 7A because of the freezing issue. Kind of waiting form the official update to be released. Tried setting the hard drive to never sleep, but that hasn't helped either. In the meantime I just let the computer run and found if I keep the monitor from going to standby it doesn't freeze. I'll have to live with that for now.

I read in one of your replies to another thread that you had the same blue screen on wake up problem. Did you try the hot fix, and if so did it help?

One dump file, just in case the Lock Ness monster was swimming by.

Thanks for all your help
kcburgie

hi and welcome

this ine probably caused by a critical file termination.

I would
run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow


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\122709-19406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
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`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Sun Dec 27 22:36:09.386 2009 (GMT-5)
System Uptime: 4 days 18:43:05.720
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80031794a0, fffffa8003179780, fffff80002dc4240}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

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

[B]CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.[/B]
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80031794a0, Terminating object
Arg3: fffffa8003179780, Process image file name
Arg4: fffff80002dc4240, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80031794a0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

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

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`037550e8 fffff800`02e47142 : 00000000`000000f4 00000000`00000003 fffffa80`031794a0 fffffa80`03179780 : nt!KeBugCheckEx
fffff880`037550f0 fffff800`02df3269 : ffffffff`ffffffff fffffa80`04270a00 fffffa80`031794a0 fffffa80`031794a0 : nt!PspCatchCriticalBreak+0x92
fffff880`03755130 fffff800`02d77c74 : ffffffff`ffffffff 00000000`00000001 fffffa80`031794a0 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17a06
fffff880`03755180 fffff800`02abb153 : fffffa80`031794a0 fffff800`c0000005 fffffa80`04270a00 fffff880`03755b78 : nt!NtTerminateProcess+0xf4
fffff880`03755200 fffff800`02ab76f0 : fffff800`02afbada fffff880`03755b78 fffff880`037558d0 fffff880`03755c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03755398 fffff800`02afbada : fffff880`03755b78 fffff880`037558d0 fffff880`03755c20 00000000`00792170 : nt!KiServiceLinkage
fffff880`037553a0 fffff800`02abb542 : fffff880`03755b78 00000000`000116e4 fffff880`03755c20 00000000`00791c48 : nt! ?? ::FNODOBFM::`string'+0x4619d
fffff880`03755a40 fffff800`02aba0ba : 00000000`00000001 00000000`000116e4 00000000`00000201 fffffa80`028d61c0 : nt!KiExceptionDispatch+0xc2
fffff880`03755c20 00000000`779159ad : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00790ef0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779159ad


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner
---------

 

[kcburgie]

SethT
HP does not have a BIOS update and Foxconn doesn't list the motherboard on their site. Proprietary C. The BIOS is so basic that there are only a few changes that can be made.

Zigzag 3143
No integrity violations found in sfc/scannow just as before.

Since I have been recieving the F4 and 7A stop codes, I was wondering if it has helped anyone. My HDD isn't very big (320GB) but if its a little slow on the uptake, this may solve the problem.

kcburgie

 

[sman5922]

Hi again,

I posted a while ago on this thread and I've been following it because my problem is just so similar. Can you please describe to me the state of your problem now? Like did anything change. I also get the random BSOD, but usually at wake-up. I also have a 320 GB HDD. I'm really wondering if its the hotfix that will help. By the way, could you please tell me where the stop errors would be shown?

 

[usasma]

My errors are STOP A0 - and they occur at a different point in the OS's operation than the one's referred to in the hotfix article (mine occur as sleep happens - not when resuming)

 

[kcburgie]

Hi again,

I posted a while ago on this thread and I've been following it because my problem is just so similar. Can you please describe to me the state of your problem now? Like did anything change. I also get the random BSOD, but usually at wake-up. I also have a 320 GB HDD. I'm really wondering if its the hotfix that will help. By the way, could you please tell me where the stop errors would be shown?

sman5922
My desktop only bsod's at wake up from sleep, at least so far.Since you have a laptop, I'm not sure if the fix will work for you. Follow the advice of usasma, torrentg and the rest, they are trying to figure this out for you, and it may help someone else along the way.
I've reset the "auto restart after failure" in BIOS so I can read the stop error codes before restarting.
You really do need to fill out your system specs.
kcburgie

 

[kcburgie]

My errors are STOP A0 - and they occur at a different point in the OS's operation than the one's referred to in the hotfix article (mine occur as sleep happens - not when resuming)

usasma
Sorry to hear that.
I'm going to try the fix and see what happens. Was hoping to get a little more feed back first. I don't like GREY areas. I've ordered a new hard drive just in case this isn't it, who knows. It's like chasing a ghost in a wind storm for me.
Spent some time on Technet last night, lots of articles, some of interest, but nothing that pushed me over the edge.
I'll keep you posted and thanks for all the help.

kcburgie