W 7 crashes

J

Jeff

I have Windows 7 home premium 64 bit, 4GB RAM, which has been stable for
months. Then, in the past week I've had 2 (maybe 3) crashes, with a blue
screen notifying me that it was preparing a crash dump. When it restarts
W7 it asks me if I want it to search for a solution and though I say
yes, the popup disappears and nothing happens.

The first crash was such a rare event I just ignored it, but now I am
concerned. How does one explore the reason for repeated crashes?

Advice appreciated.

Jeff
Click to expand...
I used AppCrahView to view the dump report for the last crash on 7/10.
Here is what it says:
......................
Version=1
EventType=BlueScreen
EventTime=129547951205748010
ReportType=4
Consent=1
UploadTime=129547951301344189
ReportIdentifier=107ce006-ab20-11e0-bcdf-c15216744d3a
IntegratorReportIdentifier=071011-22604-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will
notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=9f
Sec[1].Key=BCP1
Sec[1].Value=0000000000000003
Sec[2].Key=BCP2
Sec[2].Value=FFFFFA8006034A00
Sec[3].Key=BCP3
Sec[3].Value=FFFFF80000BA2748
Sec[4].Key=BCP4
Sec[4].Value=FFFFFA8005A32880
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=768_1
File[0].CabName=071011-22604-01.dmp
File[0].Path=071011-22604-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\071011-22604-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-68250-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER-68250-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER7242.tmp.WERInternalMetadata.xml
File[2].Flags=589826
File[2].Type=5
File[2].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER7242.tmp.WERInternalMetadata.xml
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
.......................
There were several other crashed apps earlier with Event names such as
"Stopped responding and was closed" and "Stopped working"

