Question
Applies to
355 views

Windows 7: Bluescreen upon wakeup

Hellraiser241 asked on
I have a Alien ware M15x laptop that runs Windows 7 home premium. I have been running into a problem where my computer will go into sleep mode and will often refuse to wake up. Only after multiple attempts will it start normally, and I am notified that and error has occurred and my computer had recovered from an unexpected shutdown

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033

Additional information about the problem:
  BCCode: d1
  BCP1: FFFFFA8408CCF00E
  BCP2: 0000000000000002
  BCP3: 0000000000000000
  BCP4: FFFFF880057A1AD7
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

Files that help describe the problem:
  C:\Windows\Minidump\101513-14414-01.dmp
  C:\Users\Owner\AppData\Local\Temp\WER-47393-0.sysdata.xml

I tried to troubleshoot the problem in Control panel -->Sytem and Security --> Review Your Computers Status.
And I am notified that there is an unknown device that does not have a driver.

If you do have and idea on how to fix this problem, please be explicit.


2 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Thank you!

Two attached DMP files, two bugchecks:


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

If we take a look at the call stack:

1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`02f1b2f8 fffff800`02ad3169 : 00000000`0000000a fffffa84`08ccf00e 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b300 fffff800`02ad1de0 : 00000000`00280180 00000000`00000001 00000000`000f4240 fffffa80`08ccf000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b440 fffff880`057a1ad7 : fffffa80`08ccf000 fffffa80`07e84870 00000000`00000005 00000041`0000003c : nt!KiPageFault+0x260 (TrapFrame @ fffff880`02f1b440)
fffff880`02f1b5d0 fffffa80`08ccf000 : fffffa80`07e84870 00000000`00000005 00000041`0000003c 00000000`0000004c : netw5v64+0xfaad7
fffff880`02f1b5d8 fffffa80`07e84870 : 00000000`00000005 00000041`0000003c 00000000`0000004c 00000000`0000005e : 0xfffffa80`08ccf000
fffff880`02f1b5e0 00000000`00000005 : 00000041`0000003c 00000000`0000004c 00000000`0000005e 0000003f`0000003a : 0xfffffa80`07e84870
fffff880`02f1b5e8 00000041`0000003c : 00000000`0000004c 00000000`0000005e 0000003f`0000003a fffffa84`08ccf00e : 0x5
fffff880`02f1b5f0 00000000`0000004c : 00000000`0000005e 0000003f`0000003a fffffa84`08ccf00e 00000000`0000005e : 0x41`0000003c
fffff880`02f1b5f8 00000000`0000005e : 0000003f`0000003a fffffa84`08ccf00e 00000000`0000005e fffffa80`08ccf000 : 0x4c
fffff880`02f1b600 0000003f`0000003a : fffffa84`08ccf00e 00000000`0000005e fffffa80`08ccf000 00000026`2a2f3538 : 0x5e
fffff880`02f1b608 fffffa84`08ccf00e : 00000000`0000005e fffffa80`08ccf000 00000026`2a2f3538 00000026`00000021 : 0x3f`0000003a
fffff880`02f1b610 00000000`0000005e : fffffa80`08ccf000 00000026`2a2f3538 00000026`00000021 0000003c`00000032 : 0xfffffa84`08ccf00e
fffff880`02f1b618 fffffa80`08ccf000 : 00000026`2a2f3538 00000026`00000021 0000003c`00000032 00000000`00000044 : 0x5e
fffff880`02f1b620 00000026`2a2f3538 : 00000026`00000021 0000003c`00000032 00000000`00000044 fffffa80`079ce000 : 0xfffffa80`08ccf000
fffff880`02f1b628 00000026`00000021 : 0000003c`00000032 00000000`00000044 fffffa80`079ce000 00000000`00000810 : 0x26`2a2f3538
fffff880`02f1b630 0000003c`00000032 : 00000000`00000044 fffffa80`079ce000 00000000`00000810 00000000`0000005e : 0x26`00000021
fffff880`02f1b638 00000000`00000044 : fffffa80`079ce000 00000000`00000810 00000000`0000005e 00000000`000007ff : 0x3c`00000032
fffff880`02f1b640 fffffa80`079ce000 : 00000000`00000810 00000000`0000005e 00000000`000007ff ffff0024`282d3336 : 0x44
fffff880`02f1b648 00000000`00000810 : 00000000`0000005e 00000000`000007ff ffff0024`282d3336 00000027`00000022 : 0xfffffa80`079ce000
fffff880`02f1b650 00000000`0000005e : 00000000`000007ff ffff0024`282d3336 00000027`00000022 0000003d`00000000 : 0x810
fffff880`02f1b658 00000000`000007ff : ffff0024`282d3336 00000027`00000022 0000003d`00000000 00000000`00000044 : 0x5e
fffff880`02f1b660 ffff0024`282d3336 : 00000027`00000022 0000003d`00000000 00000000`00000044 00000000`00000002 : 0x7ff
fffff880`02f1b668 00000027`00000022 : 0000003d`00000000 00000000`00000044 00000000`00000002 fffffa80`08c014e0 : 0xffff0024`282d3336
fffff880`02f1b670 0000003d`00000000 : 00000000`00000044 00000000`00000002 fffffa80`08c014e0 00000000`00000002 : 0x27`00000022
fffff880`02f1b678 00000000`00000044 : 00000000`00000002 fffffa80`08c014e0 00000000`00000002 fffffa80`08ccf2ce : 0x3d`00000000
fffff880`02f1b680 00000000`00000002 : fffffa80`08c014e0 00000000`00000002 fffffa80`08ccf2ce 00000000`0000001a : 0x44
fffff880`02f1b688 fffffa80`08c014e0 : 00000000`00000002 fffffa80`08ccf2ce 00000000`0000001a fffffa80`08c0cbb0 : 0x2
fffff880`02f1b690 00000000`00000002 : fffffa80`08ccf2ce 00000000`0000001a fffffa80`08c0cbb0 00000000`00000000 : 0xfffffa80`08c014e0
fffff880`02f1b698 fffffa80`08ccf2ce : 00000000`0000001a fffffa80`08c0cbb0 00000000`00000000 fffff880`014af845 : 0x2
fffff880`02f1b6a0 00000000`0000001a : fffffa80`08c0cbb0 00000000`00000000 fffff880`014af845 fffffa80`08ccf000 : 0xfffffa80`08ccf2ce
fffff880`02f1b6a8 fffffa80`08c0cbb0 : 00000000`00000000 fffff880`014af845 fffffa80`08ccf000 fffffa80`08ccf000 : 0x1a
fffff880`02f1b6b0 00000000`00000000 : fffff880`014af845 fffffa80`08ccf000 fffffa80`08ccf000 00000000`32746e49 : 0xfffffa80`08c0cbb0


From the above, we can see that we have a netw5v64.sys call directly before the bugcheck. This is the
Intel Wireless WiFi Link Driver.

-------------------------------------

DRIVER_POWER_STATE_FAILURE (9f)

This bug check indicates that the driver is in an inconsistent or invalid power state.

If we run an !irp on the 4th parameter of the bugcheck (blocked IRP address), we get the following:

>[ 16, 2]   0 e1 fffffa80084a6050 00000000 fffff80002cd3200-fffffa8007714400 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
 \Driver\netw5v64    nt!PopSystemIrpCompletion


^^ We can again see multiple instances of the Intel Wireless WiFi Link Driver.

Overall, in network related crashes like this, they are usually caused by one of two things:

1. Driver itself needs to be updated, which in this case you'd check Dell's website as you have an Alienware - http://www.dell.com/support/drivers/us/en/19/DriversHome/ShowProductSelector

If Dell's site reports the latest, try Intel's website - http://downloadcenter.intel.com/Default.aspx

2. 3rd party antivirus or firewall software causing conflicts and or corruption. It does not appear you have any security software installed, do you?

Regards,

Patrick
Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi,

In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where DMP files are located, here's how to get to them:

 1.    Navigate to the %systemroot%\Minidump folder.
 2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
 3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

If you are going to use Skydrive but don't know how to upload to it, please visit the following:

http://www.wikihow.com/Use-SkyDrive

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

If your computer is not generating DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history


progress