BSOD - Unexpected Shutdown Win 7 Pro 64

[Toddsta]

Hello good people!

I am definitely not a computer guru - thus my post here - but am learning. Built a few computers with some help from more knowledgeable friends. Can work thru problems with assistance.

So... I installed a fresh Windows 7 Professional 64 bit OS on my new custom system (hopefully you can see my system specs from my registration?) and have had intermittent BSOD's.... never while I have been working on the system.

Seems like they are always waiting for me in the morning when I revive my computer from 'sleep' mode.... or when I do the same after a period of non-use during the day.

I have attached the .zip file of the error report. It seems like there may be two targeted issues "caused by driver":

1. NTOSKRNL.EXE
2. PSHED.DLL

I have no idea what these are, what they mean, nor how to fix them. Can you help?

I sincerely appreciate your patience in working with me, a computer neophyte.

Thanks!

 

[torrentg]

Hi. You may follow this.

http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

In the meantime and in between time, you could look into updating your chipset/motherboard drivers to latest available. Install latest bios if there's a new one too.

 

[Toddsta]

Hi Torrentg -

Thank you for your quick reply. I should have included that I have updated all drivers including chipset, etc available for the (win 7 64 bit) Asus P6T Deluxe per Asus site.

I believe I have for the Bios as well... but will double-check. Thanks.

 

[usasma]

NTOSKRNL.EXE and PSHED.DLL are components of the Windows operating system.
NTOSKRNL.EXE is the "core" of the OS. If it was causing problems you'd most likely have many more issues other than the BSOD's. So, it's likely that there are other things that are causing this. Uploading the dump files will allow us to run them and see what's going on "underneath the hood".

Additonally, your attachment shows that the error is a STOP 0x124. This is an error that your CPU reports to Windows. Since it reports in a different format than the Debugging Tools use - it's not likely that we'll get a lot of info out of the dump files.

But, these sort of errors are typically either hardware malfunctions or compatibility issues. So, if you've upgraded to Windows 7 recently there's a good chance that this is a compatibility issue (although hardware malfunctions are still possible).

Please run the free Windows 7 Upgrade Advisor to see if there's anything mentioned by it. It's available here: http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en

FWIW - I've got a P6T Deluxe, Core i7 920 and 12gB of OCZ RAM (ATI HD 4870 video and hardware RAID 5) that I've been using since the M3 release of Win7. The system has one issue (BSOD on sleep) - and that's due to my RAID card drivers, not the mobo.

There are a couple of Asus drivers that may cause issues - but I haven't experienced them on my system. Beyond that I'd have to suspect something that you've installed on the system. To test this, remove what you've installed and uninstall the software/drivers associated with it.

 

[Toddsta]

Thanks for your reply usasma -

I downloaded the Windows adviser, turned everything "on" and ran the adviser program.

I have included a screenshot of it's results.... seems like it doesn't like a Marvell Miniport Driver? Funny, because I don't have any exclamation marks in Device Mgr on this...

Also, I have a PCI 4-port USB adapter plugged into the short slot on my motherboard...it has an internal USB as well on the card - which I have a generic floppy/multicard internal reader plugged into. Could this be an issue?

 

[usasma]

All of this is speculation until we've seen your BSOD dump files (and maybe some other files).

Upload Dump Files
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

 

[Toddsta]

Thanks usasma -

Here's a zip of the mini dump files... also, I did discover there was a newer (week old) driver for my Nvidia card...so I just updated that. Here's the dump files: Thanks again for your willingness to trouble-shoot this for me!!

 

[usasma]

The errors are STOP 0x124 errors. These are errors that are reported by the CPU to Windows - so they're not as easy to read as the usual Windows STOP errors.

In addition to needing an update for the Marvell wired networking drivers - you also need an update for the Linksys wireless drivers that you're using.

I'd suggest updating those 2 sets of drivers, then seeing if that fixes things. If not, post back and we'll work on ruling out things on the system.

Also, I'd suggest disconnecting this device until we're finished troubleshooting:

Also, I have a PCI 4-port USB adapter plugged into the short slot on my motherboard...it has an internal USB as well on the card - which I have a generic floppy/multicard internal reader plugged into. Could this be an issue?

 

[Toddsta]