Here is an example from 7/7:
...................
Version=1
EventType=AppHangB1
EventTime=129545340698622423
ReportType=3
Consent=1
ReportIdentifier=4c3c4d35-a8c0-11e0-b7d5-9a410e47ef3a
IntegratorReportIdentifier=4c3c4d36-a8c0-11e0-b7d5-9a410e47ef3a
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Sig[1].Name=Application Version
Sig[1].Value=10.0.6866.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4c6486a7
Sig[3].Name=Hang Signature
Sig[3].Value=f64e
Sig[4].Name=Hang Type
Sig[4].Value=256
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=f64e32c6ba53058a16a687ac0e89492d
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=f6e9
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=f6e92818e1d8afefeafac34228084708
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=f64e
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=f64e32c6ba53058a16a687ac0e89492d
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=f6e9
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=f6e92818e1d8afefeafac34228084708
UI[3]=Microsoft Word is not responding
UI[4]=Windows can check online for a solution. If you close the program,
you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Microsoft Office
2002\Office10\WINWORD.EXE
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files\Alwil Software\Avast5\snxhk.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.DLL
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\syswow64\GDI32.DLL
LoadedModule[12]=C:\Windows\syswow64\USER32.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\syswow64\OLE32.DLL
LoadedModule[16]=C:\Windows\system32\apphelp.dll
LoadedModule[17]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[18]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[19]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[20]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[21]=C:\Windows\system32\USERENV.dll
LoadedModule[22]=C:\Windows\system32\profapi.dll
LoadedModule[23]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[24]=C:\Windows\system32\MPR.dll
LoadedModule[25]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[26]=C:\Windows\system32\UxTheme.dll
LoadedModule[27]=C:\Windows\system32\WINMM.dll
LoadedModule[28]=C:\Windows\system32\samcli.dll
LoadedModule[29]=C:\Windows\system32\MSACM32.dll
LoadedModule[30]=C:\Windows\system32\VERSION.dll
LoadedModule[31]=C:\Windows\system32\sfc.dll
LoadedModule[32]=C:\Windows\system32\sfc_os.DLL
LoadedModule[33]=C:\Windows\system32\dwmapi.dll
LoadedModule[34]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[35]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[36]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[37]=C:\Windows\syswow64\urlmon.dll
LoadedModule[38]=C:\Windows\syswow64\iertutil.dll
LoadedModule[39]=C:\Windows\syswow64\WININET.dll
LoadedModule[40]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[41]=C:\Windows\system32\SHUNIMPL.DLL
LoadedModule[42]=C:\Windows\system32\IMM32.DLL
LoadedModule[43]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[44]=C:\Program Files (x86)\Common Files\Microsoft
Shared\office10\mso.dll
LoadedModule[45]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[46]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[47]=C:\Windows\system32\rsaenh.dll
LoadedModule[48]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[49]=C:\Program Files (x86)\Common Files\Microsoft
Shared\office10\riched20.dll
LoadedModule[50]=C:\Windows\system32\SXS.DLL
LoadedModule[51]=C:\Windows\system32\msi.dll
LoadedModule[52]=C:\Windows\system32\mscoree.dll
LoadedModule[53]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[54]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[56]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\16b68fcaff063835ae0ee348a1201f2a\mscorlib.ni.dll
LoadedModule[57]=C:\Program Files (x86)\Microsoft Corporation\Microsoft
Office Word 2007 Get Started Tab\MicrosoftOfficeWord2007GetStartedTab.dll
LoadedModule[58]=C:\Windows\assembly\GAC\Extensibility\7.0.3300.0__b03f5f7f11d50a3a\Extensibility.dll
LoadedModule[59]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[60]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[61]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[62]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[64]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[65]=C:\Windows\system32\ncrypt.dll
LoadedModule[66]=C:\Windows\system32\bcrypt.dll
LoadedModule[67]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[68]=C:\Windows\system32\GPAPI.dll
LoadedModule[69]=C:\Windows\system32\cryptnet.dll
LoadedModule[70]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[71]=C:\Windows\system32\SensApi.dll
LoadedModule[72]=C:\Windows\system32\Cabinet.dll
LoadedModule[73]=C:\Windows\system32\DEVRTL.dll
LoadedModule[74]=C:\Windows\assembly\GAC\office\12.0.0.0__71e9bce111e9429c\office.dll
LoadedModule[75]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[76]=C:\Windows\assembly\GAC\Microsoft.Office.Interop.Word\12.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Word.dll
LoadedModule[77]=C:\Windows\system32\wtsapi32.dll
LoadedModule[78]=C:\Windows\system32\WINSTA.dll
LoadedModule[79]=C:\Program Files (x86)\Microsoft Office
2002\Office10\msohev.dll
LoadedModule[80]=C:\Program Files (x86)\Common Files\Microsoft
Shared\Office10\usp10.dll
LoadedModule[81]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll
LoadedModule[82]=C:\Windows\system32\propsys.dll
LoadedModule[83]=C:\Windows\system32\ntmarta.dll
LoadedModule[84]=C:\Windows\system32\HLINK.dll
LoadedModule[85]=C:\PROGRA~2\COMMON~1\MICROS~1\WEBFOL~1\MSONSEXT.DLL
LoadedModule[86]=C:\PROGRA~2\COMMON~1\MICROS~1\WEBFOL~1\pkmws.dll
LoadedModule[87]=C:\Windows\system32\WSOCK32.dll
LoadedModule[88]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[89]=C:\Windows\syswow64\NSI.dll
LoadedModule[90]=C:\PROGRA~2\COMMON~1\MICROS~1\WEBFOL~1\MSVCP60.dll
LoadedModule[91]=C:\Windows\system32\Secur32.dll
LoadedModule[92]=C:\Windows\system32\dnsapi.DLL
LoadedModule[93]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[94]=C:\Windows\system32\WINNSI.DLL
LoadedModule[95]=C:\Windows\system32\RASAPI32.dll
LoadedModule[96]=C:\Windows\system32\rasman.dll
LoadedModule[97]=C:\Windows\system32\rtutils.dll
LoadedModule[98]=C:\Windows\system32\mswsock.dll
LoadedModule[99]=C:\Windows\System32\wshtcpip.dll
LoadedModule[100]=C:\Windows\system32\NLAapi.dll
LoadedModule[101]=C:\Windows\system32\rasadhlp.dll
LoadedModule[102]=C:\Windows\System32\wship6.dll
LoadedModule[103]=C:\Windows\System32\fwpuclnt.dll
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Word
AppPath=C:\Program Files (x86)\Microsoft Office 2002\Office10\WINWORD.EXE
ReportDescription=A problem caused this program to stop interacting with
Windows.
........................

