BSOD in Sleep Mode

[kcburgie]

After doing a custom install of Windows 7 64 bit, from Vista 64 bit, my computer blue screens while in, or just after wake from hybernation. Install seemed to go fine but the next day it blue screened, 0x0...F4, later 0x0....7A. Messege; momentarily lost track of hard drive.
I have spent the last two weeks checking hardware, software, program compatability and running countless tests. Updated all drivers including NVidia's 195.62 WHQL. No luck so far. The only way to keep it running was to disable sleep mode. Had to replace the DVD burner to get it to work consistantly.
Memtest86, Prime95, dskchk ,system files, no errors. Attached are the dump files.

I'd like to resolve this issue before I tackle my other computers!
Thanks, kcburgie

 

[zigzag3143]

After doing a custom install of Windows 7 64 bit, from Vista 64 bit, my computer blue screens while in, or just after wake from hybernation. Install seemed to go fine but the next day it blue screened, 0x0...F4, later 0x0....7A. Messege; momentarily lost track of hard drive.
I have spent the last two weeks checking hardware, software, program compatability and running countless tests. Updated all drivers including NVidia's 195.62 WHQL. No luck so far. The only way to keep it running was to disable sleep mode. Had to replace the DVD burner to get it to work consistantly.
Memtest86, Prime95, dskchk ,system files, no errors. Attached are the dump files.

I'd like to resolve this issue before I tackle my other computers!
Thanks, kcburgie

Hi KCB and welcome

Couple of questions?


Are you overclocking?

Do you use a raid?

Was the upgrade from vista to win 7 done as a upgrade, or clean install with format?

How long did you run memtestx86 for?


I am taking a look at the dmps, I get the feeling it is either a hardware problem, and or a memory problem

Thanks

Ken J+

 

[kcburgie]

I am not overclocking, nor running a raid . I did a clean install from Vista, reformated.

Ran the Memtest for four+ hours, maybe five, and prime95 for 12 hours last night, no erors.

Tried a different hard drive, run on 1GB, 2GBs and 3GBs, using each slot and letting the computer go in and out of sleep mode, same results.

Let me know what the dump files tell you and if there is anything else to try to solve this.

Thanks kcburgie

 

[usasma]

Last dump file is dated November 23 - have there been any further crashes since then? Is the system clock set correctly?

I'd suggest updating this driver due to it's age: mdmxsdk mdmxsdk.sys Mon Jun 19 17:27:26 2006
I'd guess that it's a part of the driver package for your Conexant modem.

The dump files aren't giving up much information - the common thread seems to be one of improper actions with security features. As such I'd suspect malware or a corruption of the OS.

For starters, please run at least one of these free, independent online antimalware scans: Malware Please let us know the results when it's done.

Here's more info on each of the errors:
STOP 0x7A
STOP 0xF4
STOP 0xc000021a

