Drivers cause BSOD {URGENT}

Good day
About 2 years ago I bought this laptop for a really good deal and i was impressed with the performance i got with it. Its quite a powerful and quality piece of tech.
There are some drawbacks...
In the two years ive had it ive formatted the laptop twice. Once to upgrade to windows 8.1, and now because windows got corrupted and it didnt want to use a restore point. Which is normal for windows, it doesnt last forever.
Drivers are a mess. Most i can gather is i'm suppose to download my laptop's drivers from here.
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv6-Entertainment-Notebook-PC-series/522...
There are 3 different wireless lan drivers, the chipset drivers cause BSOD's, i can install every single driver on the list and i still have about 4 unknown devices in my device manager.
Point is Im better off googling for the hardware ID's and scrubbing forums for my drivers.
Please could Someone supply me a link where i can download a complete Driver DVD image for my laptop model that works. I am more than willing to download a 1.4 gig torrent if it has proper work everytime drivers.
Infact i would even drive to hp head office if they could supply me with a hardcopy.
Help Please!
Before i break something.
Back on windows 7 btw

Hi @Pixelite ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-7030ei Notebook and needing a recovery disk. Here is a link to show you how to and or order the Recovery Media you need.
FWI: The driver page shows all drivers that were installed on all HP Pavilion Notebooks.
I would uninstall all the drivers with a yellow mark or caution on it. Restart the Notebook and if they are still there right click on the device and install or update the drivers.
I hope this helps you out.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Similar Messages

Display drivers causing BSODs

Hello everyone,
I'm having problem with a brand new Windows 7, W530 machine.
I had problems related to BSODs that have been 'fixed' by changing out the motherboard, RAMs and a power cable.
Now I have a problem that whenever I start Photoshop CS6, or randomly, I get this BSOD. I am attaching a Drive folder with a minidump and a screen shot.
https://drive.google.com/folderview?id=0B_ueEWCEVdGDMnlicl9CcWZzeE0&usp=sharing
I am also unable to connect to my external display, as it seems that it doesn't know what to do, it switches screens in and out for a while, changes colors, then gives an error.
Please, let me know if there is anyhting I should try, or if this is a hardware problem.
Thanks!

When you switch to discrete, you should re-run the install from the package at http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS029106
Make sure your W530 is also running the latest BIOS.
See http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS029170 for that.

Reader 9 causes BSOD on Windows XP Pro

We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.
Here are details of our systems:
Dell Optiplex 755
Windows XP Pro SP3
2GB Ram
32 Bit OS
I have found this occurs most often when opening pdf's that were created with earlier versions.
I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!

[While the original post was for Reader 9, I found this same problem with Acrobat 9 Pro, and found a solution.]
Problem: Opening one PDF file is fine, but once you open the second file -- BSOD.
Cause: There is still a problem with Adobe's 2D GPU Acceleration feature.
Per http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405218&sliceId=1, "If acceleration hardware is detected, then optimization is enabled for all files except the first one opened when Acrobat launches." That is why the first file opens OK, but the second causes BSOD. Adobe is either not detecting acceleration hardware correctly, or is not calling it correctly.
Temporary Solution:
1. In Acrobat or Adobe Reader, choose to Edit > Preferences.
2. Go to the Page Display panel.
3. Uncheck Use 2D GPU acceleration.
I tested my machine [Dell Optiplex 755, ATI Radion HD 2400 XT 8.420.0.0, Win XP Pro, Adobe 9 Pro] with "2D GPU acceleration" checked, attempted open of 4 PDFs from File Explorer -->first one opened, then BSOD, rebooted, unchecked "2D GPU", attempted the exact same operation --> all four opened in their windows and now I am happily typing on this page.
This is per http://kb.adobe.com/selfservice/viewContent.do?externalId=324073, which is a post from two years ago and relates to Adobe 8. So, Dell has been fielding calls on this for at least two years. Way to stick in there, Dell. Two years ago, Adobe knew the problem ("You are using an desktop ATI video card with driver version 8.291 or 8.301 and have the Acrobat Page Display Preference 'Use 2D GPU acceleration' enabled." was what they said back then, and recommended updating the video drivers. So, Dell stays with it, Adobe says to update your drivers. Well, I bought an entirely new Dell to get the latest drivers and it didn't help.
Permanent solution:
Adobe needs to get 2D GPU acceleration to really work (how about a line of code where you check whether it is going to work before you execute it?) or ship their product with that feature off by default.