Where do I go from here?
 
P

Paul

(e-mail address removed) wrote:

Response inline...
I have Windows 7 home premium 64 bit, 4GB RAM, which has been stable for
months. Then, in the past week I've had 2 (maybe 3) crashes, with a blue
screen notifying me that it was preparing a crash dump. When it restarts
W7 it asks me if I want it to search for a solution and though I say
yes, the popup disappears and nothing happens.

The first crash was such a rare event I just ignored it, but now I am
concerned. How does one explore the reason for repeated crashes?

Advice appreciated.

Jeff
Click to expand...
I used AppCrahView to view the dump report for the last crash on 7/10.
Here is what it says:
.....................
Version=1
EventType=BlueScreen
EventTime=129547951205748010
ReportType=4
Consent=1
UploadTime=129547951301344189
ReportIdentifier=107ce006-ab20-11e0-bcdf-c15216744d3a
IntegratorReportIdentifier=071011-22604-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will
notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=9f
Sec[1].Key=BCP1
Sec[1].Value=0000000000000003
Sec[2].Key=BCP2
Sec[2].Value=FFFFFA8006034A00
Sec[3].Key=BCP3
Sec[3].Value=FFFFF80000BA2748
Sec[4].Key=BCP4
Sec[4].Value=FFFFFA8005A32880
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=768_1
File[0].CabName=071011-22604-01.dmp
File[0].Path=071011-22604-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\071011-22604-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-68250-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER-68250-0.sysdata.xml

File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER7242.tmp.WERInternalMetadata.xml
File[2].Flags=589826
File[2].Type=5
File[2].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER7242.tmp.WERInternalMetadata.xml

FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
Click to expand...
If you use some other Nirsoft program, have you tried loading

C:\Windows\Minidump\071011-22604-01.dmp

and see if there is any stack trace or driver info ?

I interpret the above report to be

"Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE"

http://msdn.microsoft.com/en-us/library/ff559329(v=VS.85).aspx

and the trail stops cold right there. The "type 3" doesn't
tell us much.

"The device driver did not correctly set the IRP as "pending"
or complete the IRP."

From Wikipedia

"I/O request packets (IRPs) are structures that are used by
Windows Driver Model (WDM) and Windows NT drivers to communicate
with each other and the operating system. They are typically
created by the IO Manager on behalf of drivers."

As an amateur sleuth, "I want names". And would run any tool
that can give driver names. You need to work on the
"071011-22604-01.dmp" file, and beat a confession out of it :)
......................
There were several other crashed apps earlier with Event names such as
"Stopped responding and was closed" and "Stopped working"

Here is an example from 7/7:
..................
Version=1
EventType=AppHangB1
EventTime=129545340698622423
ReportType=3
Consent=1
ReportIdentifier=4c3c4d35-a8c0-11e0-b7d5-9a410e47ef3a
IntegratorReportIdentifier=4c3c4d36-a8c0-11e0-b7d5-9a410e47ef3a
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Click to expand...
<< laundry list snipped >>

I tried searching on "AppHangB1" and found precisely... nothing.

I was hoping the Hang Type field would mean something, but so
far can't find definitions.

I'd work on your first one, and hope the second one is related
some how, and both will clear up, when you fix the first one.
 
R

ray

You've checked RAM - that's a start. The next most likely culprits, in my
experience, would be the hard drive or the power supply. There are
utilities to check the hard drive. You could check the power supply, to
some extent, by booting a Live CD (there are many Linux and BSD ones
available).

How frequent are your crashes? If they are becoming, say, daily and the
system would boot and run a Linux Live CD for several days, that could
rule out the power supply.

Another option, of course, would be to reinstall the OS. If it continues
to crash then you'd most likely have a hardware problem of some sort.
 
J

Jeff

(e-mail address removed) wrote:

