Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Meaning of BSOD for HP Elitebook 850


  • Please log in to reply
53 replies to this topic

#1 wizard44

wizard44

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 22 March 2015 - 05:14 PM

 Hey guys,

 

So my HP Elitebook 850 has been giving me quite a bit of issues with the past month or so, such as apparently shutting down when waking up, still running even while in "sleep" mode, and getting blue screens of death. I downloaded BlueScreenViewer in response to the BSOD that I received today. Below is the log that was generated in today's dump. Can someone tell me what is going on here? Is it because of a corrupt windows 8.1 installation?

 

 

 

==================================================
Dump File         : 032215-6687-01.dmp
Crash Time        : 3/22/2015 2:35:30 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : ffffd000`246a0000
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`60dd2c74
Caused By Driver  : WinUSB.sys
Caused By Address : WinUSB.sys+114cc74
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1509a0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\032215-6687-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 282,016
Dump File Time    : 3/22/2015 2:36:26 PM
==================================================

 



BC AdBot (Login to Remove)

 


#2 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 05:39 PM

According to the tool, the crash was

 

Caused By Driver  : WinUSB.sys

 

 

Info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff540283%28v=vs.85%29.aspx

 

Do you have any new USB devices plugged into the computer? I'm just guessing but if you want a more thorough analysis of the BSOD log, the actual C:\WINDOWS\Minidump\032215-6687-01.dmp file will provide people that know how to use WinDbg a more conclusive reason of what could be the issue. Good luck! I'll try to help where I can if you are able to attach the log to your post.



#3 wizard44

wizard44
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 22 March 2015 - 06:09 PM

Nope, I have no usb devices plugged into this computer. I cannot upload the actual dmp file, since it gives the message "you aren't permitted to upload this kind of file." How can I get a more complete log?



#4 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 06:16 PM

http://www.bleepingcomputer.com/submit-malware.php?channel=137

 

Go to the above link and try sending the file this way.



#5 wizard44

wizard44
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 22 March 2015 - 06:22 PM

Ok, I submitted the file. I don't know if this is relevant, but my wireless network adapter (which is the one that the laptop came with) sometimes isn't recognized by my laptop.



#6 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 06:42 PM

Ok, I submitted the file. I don't know if this is relevant, but my wireless network adapter (which is the one that the laptop came with) sometimes isn't recognized by my laptop.

 

I got it. The wireless adapter is something I'd look into as well as it appears in your BSOD log. I'll highlight/bold it below and attach the log for someone more knowledgeable to review but I do think it's a good chance the problem is related to your wireless driver by Intel.

 

 

BugCheck D1, {ffffd000246a0000, 2, 1, fffff80060dd2c74}

 
Unable to load image \SystemRoot\system32\DRIVERS\NETwbw02.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwbw02.sys
Probably caused by : NETwbw02.sys ( NETwbw02+1d2c74 )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd000246a0000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80060dd2c74, address which referenced memory
 
Debugging Details:
------------------
 
 
WRITE_ADDRESS: fffff80043f4cc60: Unable to get special pool info
fffff80043f4cc60: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffffd000246a0000 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
NETwbw02+1d2c74
fffff800`60dd2c74 660f7f49f0      movdqa  xmmword ptr [rcx-10h],xmm1
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0xD1
 
PROCESS_NAME:  wlanext.exe    (wlan = wireless lan)
 
LAST_CONTROL_TRANSFER:  from fffff80043de24e9 to fffff80043dd69a0
 
STACK_TEXT:  
ffffd000`24237a58 fffff800`43de24e9 : 00000000`0000000a ffffd000`246a0000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`24237a60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
 
 
STACK_COMMAND:  .bugcheck ; kb
 