And here's the summary of the memory dump analysis':

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 13 16:16:32.946 2009 (GMT-5)
System Uptime: 0 days 4:58:41.006
BugCheck F4, {3, fffffa80040cdb30, fffffa80040cde10, fffff80002d90240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 13 11:16:46.565 2009 (GMT-5)
System Uptime: 0 days 16:02:46.625
BugCheck 7A, {fffff8a00676ea20, ffffffffc000000e, 77eca860, fffff9600014b630}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+13b630 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 14 12:31:30.574 2009 (GMT-5)
System Uptime: 0 days 13:46:10.634
BugCheck 7A, {fffff6fb80000000, ffffffffc000000e, 43534880, fffff70000000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LightScribeCon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 15 04:28:26.725 2009 (GMT-5)
System Uptime: 0 days 3:20:14.785
BugCheck 7A, {fffff6fc50015dc0, ffffffffc000000e, ae0d3880, fffff8a002bb8034}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 20 19:53:15.152 2009 (GMT-5)
System Uptime: 0 days 7:31:43.087
BugCheck 7A, {fffff6fc40009908, ffffffffc000000e, 94b7f860, fffff88001321308}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 20 10:48:29.118 2009 (GMT-5)
System Uptime: 0 days 8:09:28.178
BugCheck C000021A, {fffff8a00268a3a0, ffffffffc0000006, 77ab442b, 227e7b0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 21 05:07:30.183 2009 (GMT-5)
System Uptime: 0 days 6:25:48.243
BugCheck 7A, {fffff6fc40009a68, ffffffffc000000e, 73742860, fffff8800134d11c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 04:37:35.752 2009 (GMT-5)
System Uptime: 0 days 1:18:40.688
BugCheck F4, {3, fffffa80045eb060, fffffa80045eb340, fffff80002d7b240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 13:09:47.100 2009 (GMT-5)
System Uptime: 0 days 1:23:09.160
BugCheck F4, {3, fffffa80042c6b30, fffffa80042c6e10, fffff80002dd6240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 03:04:55.156 2009 (GMT-5)
System Uptime: 0 days 6:28:27.216
BugCheck 7A, {fffff6fb80008000, ffffffffc000000e, 118e1880, fffff70001000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  IoctlSvc.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 23 06:03:40.214 2009 (GMT-5)
System Uptime: 0 days 4:01:18.274
BugCheck 7A, {fffff6fc50012510, ffffffffc000000e, 67a95880, fffff8a0024a2b90}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

 

[kcburgie]

usasma,
Thanks for the info, its more than I got in a week from another site, who didn't respond to my last post. System clock is set correctly. Three other crashes, one on the 26th, and two on the 27th, while I was testing the ram cards. I'll see if there are reports and attach them.
Will follow your suggestions above and post the results.

kcburgie

 

[sman5922]

usasma,
Thanks for the info, its more than I got in a week from another site, who didn't respond to my last post. System clock is set correctly. Three other crashes, one on the 26th, and two on the 27th, while I was testing the ram cards. I'll see if there are reports and attach them.
Will follow your suggestions above and post the results.

kcburgie

Hi I have a similar problem, but I managed to get rid of the BSOD everytime I would wake from sleep mode my going to ATI's website and getting the latest driver from my video card. If you havent done that I suggest you do.

 

[kcburgie]

sman5922
my chip set is NVidia GeForce7100/nForce 630i. I updated the drivers to the latest version 195.62 last week the 25th, the night before the official release. I've had three blue screens since. Everyones problems are so similar, just off a bit.
thanks for the interest though.
kcburgie

 

[kcburgie]

usasma
I ran three of the antivirus/malware scans on the list, no detections. My antivirus software, Advira AntiVIR, scans and updates daily and also has shown no detections.
The modem driver is updated to ver.7.80.4.50, 5/6/09. The other was dated two years before I bought the computer.
I don't have any more minidump logs for Nov 26th and 27th, or at least I can't find them.
Let me know if I can do anything else. Started this about Nov 12th, a few more days can't hurt.
kcburgie

 

[sman5922]

sman5922
my chip set is NVidia GeForce7100/nForce 630i. I updated the drivers to the latest version 195.62 last week the 25th, the night before the official release. I've had three blue screens since. Everyones problems are so similar, just off a bit.
thanks for the interest though.
kcburgie

I myself am still having BSOD problems so I may not be much help but maybe we can come up with a solution together since our problems seem similar. May I ask the exact make and model of your computer is it desktop or laptop. Sorry if you already posted that info.

 

[usasma]

sman5922 - While you're welcome to participate in this thread, please start your own topic for your issues. This way your problem will get the individual attention that it deserves, and won't detract from the individual attention that we are giving to the original poster.

kcburgie - is the system still crashing on you? Is it giving you any other issues? Could you please upload this report?:

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

 

[kcburgie]

usasma
The system has not crashed since the 27th, but I'm not allowing it to hybernate. This seems to work around the problem, as the blue screens happen at wake up or in sleep mode. The new DVD drive works. As far as I know there are no other issues, but I've had limited time to play with things. Not having another system to compare it to is a drawback.

.nfo files are attached
Thanks
kcburgie

 

[usasma]

There are no entries in Windows Error Reporting for the month of December. Have you turned Error Reporting off on your system?

The MSINFO32 file indicates a crash on the 27th that's possibly related to I/O errors.
This would tend to support my theory that it's a storage driver issue (which I've never solved with my own system).

I'd suggest trying this driver to see if it helps: NVIDIA DRIVERS 15.49 WHQL

Have you updated your

 

[kcburgie]

usasma
My system has not crashed since Nov 27th when I was testing the ram cards. I have not turned off error reporting, but I can't explain why there's no reports for the 26th and 27th, maybe being low on ram could cause this? Computers sleep setting are at NEVER, the only way to keep it from crashing. I can return to factory setting and see if any new dumps bare fruit.
The NVIDIA driver suggested is where I started, my numbers are 8.15.11.8655, which date 10/1/09, wouldn't the new release 195.62 (8.17.11.9562 )11/26/09 that I am running now be better? I'll try it and see, can't hurt right?

Your last sentense "Have you updated your " ??

Interesting note; the D drive ( factory image ) recovery file is empty, 12.5 GBs of space. Is this a leftover from Vista or is it there in 7 also?

kcburgie

 

[usasma]

Sorry for the cutoff sentence - I get wrapped up in things and forget what I was doing (it's because I've got the Knack: http://www.carrona.org/knack.wav )

The missing sentence should read: Have you updated your storage drivers and/or chipset drivers with Windows 7 drivers?

The nVidia driver that I suggested is for your nForce chipset (v15.49) - not for the nVidia GeForce graphics driver (v195.62).

The WER stuff isn't critical - but it does cause me to wonder what's going on. It's possible that there weren't any errors reported during that time. I wouldn't worry about it for the time being - unless you start experiencing problems and there aren't any reports in WER.

If the factory image drive is empty, something has erased the information there. This partition would be necessary if you wanted to reinstall Vista (and may ease the transition if you want to reinstall Win7). You can overcome this by ordering a set of recovery DVD's from the system manufacturer (HP). Have the computer by you when you call 1-800-HPINVENT. As I recall, they're about $20 and you'll receive them in 4 or 5 days.

 

[kcburgie]

All drivers are up to date according to device manager, most devices running on 6.1.7600.16385 win 7 ver. Am I missing something here? NVidia v15.49 and v195.62 are in their respective spots. After the 15.49 install, I returned the sleep settings to 20 min and crashed on the second wake up. The desktop flashed several times ( not in prior times ) and the desktop gadget clock was not running. This happened twice last evening, back to never sleep and ran without a glitch.

I did find the dump files from Nov 26 to current and have attached them. Operator error i'm afraid!

The factory image ( D drive ) is only for recovery to Vista or is it nescesary for Windows 7 also. I did make recovery discs, but hate the thought of returning to Vista. When I tried an install on a blank HDD, there wasn't a D drive, so I was wondering.

Let me know if the dump files reveal anything.

Thanks for the help
kcburgie

 

[usasma]

Sorry for the delay in getting back to you.
I've been real busy, and we've lost some help here at the forums.

Device Manager tells you if things are updated in relation to Windows Update. This isn't an accurate thing because the driver manufacturer's may not submit their latest drivers to Windows Update. I've been trying this new tool out and you may want to give it a try (don't rely totally on it - but it's worth a look-see): Free Driver Update Software - Device Doctor

Working the minidumps as I type this....

I prefer hanging onto the D: drive. You own the full copy of Vista on the drive - and if your copy of Win7 is an upgrade then it's technically necessary to have it to "prove" your entitlement to the upgrade. If the space is crucial, then I'd make the recover disks and format the partition.

Please update this driver: mdmxsdk.sys Mon Jun 19 17:27:26 2006
I think it's associated with your Modem

Nothing significant with the rest of the dump files. I suspect either a corrupt/incompatible service - or malware. Have you scanned the system to see if it's infected?

If you have, please post back and I'll include some instructions for setting up Driver Verifier. We'll see if that will catch the bugger that's causing this.

 

[kcburgie]

usasma
I saw the sudden rash of new posts over the last week, no wonder your busy.

I'll look in to Device Doctor, some of these services aren't much help and don't uninstall fully.
The mdmxsdk.sys driver has already been update, version is dated 5/6/09. Conexant didn't have anything newer than 06 on the list.
The NVidia 15.49 WHQL driver for the chipset was a "version mismatch" with the 195.62 graphics driver, which is for the GeForce7100/nForce 630i onboard chipset, had to revert back.
The D drive recovery file is empty, restore points, even back before the the new install are also empty. Since the drive was formatted, these should have been removed from the HDD, right? It makes me wonder if its a bad install instead of other issues. I had made Vista recovery discs over a year ago when the computer was new.
The bare HDD I tried didn't have a D drive. That install also blue screened and my jump drives would cycle on and off. They work fine on other computers and in the Windows 7 install we're working on now. I can provide the dump files on that install if you think it will help the cause.
Scanned the system with TrendMicro, ESET, BitDefender and my own, AntiVIR and no detections.
Thanks for your help
kcburgie

 

[usasma]

Yes, if the D: drive is empty you can safely eliminate it when installing Win7.
A re-install would help to see if this is a hardware issue.
The best thing is to reinstall and only install drivers that aren't loaded during the installation.
Then test to see if it BSOD's - if it does, that tends to confirm hardware issues.

 

[kcburgie]

usasma
I did a new install last night, booted from disc, formatted, removed D drive. Only installed DSL and AntiVIR 9.0.0.415 ( adobe flash player active x 10 and MS visual 2008 C++ x86 9.0.3... came with it ) updated NVidia graphics and Lan, Conexant modem and Realtek audio drivers. Ran through device manager and updated any thing else, then ran windows update. Some system devices show " no driver installed " that were there before. DMA controller, high precision event timer, numeric data processor, NVidia nForce PCI system manager,PCI standard RAM controller, programable interupt controller, system speaker and system timer, but on the driver tab for each is the generic 6.1.7600.16385 driver. These maybe in the easy transfer file that I haven't run yet?
Let the computer run and it blue screened on the second wake up just as before. I reset sleep to never and it ran all night, no errors. I've attached the dump file. Let me know and I'll keep searching for the missing drivers.
kcburgie

 

[Geo64]

Update this driver:

mdmxsdk  mdmxsdk.sys  Mon Jun 19 17:27:26 2006

If you can't seem to repair it after doing that, disconnect from the internet physically. Then uninstall your antivirus and test the machine like this for a while.