Response inline...
I have Windows 7 home premium 64 bit, 4GB RAM, which has been stable for
months. Then, in the past week I've had 2 (maybe 3) crashes, with a blue
screen notifying me that it was preparing a crash dump. When it restarts
W7 it asks me if I want it to search for a solution and though I say
yes, the popup disappears and nothing happens.

The first crash was such a rare event I just ignored it, but now I am
concerned. How does one explore the reason for repeated crashes?

Advice appreciated.

Jeff
Click to expand...
I used AppCrahView to view the dump report for the last crash on 7/10.
Here is what it says:
.....................
Version=1
EventType=BlueScreen
EventTime=129547951205748010
ReportType=4
Consent=1
UploadTime=129547951301344189
ReportIdentifier=107ce006-ab20-11e0-bcdf-c15216744d3a
IntegratorReportIdentifier=071011-22604-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will
notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=9f
Sec[1].Key=BCP1
Sec[1].Value=0000000000000003
Sec[2].Key=BCP2
Sec[2].Value=FFFFFA8006034A00
Sec[3].Key=BCP3
Sec[3].Value=FFFFF80000BA2748
Sec[4].Key=BCP4
Sec[4].Value=FFFFFA8005A32880
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=768_1
File[0].CabName=071011-22604-01.dmp
File[0].Path=071011-22604-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\071011-22604-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-68250-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER-68250-0.sysdata.xml

File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER7242.tmp.WERInternalMetadata.xml
File[2].Flags=589826
File[2].Type=5
File[2].Original.Path=C:\Users\JSM\AppData\Local\Temp\WER7242.tmp.WERInternalMetadata.xml

FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
Click to expand...
If you use some other Nirsoft program, have you tried loading

C:\Windows\Minidump\071011-22604-01.dmp

and see if there is any stack trace or driver info ?

I interpret the above report to be

"Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE"

http://msdn.microsoft.com/en-us/library/ff559329(v=VS.85).aspx

and the trail stops cold right there. The "type 3" doesn't
tell us much.

"The device driver did not correctly set the IRP as "pending"
or complete the IRP."

From Wikipedia

"I/O request packets (IRPs) are structures that are used by
Windows Driver Model (WDM) and Windows NT drivers to communicate
with each other and the operating system. They are typically
created by the IO Manager on behalf of drivers."

As an amateur sleuth, "I want names". And would run any tool
that can give driver names. You need to work on the
"071011-22604-01.dmp" file, and beat a confession out of it :)
......................
There were several other crashed apps earlier with Event names such as
"Stopped responding and was closed" and "Stopped working"

Here is an example from 7/7:
..................
Version=1
EventType=AppHangB1
EventTime=129545340698622423
ReportType=3
Consent=1
ReportIdentifier=4c3c4d35-a8c0-11e0-b7d5-9a410e47ef3a
IntegratorReportIdentifier=4c3c4d36-a8c0-11e0-b7d5-9a410e47ef3a
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Click to expand...
<< laundry list snipped >>

I tried searching on "AppHangB1" and found precisely... nothing.

I was hoping the Hang Type field would mean something, but so
far can't find definitions.

I'd work on your first one, and hope the second one is related
some how, and both will clear up, when you fix the first one.
Where do I go from here?
Click to expand...
Click to expand...
Thank you very much.

I am not suspicious of a new 32 bit video program I installed "Debut"
that does not seem to exit gracefully.
http://www.nchsoftware.com/capture/
 
J

Jeff

You've checked RAM - that's a start. The next most likely culprits, in my
experience, would be the hard drive or the power supply. There are
utilities to check the hard drive. You could check the power supply, to
some extent, by booting a Live CD (there are many Linux and BSD ones
available).

How frequent are your crashes? If they are becoming, say, daily and the
system would boot and run a Linux Live CD for several days, that could
rule out the power supply.

Another option, of course, would be to reinstall the OS. If it continues
to crash then you'd most likely have a hardware problem of some sort.
Click to expand...
Will check the HD next, but because this started recently I suspect the
culprit might be a new 32 bit video program I installed "Debut" that
does not seem to exit gracefully.
http://www.nchsoftware.com/capture/

