Forums » Technology » Hardware & Software - PC » First BSOD ever!


Topic Options
Rate This Topic
Hop to:
#3507062 - 01/30/12 07:22 AM First BSOD ever!
Flyboy Online   content
Senior Member

Registered: 11/29/06
Posts: 3015
Loc: England, UK
I've had this laptop now for roughly 2 years and 4 months and have NEVER, until now, had a blue screen/reboot.

I was just in my Yahoo! e-mail account and I hit the empty trash button and it seemed to happen then, might just have been a pure coincidence. I got a blue screen and it said something about it was shutting down the computer to try and prevent any data deletion. I think it said something about the cause being 'net32.dll' or 'netw32.dll' or something?

Anyhow, luckily just a few seconds before I had in fact saved what I was doing. The computer restarted, blah, blah, and I went back to what I was doing. I just did a Windows Update out of a bit of a panic.

I haven't had the dreaded BSOD for years, and never once before with Windows 7, and I've done what I was doing at the time of the crash a thousand times before. I just wondered if there was anything possibly to worry about? I'm hoping this was just a freakish one-off, but I have that piece of doubt in my mind now... you know how it is.

Thanks for any replies.

Top
#3507097 - 01/30/12 08:12 AM Re: First BSOD ever! [Re: Flyboy]
SkateZilla Offline
Skate Zilla HD Studios
Hotshot

Registered: 11/24/04
Posts: 8120
Loc: Virginia Beach, VA
post mini-dump file if you can, but.... net32.dll is part of the .net system....
_________________________
Skate Zilla

Chevron 11 (Born Feb. 2012)
Cooler Master HAF 922(Mesh Side), 700W OCZ, Windows 7 Pro, Windows 8 Beta
ASRock Fatal1ty 990FX Pro, Corsair H100 Water Cooled AMD FX-8120@4.0 GHz, 16GB G.SKILL Sniper @ DDR1600, WD 1.5TB Black
Sapphire RadeonHD 7950@1.0 GHz Core/6GHz Mem., ASUS VS248H-P 24" LED x 3, 5760 x 1080 Eyefinity,
Creative XFi Fata1ity Platinum Champion, Intensity Pro 10-Bit HDMI Video Recording, Ceton InfiniTV 4 PCIe


Skate Zilla HD Studios On Facebook

Top
#3507196 - 01/30/12 10:07 AM Re: First BSOD ever! [Re: Flyboy]
Flyboy Online   content
Senior Member

Registered: 11/29/06
Posts: 3015
Loc: England, UK
Where is the mini-dump saved? So if it was the net32.dll, it should be nothing to worry about?

Top
#3507207 - 01/30/12 10:15 AM Re: First BSOD ever! [Re: Flyboy]
SkateZilla Offline
Skate Zilla HD Studios
Hotshot

Registered: 11/24/04
Posts: 8120
Loc: Virginia Beach, VA
Windows 7 is: C:\Windows\Minidump\xxxxxxxxxxxx.dmp

the feature has to be configured to save the .dmp files. so if they arent there, then the feature hasnt been enabled.
_________________________
Skate Zilla

Chevron 11 (Born Feb. 2012)
Cooler Master HAF 922(Mesh Side), 700W OCZ, Windows 7 Pro, Windows 8 Beta
ASRock Fatal1ty 990FX Pro, Corsair H100 Water Cooled AMD FX-8120@4.0 GHz, 16GB G.SKILL Sniper @ DDR1600, WD 1.5TB Black
Sapphire RadeonHD 7950@1.0 GHz Core/6GHz Mem., ASUS VS248H-P 24" LED x 3, 5760 x 1080 Eyefinity,
Creative XFi Fata1ity Platinum Champion, Intensity Pro 10-Bit HDMI Video Recording, Ceton InfiniTV 4 PCIe


Skate Zilla HD Studios On Facebook

Top
#3507236 - 01/30/12 11:04 AM Re: First BSOD ever! [Re: Flyboy]
Bib4Tuna Offline
Member

Registered: 04/29/04
Posts: 1276
Loc: NC, USA

Nice little app to analyze Windows crash dumps:

http://www.resplendence.com/whocrashed
_________________________
"Hello. It's me, Jesus. I'm calling you from The Matrix."

Top
#3507817 - 01/31/12 04:37 AM Re: First BSOD ever! [Re: Flyboy]
Flyboy Online   content
Senior Member

Registered: 11/29/06
Posts: 3015
Loc: England, UK
SkateZilla - Thanks for pointing me where to look.

Bib4Tuna - Thanks for suggesting that 'WhoCrashed' program.

I downloaded and installed that 'WhoCrashed' program and let it analyze my crash dump. The crash was actually caused by the 'netw5v32.sys' file, an Intel Wireless WiFi Link Driver.


Quote:
Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 30/01/2012 14:45:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013012-30966-01.dmp
This was probably caused by the following module: netw5v32.sys (netw5v32+0x6BD54)
Bugcheck code: 0xD1 (0x64, 0x2, 0x0, 0xFFFFFFFF926A0D54)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netw5v32.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netw5v32.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5v32.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Mon 30/01/2012 14:45:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netw5v32.sys (netw5v32+0x6BD54)
Bugcheck code: 0xD1 (0x64, 0x2, 0x0, 0xFFFFFFFF926A0D54)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netw5v32.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netw5v32.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5v32.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



So I don't think there is too much here to worry about. I'm pleased that it was only my Wi-Fi Driver and I didn't lose anything. Obviously if it happens again then I'll look into upgrading the driver or whatever, but for now I'll leave it as this has only happened once in over 2 years.

Thanks guys!

Top
Topic Options
Rate This Topic
Hop to:


Forum Use Agreement | Privacy Statement | SimHQ Staff
Copyright 1997-2012, SimHQ Inc. All Rights Reserved.