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

Need Help Diagnosing BSOD


  • Please log in to reply
5 replies to this topic

#1 dpitch40

dpitch40

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:08:47 PM

Posted 23 September 2009 - 09:26 PM

**Note: Right as I was posting this I noticed the typo in the thread title...apologies.

Hello all, I just discovered this helpful-looking site while Googling around for help ending my laptop's habit of crashing with BSODs. I am running Windows Vista Home Premium with SP1, on a Toshiba Satellite A305 laptop if that makes any difference.

So far I can't find any definite link between my actions and the causes of the crashes. They occur when I'm doing fairly unremarkable things on my computer like browsing the internet and listening to music, things that ordinarily don't cause any problems. As soon as I reboot, I can repeat whatever I was doing exactly without causing a crash. I can't think of anything major I did shortly before the crashes started, besides installing Skype and Ventrilo, which I uninstalled to see if it would help. (It didn't) I don't have any system restore points from before the crashes started (though I recently changed system restore to make backups every 5 days instead of 1 so I can go back farther).

Anyway, using a tutorial on this site I finally figured out how to crack open my crash logs. Oddly, the dumps from my latest several crashes seem to be missing; I think I may have rebooted too early after the crash for them to be saved or something, and will correct this in the future. The following is the debugger's translation of the log from the first recorded crash. (If more logs would be helpful I can post them; there are a total of 7 saved)

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000009850000007e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001e79463, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002043080
000009850000007e

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeAcquireSpinLockRaiseToDpc+13
fffff800`01e79463 f0480fba2900 lock bts qword ptr [rcx],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffffa601b72eb70 -- (.trap 0xfffffa601b72eb70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=000009850000007e
rdx=fffffa8004247a70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001e79463 rsp=fffffa601b72ed00 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000002 r10=00017e9723fb2a00
r11=fffffa601b72ee10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeAcquireSpinLockRaiseToDpc+0x13:
fffff800`01e79463 f0480fba2900 lock bts qword ptr [rcx],0 ds:00000985`0000007e=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001e6e3ee to fffff80001e6e650

STACK_TEXT:
fffffa60`1b72ea28 fffff800`01e6e3ee : 00000000`0000000a 00000985`0000007e 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`1b72ea30 fffff800`01e6d2cb : 00000000`00000001 fffffa80`03e11000 fffff800`01f8ef00 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`1b72eb70 fffff800`01e79463 : fffffa80`07991000 fffffa80`06edd8c0 fffffa80`0720e840 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`1b72ed00 fffffa60`02c70645 : fffffa60`047a7060 fffffa60`047a7000 00000000`037d2060 31d55ef1`00001000 : nt!KeAcquireSpinLockRaiseToDpc+0x13
fffffa60`1b72ed30 fffffa60`047a7060 : fffffa60`047a7000 00000000`037d2060 31d55ef1`00001000 00000000`00000000 : NETw4v64+0x66645
fffffa60`1b72ed38 fffffa60`047a7000 : 00000000`037d2060 31d55ef1`00001000 00000000`00000000 00001f80`00c20087 : 0xfffffa60`047a7060
fffffa60`1b72ed40 00000000`037d2060 : 31d55ef1`00001000 00000000`00000000 00001f80`00c20087 00000000`00000000 : 0xfffffa60`047a7000
fffffa60`1b72ed48 31d55ef1`00001000 : 00000000`00000000 00001f80`00c20087 00000000`00000000 fffffa80`07991040 : 0x37d2060
fffffa60`1b72ed50 00000000`00000000 : 00001f80`00c20087 00000000`00000000 fffffa80`07991040 00000000`00000000 : 0x31d55ef1`00001000


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw4v64+66645
fffffa60`02c70645 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: NETw4v64+66645

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw4v64

IMAGE_NAME: NETw4v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46fa5c47

FAILURE_BUCKET_ID: X64_0xA_NETw4v64+66645

BUCKET_ID: X64_0xA_NETw4v64+66645

Followup: MachineOwner
---------

I can't figure out much from this dump; the tutorial said that posting the log here was the next step. One thing I did notice from analyzing a few dumps is that the process name is different, so this isn't being caused by one bad application (I think). Any insights into the possible nature/cause of my BSOD problem are greatly appreciated.

Edited by dpitch40, 23 September 2009 - 09:27 PM.


BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,084 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:09:47 PM

Posted 30 September 2009 - 07:51 AM

Hi -

The bugcheck = 0xa = a driver accessed paged memory at a time it should not have (IRQL too high)

Update your Intel wifi driver - http://downloadcenter.intel.com/SearchResu...llation+Utility

Regards. . .

jcgriff2

.
Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#3 dpitch40

dpitch40
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:08:47 PM

Posted 30 September 2009 - 08:10 AM

Interesting. For the update utility, how do I check which chipset I have?

#4 dpitch40

dpitch40
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:08:47 PM

Posted 02 October 2009 - 09:48 AM

I followed this tutorial to try and figure out which chipset I have. It says to look for something like a 'memory controller hub', but I don't see that and am not sure which one it could be. I'm posting a screenshot of my list of system devices in case someone here has a better idea.

Posted Image

#5 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:09:47 PM

Posted 02 October 2009 - 10:53 AM

From what I can figure out from the Driver that is referenced in the Bugcheck Analysis you are running a 64Bit version of Windows Vista.

Your Wireless Drivers can be found here.

According to Toshiba that laptop series came with an Intel 3945ABG Wireless adapter installed in it. The link I gave you will put you right on the page for download. Download the first file referenced as it is executable and will automatically update your wireless drivers.

To answer your question as to which Chipset you have installed in your laptop, according to both Toshiba and your Device Manager you have a Mobile Intel® GM965 Express Chipset.

Hope this helps,
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#6 dpitch40

dpitch40
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:08:47 PM

Posted 23 October 2009 - 01:32 PM

Thanks--I guess I'll know if it worked if the crashes stop.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users