Usb 6501 unresponsive causing BSOD(Blue Screen Error)

There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
System Details:
Windows 7 SP1
NI MAX 14.0
power saving is disabled
I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
Attachments:
060115-12480-01.txt ‏315 KB
053015-12324-01.txt ‏315 KB
052615-17440-01.txt ‏315 KB

Additional info : i did an analysis of the dump files and this is the result
0: 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: fffff88009fe10b1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800657922e, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
fffff88009fe10b1
CURRENT_IRQL: 2
FAULTING_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nifslk+0x822e:
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
STACK_TEXT:
fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
STACK_COMMAND: kb
FOLLOWUP_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nifslk+822e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nifslk
IMAGE_NAME: nifslk.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
BUCKET_ID: X64_0xD1_nifslk+822e
Can anyone help me with what this means?

ITUNES downloads from store causing BSOD windows stop error- Please Help!

Hi everyone,
maybe someone can help me out or knows how to fix this problem.
Problem in detail:
This problem started since I updated to the latest version of itunes 7 to download video for my ipod video 30gb. Itunes worked perfect on my computer before updating as I used it with an ipod mini.
I was able to use my new IPOD 30gb fine and transfer all my music to it correctly.
The main problem occurrs when downloading anything from itunes store...1st noticed this when my podcasts were updating and downloading and then the system suddenly crashed with the windows blue screen error message and had to reboot. This happened multiple times so I disabled the automatic downloads of podcasts. Itunes then works fine when not downloading anything.
I then tried purchasing a TV show, whole series, and when it began downloading, the Exact same Error and Blue screen will occur--Very Frustrating.
I uninstalled ITUNES and Quicktime, and then reinstalled them via the latest download from itunes. The same errors still occur.
When windows reboots and sends error report to Microsoft, it states the error is due to a Driver error of which the specific driver is not known.
I have called apple/itunes support and spoke with them and they could not figure out the problem and said I should check with my computers cust service and/or microsoft as it was probably something on this end...I did this and they stated the problem must be something with itunes and especially since all other programs run fine on my system.
SO basically I am going in circles trying to figure this out so I am hoping someone here may know how to fix this problem.
Not only that, but I tried the same on my desktop as I figured I could at least download my podcasts and purchases to my desktop and then transfer to my ipod from there(as I am mainly using my labtop for my ipod) and updated my desktop to itunes 7 latest version,, and figured it would work on my desktop with same operating system----but it Caused the SAME error BSOD as my labtop and in same fashion....only when downloading from itunes.
ANy help is much appreciated as I got the ipod video mainly because of ITUNES video content and podcasts and if I cannot use these major functions on ITUNES than This Was a Complete Waste for me to get the Video IPOD.
Hope there is a way to fix
Thanks

I afraid can’t help much with this, but no one else
has answered. It does seem very odd that two
different computers have the same problem. It makes
you wonder about the content you were trying to
download. As a matter of interest was the
installation for both computers done from the same
download file?
When your computer dies, can you read the stop
message or does it disappear, if it does, go to
Control Panel>System>Advanced
Click Settings in Start Up and Recovery and make sure
that Automatically Restart is no checked.
You should be able to get a stop number from the blue
screen and you may also be able to identify the
filename of a driver, which could give a clue to the
problem.
The Microsoft Website has a certain amount of help on
specific stop messages, you can search for the number
of the stop message which will be something like
0x0000000A.
There is also some help on troubleshooting stop
messages here:
http://aumha.org/win5/kbestop.htm
Thanks for your reply.
As far as the content being downloaded from itunes---consisted of different podcasts and also on a separate occasion-the tv show Heroes complete season on ITUNES..So I would guess the error has nothing to do with the content being downloaded.
The ITUNES installation for both computers was from the same itunes download file on this website on apples itunes free download.
I did not write down the most recent stop numbers and no drivers seemed to be named on the blue screen from what I could tell, but I guess I could be missing something...
From a previous crash with the BSOD- the error message listed was this: STOP: 0x00000050 (0xbad0b158, 0x00000000, 0x8056ea22, 00000002)
not sure if this helps maybe figure out the cause of this or not.
Maybe this will help get to the bottom of this.
Thanks