FOLLOWUP_IP: 
NETwbw02+1d2c74
fffff800`60dd2c74 660f7f49f0      movdqa  xmmword ptr [rcx-10h],xmm1
 
SYMBOL_NAME:  NETwbw02+1d2c74
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: NETwbw02
 
IMAGE_NAME:  NETwbw02.sys     (Intel Wireless WiFi Link Adapter)
 
DEBUG_FLR_IMAGE_TIMESTAMP:  54327471
 
FAILURE_BUCKET_ID:  X64_0xD1_NETwbw02+1d2c74
 
BUCKET_ID:  X64_0xD1_NETwbw02+1d2c74
 
Followup: MachineOwner
---------
 
3: kd> lmvm NETwbw02
start             end                 module name
fffff800`60c00000 fffff800`60f7f000   NETwbw02 T (no symbols)           
    Loaded symbol image file: NETwbw02.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwbw02.sys
    Image name: NETwbw02.sys
    Timestamp:        Mon Oct 06 05:52:33 2014 (54327471)
    CheckSum:         003605FE
    ImageSize:        0037F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

 

A topic you may want to review as it looks like this person encountered the same issue here.

 

In the meantime though, I think it's safe to update your Intel Wireless Driver and see if that resolves any issues. I'm not good enough at WinDbg to find out which operating system you are running. All I can tell is that it's a 64 bit operating system. Let us know and I'll try to find the correct Wireless Driver for you

Attached Files


Edited by thisisu, 22 March 2015 - 06:46 PM.


#7 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 06:49 PM

 Is it because of a corrupt windows 8.1 installation?

 

 

I missed this, if you are on Windows 8.1, the Intel driver for your laptop is located here.



#8 wizard44

wizard44
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 22 March 2015 - 07:00 PM

I already installed this particular driver two weeks ago, and yet this happened? Would trying the whole process again really fix it?



#9 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 07:07 PM

Possibly, we don't know yet. Maybe the wireless hardware itself is what has gone bad. Driver is much easier to replace. What I would do is completely uninstall (or repair if that's an option) your Intel wireless driver from Programs and Features. It will probably appear as Intel ... Driver in the list. Reboot if prompted to. Then ensure that there is not a wireless driver installed by checking in the Device Manager. Then download and install the driver I linked above. Also, turn off sleep mode / hibernation is something I'd also recommend. These have often caused more harm than good.


Edited by thisisu, 22 March 2015 - 07:33 PM.


#10 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 22 March 2015 - 07:45 PM

Alternative driver and newer version than the one from HP's site: https://downloadcenter.intel.com/download/24681/Intel-PROSet-Wireless-Software-for-Bluetooth-technology-for-Windows-8-1-64-bit-WP-

 

Logging off for a while. Good luck :)


Edited by thisisu, 22 March 2015 - 10:05 PM.


#11 dinodod

dinodod

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Local time:12:26 PM

Posted 23 March 2015 - 01:49 PM

Try using WhoCrashed to analyze your BSOD better

 

 

Run a Chkdsk /r as well to see if there are any bad sectors

 

LOL, the driver you mentioned from HP says: 

Fixes an issue with causes a blue screen event to occur. :)  Really now?  LMAO

 

Intel has a driver if you want to try it:

https://downloadcenter.intel.com/download/24655/Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-8-


Essential Tools for safe computing

https://sites.google.com/site/dinodod/pc-standards

 

Please leave a comment on anything relative and help me expand on it.

 


#12 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 23 March 2015 - 02:12 PM

LOL, the driver you mentioned from HP says: 

Fixes an issue with causes a blue screen event to occur. :)  Really now?  LMAO

 

Haha

It also says:

Fixes an issue where the system does not connect properly to an ad hoc wireless network after the system resumes from sleep or hibernate mode.



#13 wizard44

wizard44
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 31 March 2015 - 02:49 PM

Ok, so I did everything you instructed me to, and I got a new BSOD weeks later. I have attached the dmp file to the previous link you gave me.



#14 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:26 PM

Posted 31 March 2015 - 03:58 PM

This one seems to suggest DirectX which is video related as the culprit.

 

 

 

2: kd> knL

 # Child-SP          RetAddr           Call Site
00 ffffd001`dc76c7a8 fffff801`a7dbc9ca nt!KeBugCheckEx
01 ffffd001`dc76c7b0 fffff801`a78179dd watchdog!WdLogEvent5_WdCriticalError+0xce
02 ffffd001`dc76c7f0 00000000`00000000 dxgmms1!VidSchiResetEngine+0x2f1

 

 

fffff801`a820b000 fffff801`a829f000   atikmpag   (deferred)   

 

 

So you have an AMD/ATI graphics card...

 

Try this driver for your video card: http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5405106&swItemId=ob_146034_1&swEnvOid=4158

 

Regards

Attached Files


Edited by thisisu, 31 March 2015 - 04:00 PM.


#15 wizard44

wizard44
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:10:26 AM

Posted 19 April 2015 - 08:46 PM

Installed the driver, and I got ANOTHER BSOD today. The dmp file is attached to the previous link used for the first two.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users