Navigation section

Windows 7 I am getting a BSOD only when the PC is asleep. Attached is the zip file as requested.

B

berniealen

New Member
Joined
Jan 26, 2013
Messages
4
I am getting a BSOD only when the PC is asleep. Attached is the zip file as requested. It is happening every night and today for the first time I saw it during the day (but only when the PC is in sleep mode).

Thank you.

Bernie
 


Attachments

Solution
usasma
Device manufacturer's submit drivers to Windows Update whenever they feel like it. For example, the ASACPI.sys file on my system dates from 2005 - and we see a lot of BSOD's due to it - but it's what Asus has uploaded to Windows Update.

The Update Driver function in Device Manager uses Windows Update.

While you can often get away with using older drivers - when you're having BSOD (and other) issues, you need to have the most updated drivers. The reason for this is that the more updated the drivers are, the more likely they are to have all bug's fixed.

The most likely place to get the most updated drivers is the device manufacturer's website. On occasion the device manufacturer won't make drivers available - so you're stuck using...
Sort by date Sort by votes
This device is disabled:
DW1501 Wireless-N WLAN Half-Mini Card PCI\VEN_14E4&DEV_4727&SUBSYS_00101028&REV_01\4&AA4FEAE&0&00E0 This device is disabled.
Click to expand...
Is this deliberate? If so, why?

Please re-enable it, update the drivers, then re-disabled it (if so desired).

The system hit a breakpoint and stopped (crashed). This isn't supposed to happen in code that most users can get their hands on. Is there anything special that you've done to the system that might have caused this? This appears to have started suddenly around 22 Jan 2013. Do you recall anything in particular that you did around that time?

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

LHidFilt.Sys Wed Jun 17 12:49:39 2009 (4A391EA3)
Logitech SetPoint HID Filter Driver
Link Removed

LMouFilt.Sys Wed Jun 17 12:49:43 2009 (4A391EA7)
Logitech SetPoint HID Filter Driver
Link Removed

motoandroid.sys Fri Jul 10 01:06:49 2009 (4A56CC69)
Relates to the attached phone's software
motoandroid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

nusb3hub.sys Mon Oct 26 10:19:44 2009 (4AE5B000)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2009/2010 version)
Link Removed

nusb3xhc.sys Mon Oct 26 10:19:48 2009 (4AE5B004)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2009/2010 version)
Link Removed

If the above steps don't fix the BSOD"s, please run Driver Verifier according to these instructions: Link Removed