Also, though I have 6 GB ram, I know that the built in video card has
shared memory and is the slowest thing on this laptop. So video may be a
problem here.

System was very stable until about 7-10 days ago.
 
G

Gene E. Bloch

You wouldn't have to wait if only you'd use Nirsoft's BlueScreenView,
as suggested.
Click to expand...
+1 on BSV.

It doesn't tell me everything, but that would be more than I can
understand anyway. It did point to a specific piece of software (from
Garmin) that was newly installed.

It is no help when there's no dump (it was time to state the obvious,
and besides, I had one such failure too, possibly also related to
Garmin).
 
J

Jeff

+1 on BSV.

It doesn't tell me everything, but that would be more than I can
understand anyway. It did point to a specific piece of software (from
Garmin) that was newly installed.

It is no help when there's no dump (it was time to state the obvious,
and besides, I had one such failure too, possibly also related to
Garmin).
Click to expand...
Don't have anything by Garmin.
 
U

Unk

Thank you.

Stopped the automatic restart and noticed that the kernel memory dump is
listed as
%SystemRoot%\MEMORY.DMP

Checked
""Windows Logs", click "System" and see if there are any "disk" errors".
All it had was benign informational items about the Service Control
Manager getting started.

Checked
""Windows Logs", click "Applications""
and only found 2 warnings, both for Google update which I know I am
blocking.

"BSOD can be caused by driver problems"
The only driver change I did was to install a W7 driver for the EasyCAP
USB device. Wonder if that might be the cause. Any way to find out
without uninstalling it?
http://www.amazon.com/EasyCAP-DC60-Creator-Capture-High-quality/dp/B002H3BSCM
I forget where I got the W7 64 bit drivers.

I'll check my drives but I think they will be fine too.

What else should I do, and thanks for all the expert help.

Jeff
Click to expand...
First, see Thip's post about "BlueScreenView" http://www.nirsoft.net/utils/blue_screen_view.html
See if it references the EasyCAP. If yes, Uninstall the EasyCAP driver and see if that fixes it.
If not, you can always install it again.

Reboot to the safe mode (Press F8 during bootup) and see if all is well.
If yes, Click Start, Run, and in the run box type "msconfig" without the quotes and click OK.
In the window that apperars check the "Startup" and "Services" for anything out of the ordinary.
Uncheck 1/2 the items and reboot. If it still BSOBs, recheck them and uncheck the other 1/2.
It'll be trial and error until you find the one that causes the BSOD.


Unk
 
U

Unk

(SNIP)
Click to expand...
Jeff,
You really shouldn't start a new thread for continuing this problem...
It makes it difficult to follow the line of progress and us leaving replies on dead threads.

Not picking, just advising.

Unk
 
J

Jeff

Jeff,
You really shouldn't start a new thread for continuing this problem...
It makes it difficult to follow the line of progress and us leaving replies on dead threads.

Not picking, just advising.

Unk
Click to expand...
Thanks.
 
J

Jeff

First, see Thip's post about "BlueScreenView" http://www.nirsoft.net/utils/blue_screen_view.html
See if it references the EasyCAP. If yes, Uninstall the EasyCAP driver and see if that fixes it.
If not, you can always install it again.

Reboot to the safe mode (Press F8 during bootup) and see if all is well.
If yes, Click Start, Run, and in the run box type "msconfig" without the quotes and click OK.
In the window that apperars check the "Startup" and "Services" for anything out of the ordinary.
Uncheck 1/2 the items and reboot. If it still BSOBs, recheck them and uncheck the other 1/2.
It'll be trial and error until you find the one that causes the BSOD.


Unk
Click to expand...
OK, I finally downloaded BlueScreenView and could see the minidump the
way it appears as a blue screen. (Until now I was using AppCrashView
which did not provide that view)

There were 4 crashes (in C:\Windows\Minidump), all in the last 10 days.
The problem in each was:

7/10: NETw5s64.sys DRIVER_POWER_STATE_FAILURE
7/5 : NETw5s64.sys DRIVER_POWER_STATE_FAILURE
6/29: ntoskrnl.exe DRIVER_POWER_STATE_FAILURE
6/29: ntoskrnl.exe DRIVER_POWER_STATE_FAILURE