Thank you sir! I'll do it... I'll post back... one question though: I initially tried to use a Linksys wiresless adapter and had no luck, so I installed a Azio AWD102N wireless card which had known working Win 7 drivers....

Just curious about the Linksys driver - does it show a corrupt one? Thanks.

 

[usasma]

The Linksys driver (scmndisp.sys) is loaded in each of the dump files. If it's not common to both wireless adapters, then it's not supposed to be loaded.

Uninstall the Linksys adapter, then uninstall the Azio adapter.
Then check C:\Windows\System32\Drivers to see if the scmndisp.sys file is gone (If not, rename it to scmndisp.BAK).
Then install the Azio drivers and check to see if they installed an scmndisp.sys file. Continue running the system to see if that fixes the BSOD's.

 

[Toddsta]

usasma - I checked, and there is no "Linksys" program to uninstall. So, I opened up Device Manager...looked under Network adapters and then went to the drivers tab and it showed this for the Azio drivers.... Should I simply rename the scmndisp.sys to scmndisp.BAK?

If not, I am not sure how to uninstall a Linksys adapter that I cannot locate?? Thanks!

 

[torrentg]

Click the uninstall box and then there will also be a check box to click, to delete the driver software as well.

 

[usasma]

Please check Control Panel...Programs...Uninstall a program for both the Linksys and the Azio programs.
Remove them from there, then visit the Device Manager and remove anything that's leftover from there.
Then go to C:\Windows\System32\drivers and rename the scmndisp.sys to scmndisp.BAK (don't worry if it's not there).
Then install the Azio program again and see how it works.
Check in C:\Windows\System32\drivers to see if the Azio program installed a scmndisp.sys driver (just to be sure).
Check the date on the driver to ensure that it's not from 2007. If it is, post back and let us know.

 

[Toddsta]

will do... thanks...

 

[Toddsta]

Usasma - Ok. I uninstalled every network adapter I could find... and then rebooted...checked and the scmndisp.sys driver was still in the drivers list. So, I installed my Azio wireless adapter and then went in and renamed the scmndisp.sys to scmndisp.bak....

Should I be good to go and see what happens in the next couple days? The last BSOD took 1 1/2 days to pop up...so thinking I'll give it a few days...let it run all night etc.

Thanks a ton - - you've been a great help so far...

 

[usasma]

Yep, wait for the next BSOD. Hopefully it's been fixed and you'll wait for a long, long time!
Good luck!

 

[Toddsta]

Ok.. I don't know if this is related or not... but the system was working fine after I did as you advised... however...I left it running when I went to bed at 2 am this morning.

When I woke up... I came down and the system was in 'sleep' mode (not hibernation - had it turned off)... and I wiggled my mouse to revive the computer - - and only the case fans came on... no displays... I thought it was my wireless mouse, so I unplugged it and plugged in a standard usb mouse... no difference.

So, I turned the system off by holding in the case power button. I waited about 20 seconds and then pushed the case power button again, to turn the computer on - thinking that the system had just got hung up somehow.

Well, NOTHING came on then....no case fans...nothing.

I did see that the 'light' was on on my motherboard. I turned the power supply off...unplugged the power supply and waited about 5 minutes.

I plugged the power supply back in... turned the power supply switch on...which lit up the mother board lights and then I turned the case power but on...NOTHING... no fans, nothing.

So now, I have turned the power supply back off and uplugged it again...unplugged the power to my video card... and waited ten minutes.

I plugged the power supply back in and turned it's power switch on...and then pushed the power button on my case to turn it on and again.... NOTHING TURNS ON...NO FANS...NOTHING.

Any ideas here??? Thanks.

 

[usasma]

I don't know if it's related either, but I don't think so.
Something has broken, which in turn, has caused the system to stop booting.
The most likely thing (IME) is the PSU. Even if the mobo lights up, that doesn't mean that the PSU is good.

Can you borrow a PSU to see if that is the issue? Maybe purchase one that you can return? You'll only need to plug in the motherboard and the 4 prong thing on the motherboard to test if it works. Make sure you push the power button on the case in order to turn it on - otherwise the PSU won't do a durned thing.

 

[chev65]

I think I might clear the cmos before I did anything else.

 

[Toddsta]

Ok... whew! I took the battery out and cleared the CMOS along with the jumper clear... it's working now. What in tarnation would make THAT happen??