BSOD problem

[cathymiseta]

I posted on another thread but didn't attach the dump files. I had to do a bunch of permission things to get it to work, but I think it's all here now. Please let me know if you can help me. Thanks.

Oh, and here's a copy/paste of the "problem signature"

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7600.2.0.0.768.3[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 9f[/FONT]
[FONT=&quot] BCP1: 0000000000000003[/FONT]
[FONT=&quot] BCP2: FFFFFA8006E47060[/FONT]
[FONT=&quot] BCP3: FFFFF80000B9C518[/FONT]
[FONT=&quot] BCP4: FFFFFA8004DF4C10[/FONT]
[FONT=&quot] OS Version: 6_1_7600[/FONT]
[FONT=&quot] Service Pack: 0_0[/FONT]
[FONT=&quot] Product: 768_1[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\040110-43680-01.dmp[/FONT]
[FONT=&quot] C:\Users\Miseta\AppData\Local\Temp\WER-72649-0.sysdata.xml[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/FONT][FONT=&quot][/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]C:\Windows\system32\en-US\erofflps.txt[/FONT][FONT=&quot][/FONT]

 

[zigzag3143]

I posted on another thread but didn't attach the dump files. I had to do a bunch of permission things to get it to work, but I think it's all here now. Please let me know if you can help me. Thanks.

Oh, and here's a copy/paste of the "problem signature"

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7600.2.0.0.768.3[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 9f[/FONT]
[FONT=&quot] BCP1: 0000000000000003[/FONT]
[FONT=&quot] BCP2: FFFFFA8006E47060[/FONT]
[FONT=&quot] BCP3: FFFFF80000B9C518[/FONT]
[FONT=&quot] BCP4: FFFFFA8004DF4C10[/FONT]
[FONT=&quot] OS Version: 6_1_7600[/FONT]
[FONT=&quot] Service Pack: 0_0[/FONT]
[FONT=&quot] Product: 768_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\040110-43680-01.dmp[/FONT]
[FONT=&quot] C:\Users\Miseta\AppData\Local\Temp\WER-72649-0.sysdata.xml[/FONT]

[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/FONT]

[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot]C:\Windows\system32\en-US\erofflps.txt[/FONT]

All of these crashes were identical which is a good thing. They were all caused by a device driver. The bad news is they dont tell us which one.

Because they dont I would
run a system file check to verify and repair your system files and drivers.
to do that type cmd in search>right click and run as admin>sfc /scannow note the space between sfc and "/"

If this passes with no errors we can get more aggressive by using driver verifier.

010810-23649-01.dmp    1/8/2010 7:05:50 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`06c70060    fffff800`00ba2748    fffffa80`06a02570    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\010810-23649-01.dmp    1    15    7600    
011310-19063-01.dmp    1/13/2010 9:49:38 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05157060    fffff800`00b9c518    fffffa80`089fdc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-19063-01.dmp    1    15    7600    
012110-17238-01.dmp    1/21/2010 6:22:40 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`04fde060    fffff800`00b9c518    fffffa80`09b2b6a0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\012110-17238-01.dmp    1    15    7600    
020510-17690-01.dmp    2/5/2010 8:04:14 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`06aec060    fffff800`00ba2748    fffffa80`08898650    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\020510-17690-01.dmp    1    15    7600    
021710-44756-01.dmp    2/17/2010 7:54:06 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`06e55440    fffff800`00b9c518    fffffa80`0a2ef2b0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\021710-44756-01.dmp    1    15    7600    
022210-54506-01.dmp    2/22/2010 7:21:18 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`04ff8060    fffff800`00b9c518    fffffa80`091ba660    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\022210-54506-01.dmp    1    15    7600    
030410-39624-01.dmp    3/4/2010 9:38:18 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0706e060    fffff800`00b9c518    fffffa80`07668010    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\030410-39624-01.dmp    1    15    7600    
032810-50279-01.dmp    3/28/2010 12:19:58 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`07e87060    fffff800`00b9c518    fffffa80`0767d4b0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\032810-50279-01.dmp    1    15    7600    
040110-43680-01.dmp    4/1/2010 1:35:34 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`06e47060    fffff800`00b9c518    fffffa80`04df4c10    USBPORT.SYS    USBPORT.SYS+223c4                    x64        C:\Users\K\Desktop\Minidump\040110-43680-01.dmp    1    15    7600

 

[cathymiseta]

Thanks for taking the time to look at that. I did the scan as you indicated and the result was "Windows Resource Protection did not find any integrity violations." I don't have too many peripherals attached to this computer, just a small Dymo label printer and a USB wireless adapter. I wonder if it's the driver for one of those items?

I came into the room this morning and discovered that a shutdown had occurred yet again. I'm concerned about losing data and just the wear and tear of having this happen several times a week. Is there anything else I might be able to do? Should I just shut the computer down correctly when I know I'm not going to be using it? Or maybe instead of a shutdown, I could try disconnecting the peripherals I mentioned, to see if that solves it?

Thanks,

Cathy Miseta

 

[zigzag3143]

Thanks for taking the time to look at that. I did the scan as you indicated and the result was "Windows Resource Protection did not find any integrity violations." I don't have too many peripherals attached to this computer, just a small Dymo label printer and a USB wireless adapter. I wonder if it's the driver for one of those items?

I came into the room this morning and discovered that a shutdown had occurred yet again. I'm concerned about losing data and just the wear and tear of having this happen several times a week. Is there anything else I might be able to do? Should I just shut the computer down correctly when I know I'm not going to be using it? Or maybe instead of a shutdown, I could try disconnecting the peripherals I mentioned, to see if that solves it?

Thanks,

Cathy Miseta

Cathy

Certainly a work around would be to shut the computer down, but I think we really should figure out why they are happening.

There are several more things we can do to diagnose them.

1-you can go into the system control panel (start>control panels>system>advanced>startup and recovery>uncheck auto restart.
that way it will not reboot every time and will allow you to view log files.

2-We can use event viewer (type eventvwr in search) by going to windows log>application tab.
You need to look for critical errors (they have red in the left hand column) that say something relevant to the problem (like app hang, or app crash<reboot, etc)

When you find them not the event ID and source code and relay them to us.

3-If nothing above helps we can get more agressive and use driver verifier. Before you do you should have a restore point and backup (just in case) and the win 7 dvd (make sure you can boot from it)

4-reinstall your USB wifi driver just in case

Let us know if you need help

Ken

 

[DocBrown]

Cathy, How about some computer specs ? Desktop or Laptop ? What about Power Management settings ? Hibernation ? Several things to investigate yet.

 

[DT Roberts]

This seems just like the one we're currently working on here: http://www.sevenforums.com/crashes-debugging/75031-crashes-64bit.html

They're likely related. Do you remember installing any updates recently? Also, I am curious about your system specs as well. Also, please follow the instructions here, only running option #2: System Information Collection - Windows Live