W510 Solid State Drive (SSD) Gets Stuck Causing BSoD. Why?

Hey guys, this has been a problem for a while now, and it is really mind boggling ... I have a Lenovo ThinkPad W510 laptop with a 256GB Crucial M4 SSD drive. Ever so randomly the drive just hangs, the LED light that the drive is trying to load something stays "ON" for up to 5 minutes or so before it finally goes into a Blue Screen of Death (BSoD). Once it goes into BSoD the laptop reboots and it gets stuck on the ThinkPad motherboard logo, eventually it will display "ERROR 2100: HDD0 (Hard Disk Drive) initialization error (X)" Where X is usually 1 or 2, sometimes 3 but rarely. It will not function again until I physically turn it off and back on using the power button.
A little bit of background about the problem, this is my 3rd Crucial 256GB M4 SSD, Crucial has been very helpful and they went as far as replacing the drive twice, i am starting to highly doubt its a drive issue, I think it could be something from the laptop itself. To be more clear, my laptop has also been serviced back in March (Motherboard was swapped as well as keyboard), parts failure. It was all done in very timely manner and everything was OK after the swap.
A representative from Crucial told me that this is a classical problem with the SATA controller driver handling TRIM, he said the drive is getting stuck in an infinite TRIM state which causes the BSoD, after that the drive goes into some sort of a "panic" mode to protect itself and doesn't function again until a full power cycle. (thus the need to turn off and then on the laptop) he also added it could be fixed by installing the correct SATA controller driver.
I have tried to use the default windows SATA controller driver, and I have tried to use the Intel one too, and it seems to happen less often with the windows drivers, but overall, it happens at least once a day. It is really frustrating and I am not able to get anywhere with it.
Any help or advice is highly appreciated. I am considering getting rid of the Crucial SSD altogether and just using Intel SSD instead, but I am really doubtful that it is the SSD's fault especially that its the 3rd one I use. I also know a couple of friends who own ThinkPads with Crucial M4 SSD inside them, and they seem to be working very well for them.
Thanks in advance,
Al.

Hi again,
Ok so I have applied the fix you have mentioned above, and it did improve (lower) the frequency of the problem happening. It really improved a lot significantly when I uninstalled the Intel drivers and used the Windows 7 built in SATA controller drivers.
However, ... it still happens ... less frequent, but it still takes place, my SSD still gets stuck at least once in 3 days now, or once in 2 days (after severe testing) and the same scenario happens. I am really stuck at this point, and not sure which direction to take.
Any help would really be appreciated, if you have / know any method to debug the BSoD's I get and a way to locate the source of the problem I am willing to go through it 1 by 1 and solve this problem before deciding to finally just giving up on the drive altogether.
Sincerely,
Al.

Display adapter causing bsod

