BSOD - Shutdown unexpectedly

fuzzy76 · 29 Jan 2010

I installed windows 7 ultimate 64 bit on a new build. It was working fine for about a week, but recently I've been getting error messages saying that the computer has shutdown unexpectedly. Both times it has happened the computer had been in sleep mode. It doesn't always do this when in sleep mode. I've attached the contents of the minidump folder. Thanks very much for the help. Please let me know if I left out anything you need to know.

John

richc46 · 29 Jan 2010

I will request help for you, from one of our BSOD experts. You will be helped soon.

**Capt.Jack Sparrow** · 29 Jan 2010

fuzzy76 said:

I installed windows 7 ultimate 64 bit on a new build. It was working fine for about a week, but recently I've been getting error messages saying that the computer has shutdown unexpectedly. Both times it has happened the computer had been in sleep mode. It doesn't always do this when in sleep mode. I've attached the contents of the minidump folder. Thanks very much for the help. Please let me know if I left out anything you need to know.

John

Hi John, Welcome to SF,

I guess the issue is with Canonical Display Driver cdd.dll download the latest update from the website.

Run the Memory Diagnostic & HD Diagnostic
Also i would recommend to run System Integrity Checker

Start > Run > CMD > Right Click and Run as administrator > SFC/ SCANNOW

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff8a000107b78, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 000000008cd61860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff960001d6970, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Update the driver

Code:

AsIO.sys     Mon Dec 17 14:41:49 2007

Hope this helps,
Captain

fuzzy76 · 30 Jan 2010

Captain,

Thanks for the help. I ran memtest for 3 passes and didn't find any errors. It seems like from other posts that this isn't a guarantee that there are indeed no errors. However, I decided to move on and try some other things you mentioned. I had some trouble locating a new cdd.dll driver. It seems like something from microsoft, but when I tried to update a fix I found on the microsoft page it said it was already loaded. I probably should have mentioned that I recently added a avermedia TV tuner to my system. I though I would reload that driver with the most current just to see if that had anything to do with anything. I noticed when I loaded the driver this time the tv tuner driver loaded without a problem but I got an error message about a multimedia controller. I'm not sure what this is. Windows gave me an option to try again with different setting, I clicked ok and it loaded. So last night there was no crash. I'll keep monitoring and post if it crashes again. I'm also going to try and run the harddrive diagnostics later today.

Thanks again.

John

fuzzy76 · 03 Feb 2010

Hi all. I need help again. I ran memtest and no errors were detected. I also ran an hd diagnostic and nothing came back. I thought I updated the drivers. Everything seemed to be stable for a couple days, but then it crashed today. Once it crashed when the computer was in sleep mode, but it may have been waking up to record a show in media center. The second crash was when I was waking it from sleep to do some work. I've attached the dmp files. Any help would be greatly appreciated. Thanks

John

zigzag3143 · 04 Feb 2010

fuzzy76 said:

Hi all. I need help again. I ran memtest and no errors were detected. I also ran an hd diagnostic and nothing came back. I thought I updated the drivers. Everything seemed to be stable for a couple days, but then it crashed today. Once it crashed when the computer was in sleep mode, but it may have been waking up to record a show in media center. The second crash was when I was waking it from sleep to do some work. I've attached the dmp files. Any help would be greatly appreciated. Thanks

John

Hi John

These were probably caused by csrss.exe. This is the user-mode portion of the Win32 subsystem; Win32.sys is the kernel-mode portion. Csrss stands for Client/Server Run-Time Subsystem, and is an essential subsystem that must be running at all times. Csrss is responsible for console windows, creating and/or deleting threads, and implementing some portions of the 16-bit virtual MS-DOS environment.

I would run a system file check to repair it and others
typecmd in search>right click and run as admin>sfc /scannow

Let us know the results

Ken

fuzzy76 · 04 Feb 2010

Ken,

I ran the scannow as suggested. It ran, and I got the message that "Windows Resource Protection did not find any integrity violations." I did notice one thing though that seemed kind of weird. The crashes seem to happen around the same time. 11:24am yesterday and 11:24am today. Is there anything that would make it crash at the same time, while in sleep mode? Automatic updates are set for late evening and media center wasn't recording anything at either time. I don't know if the time means anything it just seem like a weird coincidence. I've attached the minidmp from today if that can help any. Once again thanks again for the continued assistance.

John

usasma · 06 Feb 2010

Just a suggestion:
Go to Start and type Task Scheduler
Then open Task Scheduler and see if there's anything scheduled to run around that time.
Be sure to check earlier times in case it's a long running program such as scan or a backup.

fuzzy76 · 06 Feb 2010

Thanks for the suggestion. I was wondering if there was a way to check scheduled tasks. I opened up the task scheduler and nothing showed up. I looked at active tasks too and nothing seemed to match the crash times. The computer crashed again yesterday at 11:24am. But it also crashed again this morning. Again it happened while it was in sleep mode. I've attached the dmp files again, if anyone has time to take a look at them. Thanks

John

usasma · 06 Feb 2010

Upload this file for us to have a look at:

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.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Please update this driver that zigzag3143 requested: AsIO.sys Mon Dec 17 04:11:49 2007
It's a part of the Asus utilities on your system - so visit the Asus support website to obtain it.

Please run one of these scans "just in case":

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb  3 12:23:12.239 2010 (GMT-5)
System Uptime: 0 days 18:16:00.003
BugCheck F4, {3, fffffa8005aba060, fffffa8005aba340, fffff80002d88240}
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: Thu Feb  4 12:23:13.613 2010 (GMT-5)
System Uptime: 0 days 15:02:17.003
BugCheck F4, {3, fffffa8004dae060, fffffa8004dae340, fffff80002dd2240}
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 Feb  5 12:23:11.829 2010 (GMT-5)
System Uptime: 0 days 13:45:30.593
BugCheck F4, {3, fffffa8005c8a970, fffffa8005c8ac50, fffff80002dd0240}
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: Sat Feb  6 08:04:51.620 2010 (GMT-5)
System Uptime: 0 days 19:40:36.383
BugCheck F4, {3, fffffa80059d5a70, fffffa80059d5d50, fffff80002d8d240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT