BSOD watching movies or browsing internet, error 0x0000000a

[DarKAngeL399]

Hello everyone ! I have these BSOD more than 3 times per day in the last three or four months and is getting really annoying. Can you please help me and tell me where the problem is ? I uploaded the dump files. Thank you!

 

[koolkat77]

Welcome to the Forum.

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!:-

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

RTSTOR64.SYS Wed Mar 26 09:03:05 2008 (47E9BCE9)

Realtek Card reader
Driver Reference Table - RTSTOR64.SYS

SynTP.sys Fri Apr 25 22:18:35 2008 (4812045B)

Synaptic Touch Pad Driver
Driver Reference Table - SynTP.sys

VSTCNXT6.SYS Thu Oct 16 06:52:22 2008 (48F69046)

Conexant SoftK56 Modem Driver
Driver Reference Table - VSTCNXT6.SYS

VSTAZL6.SYS Thu Oct 16 06:53:42 2008 (48F69096)

Conexant SoftK56 Modem Driver
Driver Reference Table - VSTAZL6.SYS

VSTDPV6.SYS Thu Oct 16 06:57:45 2008 (48F69189)

Conexant SoftK56 Modem Driver
Driver Reference Table - VSTDPV6.SYS

netw5v64.sys Thu Mar 26 22:21:24 2009 (49CBAB84)

Intel Wireless WiFi Link Driver
Driver Reference Table - netw5v64.sys

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

dtsoftbus01.sys Thu Jan 13 14:15:01 2011 (4D2EB485)
Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Let us know the results.

BugCheck A, {0, 2, 0, fffff80002c0c477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c0a477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003207477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031fd477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003205477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c1a477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003205477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c1a477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031f3477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c1a477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031e9477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031f3488}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck D1, {8, 2, 0, fffff88006a14c03}
Probably caused by : netw5v64.sys ( netw5v64+5c03 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c08477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031f3477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003203477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003205477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003203477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c04477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c1a477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003201477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031f5477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c1e477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80003203477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031f3477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff800031fd477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {0, 2, 0, fffff80002c20477}
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[DarKAngeL399]

I performed a format and installed a clean win7 version a while ago after the BSOD occures. I thought that would help. Isn't that supposed to help ? I don't have a modem connected to the laptop... Thanks for the prompt responses!

 

[koolkat77]

You mean the bsods continue after a fresh install?

 

[DarKAngeL399]

Yes, they are ... before the fresh install some of them were DRIVER_IRQL, but now only these type of stop code and IRQL

 

[koolkat77]

Is it still a vanilla install or have you installed software?

 

[DarKAngeL399]

i installed updates from wind and some drivers from the producer webpage like that for synaptics, card reader ... can this be the problem ? i have to mention that i always did this type of formatting and driver installing. Sorry if my english is kinda bad. Thanks

 

[koolkat77]

Do you get BSOD in safe mode?

 

[DarKAngeL399]

I have to admit that i didn't do this sort of tests. I haven't tried to run the windows in safe mode. It takes a while to get BSOD, after the laptop's heating, i presume and i wasn't that patient.

 

[koolkat77]

Well. Take memtest according to the quote below.

Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If memtest comes clean, enable driver verifier.

Enable Driver Verifier to see if it catches any misbehaving driver: Driver Verifier - Enable and Disable

Take your time and post results.

 

[DarKAngeL399]

Ok, it will take a while. Thanks a lot! I will come back with the result.

 

[DarKAngeL399]

Hello!!! I installed one more time a clean version of windows and at first i didn't install any driver after. 2 days passed now without any BSOD and i think that was the problem. Now i installed only the important drivers. I hope i will not have this problem again. Thank you koolkat77 for your help! Have a good evening!

 

[koolkat77]

Thanks for the update.

Good luck!

 

[DarKAngeL399]

Hello again! I had today another 2 BSOD. I don't know what would it be now. In dump files says a file for NT Kernel&system i guess. I attached the files in this reply if you can help me understand them. Thanks in advance!

 

[koolkat77]

Update this driver: Driver Reference Table

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\USER\Downloads\SF_26-01-2014\012514-24117-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e486d0
Debug session time: Sat Jan 25 20:27:06.889 2014 (UTC + 6:00)
System Uptime: 0 days 5:20:32.777
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800031ed477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800031ed477, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb2100
GetUlongFromAddress: unable to read from fffff80002eb21c0
 0000000000000000 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`031ed477 448b08          mov     r9d,dword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TAG_NOT_DEFINED_c000000f:  FFFFF8000402DFB0
TRAP_FRAME:  fffff8000402b990 -- (.trap 0xfffff8000402b990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000044
rdx=0000000000000044 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031ed477 rsp=fffff8000402bb28 rbp=0000000000000000
 r8=0000000000000028  r9=0000000000000000 r10=00000000000fffff
r11=fffffa800558fea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`031ed477 448b08          mov     r9d,dword ptr [rax] ds:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002c7a129 to fffff80002c7ab80
STACK_TEXT:  
fffff800`0402b848 fffff800`02c7a129 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0402b850 fffff800`02c78da0 : fffffa80`0693d8e8 fffff800`0402ba18 00000000`00000001 fffffa80`04579cb0 : nt!KiBugCheckDispatch+0x69
fffff800`0402b990 fffff800`031ed477 : fffffa80`07120bf0 fffffa80`053cffbc fffff800`031ed524 fffffa80`04579cb0 : nt!KiPageFault+0x260
fffff800`0402bb28 fffff800`031ed524 : fffffa80`04579cb0 fffffa80`0558fea0 fffffa80`03e73320 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff800`0402bb40 fffff800`031f04fb : fffffa80`04579cb0 fffffa80`0558fea0 fffffa80`07120bf0 fffff880`0805d1c7 : hal!HalpDmaMapScatterTransfer+0x34
fffff800`0402bb90 fffff800`031f0472 : fffffa80`04579cb0 fffffa80`04579ca8 00000000`00000028 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff800`0402bc20 fffff800`031ef94f : 00000000`00000000 fffff800`031ed01e 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff800`0402bc60 fffff800`031efafd : fffffa80`050bc050 fffffa80`0558fea0 00000000`00000001 fffffa80`00000528 : hal!HalpAllocateAdapterCallback+0xc7
fffff800`0402bd00 fffff800`031f0156 : fffffa80`0558fea0 00000000`00000500 fffffa80`0558fe00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff800`0402bd30 fffff800`031ef71f : fffffa80`044b6660 00000000`000005f4 fffffa80`0558fea0 fffffa80`04be45d0 : hal!HalAllocateAdapterChannel+0x11a
fffff800`0402bd70 fffff880`01496600 : fffffa80`04c96dd0 fffffa80`0558fa50 00000000`000000a0 fffff880`08299f27 : hal!HalBuildScatterGatherList+0x2f3
fffff800`0402bde0 fffff880`08052b7d : fffffa80`050bc1a0 fffff880`08299b20 fffffa80`069a4220 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff800`0402be80 fffffa80`050bc1a0 : fffff880`08299b20 fffffa80`069a4220 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff800`0402be88 fffff880`08299b20 : fffffa80`069a4220 fffff780`00000014 00000000`00000000 000005f4`00000100 : 0xfffffa80`050bc1a0
fffff800`0402be90 fffffa80`069a4220 : fffff780`00000014 00000000`00000000 000005f4`00000100 00000000`00000000 : netw5v64+0x24cb20
fffff800`0402be98 fffff780`00000014 : 00000000`00000000 000005f4`00000100 00000000`00000000 fffff880`0805afb9 : 0xfffffa80`069a4220
fffff800`0402bea0 00000000`00000000 : 000005f4`00000100 00000000`00000000 fffff880`0805afb9 fffff880`08319f80 : 0xfffff780`00000014

STACK_COMMAND:  kb
FOLLOWUP_IP: 
netw5v64+5b7d
fffff880`08052b7d ??              ???
SYMBOL_STACK_INDEX:  c
SYMBOL_NAME:  netw5v64+5b7d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: netw5v64
IMAGE_NAME:  netw5v64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  49cbab84
FAILURE_BUCKET_ID:  X64_0xA_netw5v64+5b7d
BUCKET_ID:  X64_0xA_netw5v64+5b7d
Followup: MachineOwner
---------
0: kd> lmvm netw5v64
start             end                 module name
fffff880`0804d000 fffff880`08588000   netw5v64 T (no symbols)           
    Loaded symbol image file: netw5v64.sys
    Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
    Image name: netw5v64.sys
    Timestamp:        Thu Mar 26 22:21:24 2009 (49CBAB84)
    CheckSum:         00533DE3
    ImageSize:        0053B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[DarKAngeL399]

you mean wifi driver ?
LE: I installed the driver from the link. If i occur any bsod i will come back with informations. Thanks!