first BSOD for Ages

[penfold007]

Had a BSOD a couple of hours ago, and was wondering if someone could take a look at the mini dump for me?
I haven't installed anything new, be it software or hardware for a while so can't see what it was caused by??

 

[brianzion]

hi
while you are waiting for help with your bsod have a look at your event logs this will give you a little idea whats wrong go to>
control panel>all control panel items>performance and tools>advanced tools click on> view performance details in event log> when there click on event viewer (local) and have a look at the critical ,error,warning.information,audit services,reports. also go to >action center>click on> maintenance then click on >View Reliability history.

 

[penfold007]

I looked before posting and the only thing showing is the critical error warning saying previous shutdown was unexpected.

 

[brianzion]

I looked before posting and the only thing showing is the critical error warning saying previous shutdown was unexpected.

okey dokey i have not got the debugging tools to look at the dump files quick checks are updates for drivers, windows updates and bios updates.

 

[brianzion]

download this and try this from nirsoft it may show up something http://www.nirsoft.net/utils/blue_screen_view.html
can you give a bit more detail of what was running and what you were doing when the bsod happened and have you got external drives etc connected to the pc? have you run a virus check all these things will help

also run this (in admin mode)
Run cmd.exe with elevated previlliges (right click on cmd.exe as admin) and type:
sfc /scannow this will check your system files

 

[penfold007]

it says caused by driver:ntoskrnl.exe
caused by address:ntoskrnl.exe+23617b

the PC was idle at the time of the BSOD, although I had just unplugged my PDA, have a pen drive working as turbo boost(has been plugged in for months) but no other external drives.
have not had any windows updates for days

its just whipped through the scan with no problems found

 

[brianzion]

it says caused by driver:ntoskrnl.exe
caused by address:ntoskrnl.exe+23617b

the PC was idle at the time of the BSOD, although I had just unplugged my PDA, have a pen drive working as turbo boost(has been plugged in for months) but no other external drives.
have not had any windows updates for days

its just whipped through the scan with no problems found

ntoskrnl.exe - What is ntoskrnl.exe?
just checking what it is for you
"quote" ntoskrnl.exe is a critical process in the boot-up cycle of your computer although should never appear in WinTasks whilst under normal circumstances Note: ntoskrnl.exe can be altered by the w32.bolzano and variants. If this process appears in WinTasks, please update your virus definitions immediately

 

[brianzion]

did you eject the pda using disc eject? have you had any more bsod recently after posting the thread?

 

[brianzion]

we need the error log looked at that will help but i do not have the tools sorry i have asked for help from Jonathan_King so waiting for for reply

 

[Jonathan_King]

The dump blamed memory corruption, which is usually a bad driver, but sometimes bad RAM.

Just to make sure, do a RAM test: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Now looking through your list of 3rd-party drivers, I can see three potential causes of BSODs.

The first, is your outdated Realtek networking drivers. Install these ones: Realtek

Next, I see you have Gigabyte's Easy Saver program installed, another known cause of BSODs.

gdrv.sys     Thu Mar 12 23:17:32 2009 (49B9D04C)

Please uninstall that completely via Programs and Features.

Finally, I see you have an old Acronis True Image installed. Go ahead and update to 2010, or remove the program entirely. If you would like some tutorials for using Windows Backup instead, just ask.

snapman.sys  Thu Nov 22 03:19:58 2007
snpstd3.sys  Tue Apr 03 07:25:05 2007
tdrpman.sys  Mon Nov 12 08:35:28 2007
tifsfilt.sys Wed Aug 29 08:37:17 2007
timntr.sys   Wed Aug 29 08:13:12 2007

...Summary of the Dump:

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 06:19:40.130 2010 (UTC - 4:00)
System Uptime: 0 days 1:34:39.332
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_d
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

Now, that may seem like a lot of inconvenience for you. If you only had a single BSOD, I would try to forget about it. Everyone has gotten one sometime, usually not a problem unless it starts happening frequently. Heck, I myself didn't take action when my machine BSOD'd last week, until it happened twice in 3 days.

 

[brianzion]

thank you for your quick reply jonathan just waiting for reply from penfold007,champion

 

[penfold007]

OK will do what Jonathan has said, I've already tested the memory and its passed. So will update the necessary drivers mentioned.
I havn't had another BSOD since that one, so.....
sorry for not replying sooner, but we are in the middle of re-decorating at home and havn't had time to do anything.

 

[brianzion]

OK will do what Jonathan has said, I've already tested the memory and its passed. So will update the necessary drivers mentioned.
I havn't had another BSOD since that one, so.....
sorry for not replying sooner, but we are in the middle of re-decorating at home and havn't had time to do anything.

okey dokey keep the thread posted with news

 

[penfold007]

did another memtest and all fine, updated Realtek and acronis, and fingers crossed no more BSODs

 

[brianzion]

did another memtest and all fine, updated Realtek and acronis, and fingers crossed no more BSODs

great and big thanks to jonathan