Analysis:
The following is for informational purposes only.
Code: 
[FONT=lucida console]**************************Sat Jan 26 16:17:17.362 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012613-17378-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 9:36:32.208[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff80003490dd0, fffff880009f13f8, fffff880009f0c50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80003490dd0, The address that the exception occurred at
Arg3: fffff880009f13f8, Exception Record Address
Arg4: fffff880009f0c50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 25 22:32:36.315 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012613-20732-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 14:54:16.142[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff800034c0dd0, fffff8800ce7e3f8, fffff8800ce7dc50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff800034c0dd0, The address that the exception occurred at
Arg3: fffff8800ce7e3f8, Exception Record Address
Arg4: fffff8800ce7dc50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 23:30:48.158 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-33150-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 14:47:27.985[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff80003487dd0, fffff880009f13f8, fffff880009f0c50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80003487dd0, The address that the exception occurred at
Arg3: fffff880009f13f8, Exception Record Address
Arg4: fffff880009f0c50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 16:57:46.050 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-37143-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:27:29.878[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff8000348add0, fffff880087373f8, fffff88008736c50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8000348add0, The address that the exception occurred at
Arg3: fffff880087373f8, Exception Record Address
Arg4: fffff88008736c50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 23:57:56.392 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-20623-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 4:57:01.108[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff800034d2dd0, fffff88009ba53f8, fffff88009ba4c50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff800034d2dd0, The address that the exception occurred at
Arg3: fffff88009ba53f8, Exception Record Address
Arg4: fffff88009ba4c50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 14:41:40.402 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012213-20638-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]1 days 8:06:31.119[/B]
Probably caused by :[B]Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff80003490dd0, fffff8800be793f8, fffff8800be78c50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80003490dd0, The address that the exception occurred at
Arg3: fffff8800be793f8, Exception Record Address
Arg4: fffff8800be78c50, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70[/B]
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3392[/B]
  BIOS Version                  A06
  BIOS Release Date             10/17/2011
  Manufacturer                  Dell Inc.
  Product Name                  XPS 8300  
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[FONT=lucida console]**************************Sat Jan 26 16:17:17.362 2013 (UTC - 5:00)**************************
[COLOR=RED][B]LHidFilt.Sys                Wed Jun 17 12:49:39 2009 (4A391EA3)[/B][/COLOR]
[COLOR=RED][B]LMouFilt.Sys                Wed Jun 17 12:49:43 2009 (4A391EA7)[/B][/COLOR]
[COLOR=RED][B]motoandroid.sys             Fri Jul 10 01:06:49 2009 (4A56CC69)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
HCW85BDA.sys                Fri Sep 11 16:19:06 2009 (4AAAB0BA)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
[COLOR=RED][B]nusb3hub.sys                Mon Oct 26 10:19:44 2009 (4AE5B000)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Mon Oct 26 10:19:48 2009 (4AE5B004)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
pcdsrvc_x64.pkms            Sun May  2 23:01:16 2010 (4BDE3C7C)
k57nd60a.sys                Tue Jun  8 07:40:13 2010 (4C0E2C1D)
RTKVHD64.sys                Tue Jun 22 05:27:26 2010 (4C2081FE)
npf.sys                     Fri Jun 25 12:50:58 2010 (4C24DE72)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
AtihdW76.sys                Wed Nov 17 07:02:04 2010 (4CE3C43C)
rikvm_9EC60124.sys          Wed Mar 16 04:30:49 2011 (4D807539)
iaStor.sys                  Fri May 20 12:52:24 2011 (4DD69C48)
tmtdi.sys                   Wed Jun 29 06:26:34 2011 (4E0AFDDA)
tmeevw.sys                  Wed Jun 29 10:47:24 2011 (4E0B3AFC)
tmnciesc.sys                Mon Jul  4 00:07:42 2011 (4E113C8E)
Sftvollh.sys                Fri Sep 30 12:42:46 2011 (4E85F186)
Sftplaylh.sys               Fri Sep 30 12:43:05 2011 (4E85F199)
Sftfslh.sys                 Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftredirlh.sys              Fri Sep 30 12:43:14 2011 (4E85F1A2)
atikmpag.sys                Wed Nov  9 21:12:44 2011 (4EBB331C)
atikmdag.sys                Wed Nov  9 21:52:46 2011 (4EBB3C7E)
tmevtmgr.sys                Mon Sep 24 07:58:43 2012 (50604AF3)
tmcomm.sys                  Mon Sep 24 07:58:46 2012 (50604AF6)
tmactmon.sys                Mon Sep 24 07:58:59 2012 (50604B03)
[/FONT]
Link Removed
Link Removed
motoandroid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 


Upvote 0 Downvote
Thank you. I checked all the drivers in Driver Manager and they are all up-to-date (per Windows). The only one I have a problem with is the virtual MiniWiFi which I have disabled. I have also disabled the NECs. I use a logitech MX revolution keyboard and mouse and I have been using this before the crashes. The only thing I can think of is I got a passive USB splitter to use the same wireless keyboard and mouse between two computers and that did not work well, so I don't use it anymore (it may have come with a driver disk - I don't remember). The other concern I have is the whole Java 7 security scare in January and I'm not sure if that may be causing this. Appreciate your help. - Bernie

nusb3hub.sys Mon Oct 26 10:19:44 2009 (4AE5B000)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2009/2010 version)
Link Removed

nusb3xhc.sys Mon Oct 26 10:19:48 2009 (4AE5B004)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2009/2010 version)
Link Removed
 


Upvote 0 Downvote
Are you getting the drivers from windows update as I wouldn't recommend that at all. Go to the board manufactures site or do a search for updated drivers online.
 


Upvote 0 Downvote
Device manufacturer's submit drivers to Windows Update whenever they feel like it. For example, the ASACPI.sys file on my system dates from 2005 - and we see a lot of BSOD's due to it - but it's what Asus has uploaded to Windows Update.

The Update Driver function in Device Manager uses Windows Update.

While you can often get away with using older drivers - when you're having BSOD (and other) issues, you need to have the most updated drivers. The reason for this is that the more updated the drivers are, the more likely they are to have all bug's fixed.

The most likely place to get the most updated drivers is the device manufacturer's website. On occasion the device manufacturer won't make drivers available - so you're stuck using the PC manufacturer's website (there's an additional step with add-on cards that use other manufacturer's chipsets - those you check at the add-on card manufacturer's website). Finally, there are instances where the PC manufacturer or add-on card manufacturer makes modifications to the driver that are required for your system to function properly (or they contain features that you want to use). In that case you'll use those from the PC manufacturer/add-on card manufacturer.

Then, if all else fails, then there's the Update Driver function from Device Manager (aka Windows Update). I routinely use this for new computers - but never use it for those with problems.

I wouldn't worry about the java exploit scare for this. But if you're concerned, try a few of the free scans here: Link Removed to ensure that your system isn't infected.

Unfortunately the Dell site for your system only lists the 2009 drivers (packaged in Jan of 2011) - so you'll have to look for them on your own. You might want to start here: Renesas USB 3.0 drivers for Windows BUT I have not used this site myself so I have no idea of it's reliability.
 


Upvote 0 Downvote
Solution
You must log in or register to reply here.

Similar threads

trin
  • Solved
Windows 7 I am getting a bsod, please help
Replies
3
Views
2K
kemical
kemical
Back
Top