hellloo
I am currently trying to fix my bsod issue with my evny dv6 64bit running windows 8 (16gb RAM, intel i7 8 cores), which has been happening since the first month I got it, for many different reasons.
Updating drivers and such has fixed a lot, but then a new error appears. At first I thought it was a RAM issue but that has so far come up clear (ran memtest for 24 hours, 8 passes no errors in fail safe mode, it crashed once when not in fail safe mode but I haven't been able to recreate it). recently I noticed that both intel HD 4000 graphics and NVIDIA are enabled, which it's apparently supposed to do. However, certain applications will run better, and without crashing, if I disable one.
For instance, the sims 3 will crash on the save game loading screen, but if I disable intel graphics, not only does the quality go waaay up, it won't crash on the loading screen. it is laggy, however.
minecraft won't play if only NVIDIA adapter is enabled. the picture won't show and it just won't respond. works if both are enabled. haven't managed to get it to crash if just intel graphics is enabled
Games are the only thing that makes the computer bluescreen. They're the only resource heavy programs I run (sometimes I use photoshop but as far as I can remember that has never resulted in bsod)
to my understanding, it's supposed to use NVIDIA for games and the such, but intel HD for everything else? is there the possibility of some kind of miscommunication going on with these adaptors to cause constant blue screens? or is the error more likely somewhere else?

Hi Inkiecat,
Thank you for visiting the HP Support Forums and Welcome. I have read your thread on your HP ENVY dv6 Notebook and BSOD. Please call our technical support at 800-474-6836. If you are calling within North America, the number is 1-800-474-6836 and for all other regions click here.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Wifi causing BSOD on Windows 7 64 bit

The Intel 5300 wifi card driver is causing Blue Screen of Death (BDOS) on my x200s Windows 64 bit ultimate.
A typical scneraio would be:
- Turn wifi on
- Connect to access point
- Within a few minutes, Internet activity will blue screen the laptop
Wifi card and motherboards were replaced.
After trying a bunch of stuff, I resigned to wipe the laptop and do a fresh operating system install. The result is still BSOD on wifi.
Wifi drivers are the latest from Lenovo (13.0.0.107)
Intel has a newer version (13.1.1.1) for the 5300 wifi card on the Intel web site. I am not sure it is compatible with Thinkpad.
Any advice would be appreciated, as the laptop is unusable with the wifi on.
Thank!

The Intel 5300 wifi card driver is causing Blue Screen of Death (BDOS) on my x200s Windows 64 bit ultimate.
A typical scneraio would be:
- Turn wifi on
- Connect to access point
- Within a few minutes, Internet activity will blue screen the laptop
Wifi card and motherboards were replaced.
After trying a bunch of stuff, I resigned to wipe the laptop and do a fresh operating system install. The result is still BSOD on wifi.
Wifi drivers are the latest from Lenovo (13.0.0.107)
Intel has a newer version (13.1.1.1) for the 5300 wifi card on the Intel web site. I am not sure it is compatible with Thinkpad.
Any advice would be appreciated, as the laptop is unusable with the wifi on.
Thank!

JDK 7u2 download causes BSOD

A funny anomaly for those who use JDK on Windows 7, just for your info.
On Windows 7 Professional ver.6.1 (Build 7601: Service Pack 1) that has Adobe Reader 9 Automatic Updater enabled, an attempt to download jdk-7u2-windows-i586.exe resulted in Blue Screen of Death every time when the Adobe Updater has "Click here for Updating for the newest version of Adobe Reader" displayed (as a sign of a completed automatic installer download, and the message ignored by the user).
The BSOD occurred at the last part of the download, occurred every time without failure, until I finally gave up enjoying the good old Blue Screen and installed the latest Adobe Reader 9(version 9.4.7) before downloading the JDK 7u2 installer. After this Adobe install, the download and the installation of the SE JDK went smoothly without a hitch.

Thanks for the comment. It prompted me to describe the BSOD in more detail.
Out of the 11 times I experienced these BSOD's while downloading 7u2, I got several different bug check strings:
MEMORY_MANAGEMENT 4 times, Points to ntkrnlpa.exe
IRQL_NOT_LESS_OR_EQUAL 3 times, Points to fltmgr.sys, MpFilter.sys, ntkrnlpa.exe (once)
Points to halmacpi.dll, ntkrnlpa.exe (twice)
BAD_POOL_HEADER Twice, Points to fltmgr.sys, halmacpi.dll, ntkrnlpa.exe
KERNEL_MODE_EXCEPTION_NOT_HANDLED Once, Points to ntkrnlpa.exe
PFN_LIST_CORRUPT Once, Points to ntkrnlpa.exe
Interesting, isn't it? It seems Windows is not quite sure what to blame the blue screen for. While I am quite aware of app developers' tendency to blame device drivers, driver coders blaming BIOS, BIOS coders pointing to hardware for the "cause" of a problem, I am not interested in semantics on the difference between causing and triggering. It is certainly true that many BSOD has their roots in device driver and BIOS bugs, but I am not so sure if this is the case here. As I don't have the time to look into the way Adobe lets its updater to make downloaded file status to survive a reboot, how Oracle installer performs CRC and other operations, and how Windows system files and config protection schemes interact with them, I chose to be a news reporter.

Ntkrnlmp.exe causing BSOD randomly

Recently we have been having random reboots and BSODs on our TS box
Background:
Windows Server 2012 R2 - RDS/Print/File - VM on Hyper-V Host (Windows server 2012 r2)
https://onedrive.live.com/redir?resid=AF339BCAC63CB706!228&authkey=!AG-5gWy6tUwoAiE&ithint=folder%2c
Attached are the dump files^^^
Ran ran memtest86 on the host with no errors
Ran Windows memory diags on host and VM with no errors
Updated all firmware and drivers for our HP Proliant ML350 gen8 server
Ran Driver Verifier and pointed it towards the problem child (ntoskrnl.exe) and the server bsod twice in a matter of ten minutes with, of course "Driver Verifier detected a Violation"
Checked the version number Ntoskrnl.exe version 6.3.9600.16452 - Removed
Windows Update Rollup - KB2903939
Double checked and verified removed.
Rebooted and ran Driver verifier after update removal - BSOD twice with same scenario as above. Disabled Driver verifier for now.
I'm hoping to find a fix for this as this is the main RDS server.
I appreciate your time. If you need anything else, please let me know.
Thanks!
*Going to add another DUMP that happened today Below*
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
Machine Name:
Kernel base = 0xfffff802`1f286000 PsLoadedModuleList = 0xfffff802`1f54a990
Debug session time: Fri Apr 4 16:32:20.197 2014 (UTC - 4:00)
System Uptime: 0 days 6:36:23.236
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`35f58018). Type ".hh dbgerr001" for details
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8021f2cc740, ffffd000276e0eb0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : ntkrnlmp.exe ( nt!RtlAvlRemoveNode+478 )
Followup: MachineOwner

Thanks for the information.
In case you do need to enable Driver Verifier, refer to the following:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows
kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 -
http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this
happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring
all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and
as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods:
5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
How long should I keep Driver Verifier enabled for?
I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
They will be located in %systemroot%\Minidump
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617
Regards,
Patrick

Ntkrnlmp.exe causing BSOD intermittently (DUMP Attached)

Recently we have been having random reboots and BSODs on our TS box
Background:
Windows Server 2012 R2 - RDS/Print/File - VM on Hyper-V Host (Windows server 2012 r2
https://onedrive.live.com/redir?resid=AF339BCAC63CB706!228&authkey=!AG-5gWy6tUwoAiE&ithint=folder%2c
Attached are the dump files^^^
Ran ran memtest86 on the host with no errors
Ran Windows memory diags on host and VM with no errors
Updated all firmware and drivers for our HP Proliant ML350 gen8 server
Ran Driver Verifier and pointed it towards the problem child (ntoskrnl.exe) and the server bsod twice in a matter of ten minutes with, of course "Driver Verifier detected a Violation"
Checked the version number Ntoskrnl.exe version 6.3.9600.16452 - Removed
Windows Update Rollup - KB2903939
Double checked and verified removed.
Rebooted and ran Driver verifier after update removal - BSOD twice with same scenario as above. Disabled Driver verifier for now.
I'm hoping to find a fix for this as this is the main RDS server.
I appreciate your time. If you need anything else, please let me know.
Thanks!
*Going to add another DUMP that happened today Below*
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
Machine Name:
Kernel base = 0xfffff802`1f286000 PsLoadedModuleList = 0xfffff802`1f54a990
Debug session time: Fri Apr 4 16:32:20.197 2014 (UTC - 4:00)
System Uptime: 0 days 6:36:23.236
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`35f58018). Type ".hh dbgerr001" for details
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8021f2cc740, ffffd000276e0eb0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : ntkrnlmp.exe ( nt!RtlAvlRemoveNode+478 )
Followup: MachineOwner