Does this give additional insight as to the cause or does it just tell
us a crash happened?

I will take notes the next time a crash occurs (if it does) of exactly
what I was doing at the time. This system has been extremely stable and
I never saw a BSOD until the recent 4 so it probably is something I
installed recently.

Thank you all for helping this newbie. (Actually I am not a newbie in
computers, just never had to deal with BSODs).
 
P

Paul

OK, I finally downloaded BlueScreenView and could see the minidump the
way it appears as a blue screen. (Until now I was using AppCrashView
which did not provide that view)

There were 4 crashes (in C:\Windows\Minidump), all in the last 10 days.
The problem in each was:

7/10: NETw5s64.sys DRIVER_POWER_STATE_FAILURE
7/5 : NETw5s64.sys DRIVER_POWER_STATE_FAILURE
6/29: ntoskrnl.exe DRIVER_POWER_STATE_FAILURE
6/29: ntoskrnl.exe DRIVER_POWER_STATE_FAILURE

Does this give additional insight as to the cause or does it just tell
us a crash happened?

I will take notes the next time a crash occurs (if it does) of exactly
what I was doing at the time. This system has been extremely stable and
I never saw a BSOD until the recent 4 so it probably is something I
installed recently.

Thank you all for helping this newbie. (Actually I am not a newbie in
computers, just never had to deal with BSODs).
Click to expand...
Did you pop "NETw5s64.sys" into a search engine ? The communities.intel.com
thread seems to suggest it's related to an Intel Wifi or LAN thing.

http://communities.intel.com/thread/10055

"Microsoft has released a hotfix for BSODs very similar to these,
caused be defective power management code. You can read more over
at Ars Technica using the following link:

http://arstechnica.com/microsoft/ne...ails-windows-7-memory-leaks-hangs-freezes.ars
"

But the description in that arstechnica article isn't a good match.
Since the article predates the SP1 service pack for Windows 7, do
you happen to have SP1 installed ? If so, you might already have those
improvements baked into code.

Can you provide details on computer make and model ?

Is the above "Intel WiFi Link 5300 AGN" in the Intel thread
at all relevant ?

At the moment, I'm going to have to assume the four crashes
listed are all related, and the guilty party was only
successfully named in two of them. The kernel crashes could
be related to the same problem, but the kernel got the blame
rather than that driver. But it could be the same root cause.

In any case, start Googling NETw5s64.sys and see what shows up.

Paul
 
J

Jeff

Did you pop "NETw5s64.sys" into a search engine ? The communities.intel.com
thread seems to suggest it's related to an Intel Wifi or LAN thing.

http://communities.intel.com/thread/10055

"Microsoft has released a hotfix for BSODs very similar to these,
caused be defective power management code. You can read more over
at Ars Technica using the following link:

http://arstechnica.com/microsoft/ne...ails-windows-7-memory-leaks-hangs-freezes.ars

"

But the description in that arstechnica article isn't a good match.
Since the article predates the SP1 service pack for Windows 7, do
you happen to have SP1 installed ? If so, you might already have those
improvements baked into code.

Can you provide details on computer make and model ?

Is the above "Intel WiFi Link 5300 AGN" in the Intel thread
at all relevant ?

At the moment, I'm going to have to assume the four crashes
listed are all related, and the guilty party was only
successfully named in two of them. The kernel crashes could
be related to the same problem, but the kernel got the blame
rather than that driver. But it could be the same root cause.

In any case, start Googling NETw5s64.sys and see what shows up.

Paul
Click to expand...
Have not had any crashes since I wrote. So I'll hold off doing anything
till the next one - if it happens.

Thanks for the help.

Jeff
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows 7 crashes during browsing 3
My computer crashes when I go inprivate browsing. 3
Windows freezes or crashes when I change between programs 1
Explorer.exe crashes when opening a folder that contains an .mp4 file 0
SOLVED Laptop crashes (no BSOD) - please help me 3
PC crashes during sims4 normal play mode. 1
SOLVED BSOD and crashes 9
My computer crashes when watching Netflix, Youtube, and in Word 6

Top