Before we get started.
Code:
Start Menu\Programs\[COLOR="Red"]DAEMON Tools[/COLOR] Lite Public:Start Menu\Programs\DAEMON Tools Lite Public
Daemon Tools/Alcohol is known cause of BSODs, you will have to find an alternative as there is no way around this.
Registry and SPTD problems | DAEMON Pro Help
How to remove sptd.sys from system
1. Uninstall Daemon Tools.
2. Download the
SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below
If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.
Update your network driver here.
https://downloadcenter.intel.com/Default.aspx
Your network card if you didn't know is the
Intel Wireless WiFi Link 4965AGN
Here's my analysis for anyone interested:
Code:
BugCheck A, {[COLOR="Blue"]0[/COLOR], [COLOR="Red"]2[/COLOR], 0, fffff80003005477}
This bugcheck indicates pageable memory has been access at an IRQL too high.
The address being referenced is 0x0 which is a reserved user mode address, the first usable address is 0x00010000.
So the crash happened because the instruction failed to access a memory address, normally this would result in a page fault at an IRQL lower than 2 but not page faults are allowed to happen at an IRQL of 2 or higher.
The address attempting to be accessed was invalid anyway so even if the IRQL was at 0 it would still crash.
To understand this we need to know what an interrupt is, it's a type of asynchronous event which interrupts the processor's main flow of operation for a more important matter.
With this said we need to know what an IRQL is.
So what's an IRQL?
An IRQL is an Interrupt Request Level which is split into 15 levels on 64 bit Operating Systems and 31 on 32 bit Operating Systems.
They are levels of priority, the higher the level the more priority it has over the lower levels.
For example, you get two interrupts that need servicing, a disk I/O and a GUI window that needs drawing for an application, obviously the disk I/O needs servicing first so it has a higher IRQL.
Now the IRQL cannot be lowered on that processor until the IRQ at that level has been serviced, then it lowers to the next level at which an IRQ has been waiting.
An interrupt can occur whilst an interrupt is being serviced, which then halts the current IRQ to service the higher one.
Here's a good
blog on IRQLs if you're interested.
Now because page faults can only be serviced at IRQL 1 or below the IRQL cannot lower from 2 as it hasn't been serviced.
This results in a bugcheck.
Code:
1: kd> [COLOR="Green"]knL[/COLOR]
# Child-SP RetAddr Call Site
00 fffff880`0d249668 fffff800`02a93169 [COLOR="Red"]nt!KeBugCheckEx[/COLOR] <-- BSOD
01 fffff880`0d249670 fffff800`02a91de0 [COLOR="red"]nt!KiBugCheckDispatch+0x69[/COLOR]
02 fffff880`0d2497b0 fffff800`03005477 [COLOR="red"]nt!KiPageFault+0x260[/COLOR] <-- Page fault
03 fffff880`0d249948 fffff800`03005524 hal!HalpDmaNextContiguousPiece+0x103
04 fffff880`0d249960 fffff800`030084fb hal!HalpDmaMapScatterTransfer+0x34
05 fffff880`0d2499b0 fffff800`03008472 hal!HalpMapTransfer+0x7b
06 fffff880`0d249a40 fffff800`0300794f hal!IoMapTransfer+0x8e
07 fffff880`0d249a80 fffff800`03007afd hal!HalpAllocateAdapterCallback+0xc7
08 fffff880`0d249b20 fffff800`03008156 hal!IoFreeAdapterChannel+0x109
09 fffff880`0d249b50 fffff800`0300771f hal!HalAllocateAdapterChannel+0x11a
0a fffff880`0d249b90 fffff880`016db600 hal!HalBuildScatterGatherList+0x2f3 <-- hardware abstraction routines
0b fffff880`0d249c00 fffff880`06a67b7d [COLOR="Blue"]ndis!NdisMAllocateNetBufferSGList+0x110[/COLOR] <-- network buffer allocation routine
0c fffff880`0d249ca0 fffffa80`084aa1a0 [COLOR="Red"]netw5v64+0x5b7d[/COLOR] <-- network driver stated above
0d fffff880`0d249ca8 fffff880`06caeb20 0xfffffa80`084aa1a0
0e fffff880`0d249cb0 fffffa80`0720e7e0 [COLOR="red"]netw5v64+0x24cb20[/COLOR] <-- network driver stated above
0f fffff880`0d249cb8 fffff780`00000014 0xfffffa80`0720e7e0
10 fffff880`0d249cc0 00000000`00000000 0xfffff780`00000014
With all that said lets take a look at your network driver information.
Code:
1: kd> [COLOR="Green"]lmvm netw5v64[/COLOR]
start end module name
fffff880`06a62000 fffff880`06f9d000 netw5v64 T (no symbols)
Loaded symbol image file: netw5v64.sys
Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
Image name: netw5v64.sys
Timestamp: [COLOR="Red"]Thu Mar 26 16:21:24 2009[/COLOR] (49CBAB84)
CheckSum: 00533DE3
ImageSize: 0053B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
It's out of date, as suggested above update the driver.
