unexpected shutdown in my windows 7!

Poor me,
I got another one!
find the attached please,

guys,

i really need your help.

Ryan2320 said:

Just picking out the obvious...

Have you updated all drivers for your system?? (video, Sound, etc)
Have you installed all Driver updates on your motherboard?
Does Device Manger have all drivers? Check there, Type Device Manger in the start menu..

This stated happening right when you finished building your PC, or after a few days??
Can you do a full system scan for virus, spy ware, malware.??
What Windows 7 OS are you using 32bit or 64bit..
Did you have any problems installing Windows 7?

Hope this Helps..

Capt.Jack Sparrow said:

sadon said:

Poor me,
I got another one!
find the attached please,

Hello Welcome to SF,

I guess its an issue with Memory and some old drivers. Lets start with basics. Update your BIOS Firmware. Also if your using any third party Antivirus / Firewall uninstall it and see whether it makes any difference. If your Overclocking please stop.

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System File Checker
Start > Run > CMD > Right Click and Run as administrator > SFC/ SCANNOW

Update the Following Driver

Code:

LMouFilt.Sys Wed Jan 24 05:11:16 2007 - Logitech SetPoint(TM)              
LHidFilt.Sys Wed Jan 24 05:11:13 2007 - Logitech SetPoint(TM)

Description

Code:

 MEMORY_MANAGEMENT (1a)
   # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004c5f030
Arg3: 000000000000ffff
Arg4: 0000000000000000

Bugcheck Analysis

Code:

BUGCHECK_STR:  0x1a_41790
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002d3f26e to fffff80002cccf00
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02d3f26e cc              int     
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

If these steps didn't fix then only run the Driver Verifier
Please run Driver Verifier according to these instructions to see if it can get us any extra information:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line. - Info by John

Hope this helps,
Captain

thank you both of you guys.
I have updated my GAx58A-UD7 motherboard's bios and also updated LogItech drivers along wiht and my Radeon ATI HD5850 and run a check up to see if i have bad secors in my hard drive. And everything now seems ok. it's been about 15 hours from the last time i got the BSoD.



I'll keep you guys posted once i get a new BSoD

Maaaaaaaaaaaaaaaaaaaaaaaaan

I just got a BSoD

this is so funny. Every time i report to you guys that my machine is stable, i get immediately a blue screen!



one question guys: how can i update ntoskrnl.exe driver. ALL OF MY BSoDs I SO FAR GOT ARE CAUSED BY THIS DRIVER! So, I am thinking if this driver can be updated to overcome those BSoDs.


another question guys : does RAM have a driver so that i can update?

i downloaded driver detective to update all the drivers in my machine. I am not going to go with Driver Verifier
as a first step. Let me update the drivers first by using driver detective and then will see if things will get stabled or not.

Many thanks Captin.

I have run three programs to see if my win 7 drivers need to be updated or not.

Driver Detective ( which is the one i put my money on) detects that i have 33 out-of-date drivers.

while,


the other two programs (Device doctor and Driver Agent) detect nothing out of date!

(all were running at the same time)

i am not sure which one is actually out of date.



for my system, not sure whether this observation is good to proceed with fixing errors, however i have noticed something that might help. I have scheduled my RegCure ( which is a registery cleaner program) to clean the registery 3 am everyday. the system after the cleaning gets a little bit stable.

sadon said:

I have run three programs to see if my win 7 drivers need to be updated or not.

Driver Detective ( which is the one i put my money on) detects that i have 33 out-of-date drivers.

while,


the other two programs (Device doctor and Driver Agent) detect nothing out of date!

(all were running at the same time)

i am not sure which one is actually out of date.



for my system, not sure whether this observation is good to proceed with fixing errors, however i have noticed something that might help. I have scheduled my RegCure ( which is a registery cleaner program) to clean the registery 3 am everyday. the system after the cleaning gets a little bit stable.

Sadon

If your drivers are the same as in your last DMP there are only four that could possibly be considered out of date. Thats the problem with the driver detective type programs. Their list of up to date drivers may be up to date or not. It also may be correct or not.

these are the drivers that might be considered old.

Code:

secdrv.SYS        fffff880`06352000    fffff880`0635d000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
LHidFilt.Sys        fffff880`04e1c000    fffff880`04e2e000    0x00012000    0x45b69d19    1/23/2007 6:41:13 PM                        
LMouFilt.Sys        fffff880`03e4a000    fffff880`03e5c000    0x00012000    0x45b69d1c    1/23/2007 6:41:16 PM                        
spldr.sys        fffff880`0145a000    fffff880`01462000    0x00008000    0x4a0858bb    5/11/2009 11:56:27 AM                        
amdxata.sys        fffff880`01097000    fffff880`010a2000    0x0000b000    0x4a12f2eb    5/19/2009 12:56:59 PM                        
rtkio.sys        fffff880`07995000    fffff880`0799d000    0x00008000    0x4a3c7af9    6/20/2009 1:00:25 AM