Please understand that this forum is meant for general windows server queries and we dont really analyze the crash dumps here.
Please
contact Microsoft Customer Service directly so that the memory dump file can be analyzed and this issue can be resolved efficiently.
You
may obtain the phone numbers for specific technology request please take a look at the web site listed below:
https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1
http://www.arabitpro.com

Flash causes BSoD on GX660R

Recently I bought a MSI GX600R laptop.
It seems to be working all fine except for a small issue that I can't figure out to solve.
When I view streamed videos in Flash for instance YouTube videos the laptop has a tendency cause some kind of graphical error, making the screen output look really bad and if I don't immediately close the browser a BSoD occurs.
In most cases I can make the graphical error disappear and avoid the BSoD by closing down the browser.
For the record I'm running the newest Adobe Flash Player and just downloaded the newest ATI drivers/Catalyst.
The problem is not browser specific since it happens both in IE as well as Chrome.
Furthermore I'm not sure it only happens when I'm running my laptop on the batteries but it certainly happens a lot more frequently.
Have anyone seen this problem before?

Quote from: Kksmed on 19-December-10, 19:04:45
Recently I bought a MSI GX600R laptop.
It seems to be working all fine except for a small issue that I can't figure out to solve.
When I view streamed videos in Flash for instance YouTube videos the laptop has a tendency cause some kind of graphical error, making the screen output look really bad and if I don't immediately close the browser a BSoD occurs.
In most cases I can make the graphical error disappear and avoid the BSoD by closing down the browser.
For the record I'm running the newest Adobe Flash Player and just downloaded the newest ATI drivers/Catalyst.
The problem is not browser specific since it happens both in IE as well as Chrome.
Furthermore I'm not sure it only happens when I'm running my laptop on the batteries but it certainly happens a lot more frequently.
Have anyone seen this problem before?
Hi!! i resolved on flash player disable hardware acceleration. But sometimes i have this problem. I updated my driver for ATI, but not work.
And update flash video bios again dont work :(

560Ti OC 2GB drivers causing PC shutdown

Ever since I updated my nVidia driver to 301.42, my computer has been randomly shutting down as if the power cord has been removed. There are no errors in event log, no BSOD, and the PC doesn't restart. I have rolled back to 275.33, but the problem still occurred. I then tried 285.62 (the MSI download page version) and 296.10 but still the problem occurred. The PC case is clean, I have reseated the CPU, I have run Memtest86, I have used OCCT to perform PSU testing, I have unplugged HDDs. I have repeatedly removed the video card drivers completely and reinstalled. The computer will sometimes run ok for anywhere between 10 mins and an hour and then shutdown when I am in a game such as WoW or Team Fortress 2 (even with the video settings set to low), and will then not be able to boot past the Windows loading screen without shutting off again. No errors have been brought up in any tests. All temperatures are optimal on the PSU/GPU/MB. The PC runs fine in safe mode and with the Windows standard VGA driver. I have performed full antivirus scans and Spybot scans and there has been no result. I have uninstalled the 3D vision and HD audio components of the nVidia drivers and still the problem occurs. I uninstalled Firefox and Adobe Flash player (after I turned off hardware acceleration - which made no difference).
Nothing on the computer is different apart from the nVidia driver update, and rolling back drivers should have fixed whatever problem was being caused.
I don't know what else I can do to test for the error. I have also submitted to nVidia in the hope of a resolution though am doubtful they will give me anything worthwhile. Please advise.
S/N: 602-V238-350B1201005721
Motherboard: Asus M4N82 Deluxe
PSU: Vantec 750w
Kingston HyperX DDR2 - 4096MB
AMD Phenom 2 X3 720

Your PSU is weak or faulty, consider getting a decent and quality PSU

Broadcom drivers causing XP to explode

I have a MacBook Pro that I just bought recently. I installed Boot Camp a while back on my Mac Pro desktop with no issue at all. I'm now trying to install it on the MacBook Pro and I'm getting beaten up a bit.
I installed XP SP2 with no issue, really. Everything went smoothly. It booted up into Windows, worked great. So I put in the Leopard disc I have here at work (since I don't have the MacBook Pro's install disc here) and started the Boot Camp setup. Everything installed smoothly, that is, until it hit the Broadcom wireless drivers. It showed Broadcom wireless drivers as the thing it was working on for a few seconds, then bam... I get the blue screen of death. Okay, no problem, I reboot and start it all over again. Blue screen again, at the same exact point. Now when I try to boot back into Windows, it shows the Windows XP loading screen and then reboots automatically, giving me the whole "Windows failed to start up correctly" message.
Now if it's just the Broadcom wireless drivers that are the problem, I can live without wireless when I'm in XP because to be honest I probably won't be in XP all that much. Is there a way I can have the Boot Camp installer skip it?
Any ideas what's going on here? I'm going to try to do an XP system restore to the point before I tried installing Boot Camp. If all else fails, it's not a big deal to have to start from scratch again. I'm just hoping I can work around this BSOD. Freaking Windows...

I understand that it can be frustrating but there's no need to insult a perfectly viable solution. It's not "idiotism" (whatever that is). If you read this topic it is for the MacBook Pro, not the Air. Obviously not installing wireless drivers for the Air causes a bit of the problem.
I certainly don't think you can really blame Apple for it not working. While Boot Camp is their thing, they make it clear that Windows compatibility is something they're not going to break their backs over. Their view seems to basically be if Boot Camp works for you, great... if not, oh well. I can't say that I fault them at all for that stance. After all, I don't think it's their responsibility to go out of their way to ensure that Broadcom's driver for an Apple wireless controller is fully compatible with Windows XP as well as OS X. I don't know about you, but I got my Mac because OS X blows Windows out of the water, so I'm naturally going to do the vast majority of my work on OS X. I don't mind if I can't use wifi under Windows because for the short time I'll be working outside of OS X, I'll just plug into a wired connection. I can live with that. If I can't get Boot Camp working right, it may be a bit of an inconvenience for me but overall I don't care -- using Windows wasn't the reason I bought my Mac.
So in closing, you're wrong. This solution has it's usefulness for the users it pertains to. You're not one of those users, so it might be more productive for you to seek out other solutions which are better given your circumstances rather than blast a solution that works.

Tecra M3 video drivers causing crashes

My Toshiba Tecra M3 is crashing (freezing or blue screen of death) with drivers 71.14, 71.36, and 76.44. It uses an NVIDIA GeForce Go 6600 TE 128M. When I uninstall all video drivers (or boot into safe mode), the laptop runs fine, although of course scrolling is deadly slow and I can't suspend or hibernate. But when I install either of the two WHQL certified drivers from Toshiba's site, 71.44 or 71.36, I can consistently create a crash just by running a 3D screensaver for more than 3 minutes. The same thing happens with the 76.44 non-WHQL driver from laptopvideo2go.com.
Sorry if this is not the best thread to post on, but I would desperately appreciate any help you can offer on what driver might work reliably. At this point, I'm not at all interested in great graphics performance; I just want a stable laptop to do some work on. Is there perhaps some setting within the driver to turn off whatever fancy features are causing the crash?
The laptop has a 2.13 GHz Pentium M and 2 GB of RAM. It's running WinXP SP2 with all updates and is using BIOS 1.20, the latest. And I doubt it's a related, but here's a different problem I ran into with the VPN, Wi-Fi, and Matlab.
Thanks in advance for any help you can provide.
[Edited by: admin]

Hi danhkon
I suppose that your notebook worked properly at the beginning. Can you maybe remember since when the unit started to make these troubles to you? It is not easy to give you a proper opinion or any kind of solution because every problem is caused by some reason.
First of all I want to say that you should use just display driver given by Toshiba and not some driver that you found on the net. The drivers that you got on Tools & utilities CD or drivers that you can find on Toshiba site are all tested and they should work properly. As far as I know Tecra M3 is a new model and also delivered with SP2. That means that all drivers are also tested to work properly with SP2.
Before you spend lot of times searching the right solution you should, in my opinion, save your data and reinstall OS using Recovery CD. On this way you will have a stable laptop to do some work on it. If there is no second partition you can make it for data saving using expert mode installation.

Drivers cause BSOD {URGENT}

Similar Messages

Maybe you are looking for