T410 NVIDIA BSOD caused by nvlddmkm.sys

Hi all,
I have lot of BSOD (1/week at least) caused by nvlddmkm.sys
I have the latest driver according to lenovo update.
I'm on Win7 x64.
This is not caused by overheating I'm not running any game or 3d application,
GPU idles ~60C.
Could someone help me what to do?
(Some time ago I tried the driver from NVIDIA page, but had the same experience, now I'm back on the Lenovo "official" driver.)

hey nuri,
could you try the following ?
- uninstall the current driver you have installed
- -restart your system and let Win7 install its generic driver
- check if it happens again
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

Similar Messages

MOVED: BSOD caused by nvlddmkm.sys in Vista Ultimate x64

This topic has been moved to Vista problems.
https://forum-en.msi.com/index.php?topic=121723.0

hey nuri,
could you try the following ?
- uninstall the current driver you have installed
- -restart your system and let Win7 install its generic driver
- check if it happens again
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

BSOD caused by e22win7x64.sys

Hey all,
recently I have some issues related with e22win7x64.sys. I believe this BSOD is caused by Killer network manager.
I have checked all possible solutions like uninstall Killer network, and only install the drivers.
Unfortunately, it doesn't help me much. I still have BSOD problems.
Does anyone know if there exist another network adapter that can replace Killer network?
My motherboard is X99S Gaming 9 ACK
Memorary: G.SKILL Ripjaws 4 series 32GB (4 x 8GB) 288-Pin DDR4 SDRAM DDR4 2666
GPU: MSI GTX 980 GAMING 4G GeForce GTX 980 4GB
CPU: I7-5960X

which killed driver version you are using?

GT70 OND-219US + nvlddmkm.sys + BSOD

Before I dive into the issue, I'll throw out there that I have an RMA to have warranty work done that is related to the issue. I'm posting this in case anyone has ran into the issue and knows of any way to remedy the issue without having to resort to an RMA.
This rig has run flawlessly for nearly two years, and has been amazing at playing every game I've tossed at it on max settings.
About 8 weeks ago, it started doing random BSOD, paired with nvlddmkm.sys in the error. The fan kicks into a heightened state and sticks as this happens. The settings are factory, with no modifications and no overclocking (laptop was too expensive for me to risk that). I suspect that it was the result of an Nvidia driver, but can't be 100% certain.
I have removed all video drivers using DDU, and performed reinstalls with the factory OEM drivers. None of these have proven useful.
I am able to test games using the Intel GPU, and there are no crashes using this method (I suspected as much, since the file at the center of the BSOD, nvlddmkm.sys, is an Nvidia file).
I have reinstalled Windows 7 home premium three times. I also own Windows 7 Pro, and Windows 8.1 Pro. I have installed these each two times. The issue still occurs.
I'm reasonably confident that the RMA is the best step for this. I have further read on Nvidia's official forums that there have been driver issues with the 675m that cause the issue, and Nvidia has yet to remedy this. None of the 680m cards have these issues. It is only the 675m.
I don't think MSI would do this, but following the revelation that the 675m has some pretty big issues with Nvidia's drivers (not pointing fingers at MSI at all. Nvidia gets all the blame for this), I'm wondering if MSI would be open to swapping my 4GB 675m for a 2GB 680m, or even a comparable AMD GPU? Seeing as my warranty is expiring at the end of August, I'd like to make sure the issue is resolved, and I'm not stuck with another 675m that will have the same issues at some point after the warranty expires.
For me, this is more about peace of mind, being able to get work and play done without any downtime. I'd love it if I didn't have to live under the threat of the same card having the same issue after the warranty has expired. :D
Selling my ASUS gaming laptop and getting this laptop was the best decision I've made (next to getting divorced, of course).

This exact same thing happened to me, the month after my warranty expired.
BSOD with the same nvidia file. After that, the device is always stopped by Windows (error 43) in Device Manager. I can get it "Working properly" if I disable and re-enable it, but it's still useless since for any software (Nidia Contol Panel, games, etc) to recognize it's existence it needs to be enabled on reboot. (OR it's not really enabled and CP is lying to me).
Does anyone know if there will every be a fix for this? It's starting to seem like the card itself is damaged, since no driver works (even the one on the MSI Install CD).
Please say it ain't so. It'll be another ten years before I can buy a lappy like this one :(
MSI G70 0ND, GTX 675MX 4GB with Windows 8.1

BSOD after installing NVIDIA driver (nvlddmkm.sys error)

Hi, I hope I'm posting this in the right place.
A few days ago I purchased an MSI GS60 044 (970m) laptop with Windows 8 preinstalled on it. I have an intense hatred for Windows 8 so I decided to do a clean install of Windows 7 using a disk I own. Everything was going well until I installed the NVIDIA graphics driver. The computer would run sluggishly and then Blue Screen with an error regarding "nvlddmkm.sys."
I got the drivers from MSI's website and followed the installation order on that page. I even tried downloading the latest driver from NVIDIA's website, but I got the same results.
Is anyone familiar with this issue? Is there anything I can do?
Thanks!
- Daniel

I really appreciate the help! I ended up reinstalling windows again and this time before installing the NVIDIA driver I installed the BIOS update that's provided under the "BIOS" tab on the GS60's support page. It's been installed for about 2 hours now with no crashes, so I hope that means it's fixed. I could just be getting lucky though, I'll post again tomorrow with results.
Unfortunately, now my LAN and WLAN drivers have stopped working. When I troubleshoot, windows says that there aren't any drivers detected. I have tried uninstalling and reinstalling both the bigfoot and intel drivers but neither are working. I just can't catch a break with this thing. >_<
In the event that I do have to send it to MSI, wouldn't the computer not be covered in their service anymore since I installed a different OS/formatted the original drives? I'm really hoping there isn't a hardware issue since I ordered the laptop brand new off of ebay.
Thanks again for all of the help!

0X00000116 nvlddmkm.sys - with Nvidia GTX280 OC

Hello lads,
Ive started getting a Stop Error with "0X00000116 nvlddmkm.sys" when trying to play games.
I have 2 GTX280 OC's from MSI and tried them both on their own and still get the error.
Ive reinstalled the latest drivers thinking its corrupt drivers, but it still happens.
Any help or advice would be great.
CPU: Quad Core Q6600 @ 3Ghz
Motherboard: Asus Striker 2 Extreme
Memory: OCZ Platinum Edition DDR3 1333mhz 2x 2GB
Video card: MSI GTX280 OC x 2
Hard drive: 2x Seagate Baracuda 750GB
Operating system: Vista 64bit SP1
Power Supply: Cooler Master Real Power 1000watt
Mathew

if i followed bas's advice i would be on 32 bit xp and thrown away my 2 280gtxocs for a ati 4870 (it's better apparently) vista 64 is a little wobbly, especially with overclocked quads, using overclocked grx cards with the latest drivers gives me the same error, either downclock card to standard or use an older driver, i use 142 from msi site and have both cards @700 which gives me better performance than standard clocks with latest driver, you have to experiment when you find the set up that works, back your system up on it for when you try nvidias next attempt at satisfying the masses. use a driver cleraner or good registry cleaner if you're not happy with manually removing the left overs after standard add/ remove.
mines a different system and with quad sli you need 64 bit, experiment most set ups work fine, a few bsod, check through vista logs to make sure it's nvidia driver and nothing else.
good luck.

GT70-0ND nvlddmkm.sys BSOD error

Hello Everyone.
the last months or so i started getting random BSOD all pointing to nvlddmkm.sys
i got in touch with nvidia to help me solve the problem.
the things i tried:
1) changing registry: add TdrDelay and TdrLevel (per nvidia tech department)
2) clean install of several different versions of nvidia graphics drivers (note i also used Driver-Fusion to clean up registry after each uninstall)
3) Full-system scan for Malware, Virus etc - using several programs, such as: AVG, MalwareByte.... - all returned clean reports.
lastly i tried running "Windows Memory Diagnostic Tool" and Memtest86+.
now both discovered errors!!
Memtest86 was able to complete a full pass with no crashes
but Windows tool crashed twice, once just as i started testing and once just at the beginning of the second pass.
Pictures of the Errors:
Memtest86 after 1 pass:
Windows Memory Diagnostic Tool - Stuck.
now i wanna test out which RAM module is at fault, by removing them all and inserting them one by one for testing.
the problem im currently having is as follows:
as u open up the laptop cover from the bottom, u can immediately see 2 RAM modules sitting near the CPU & GPU.
but my system has 4 RAM sticks. the other 2 i cannot locate.
if u guys know, could you please tell me where can i locate them and how to remove them?
i rather not disassemble the entire thing.
just in case you wonder, i checked youtube and google for instructions on how exactly to do this.
but all the guides i found only mention the 2 RAM modules i already know about and not the other 2.
Thanks in Advance.
Edit:
forgot to add system specs:
CPU: i7-3630QM
GPU Geforce GTX 675MX 4GB
Memory: 16GB DDR3 1600Mhz (4x4GB)
SSD: 120GB Patriot Pyro SE
HDD: 750GB WesternDigital 7200rpm
OS: Windows 7-64bit
side-note: system came pre-installed with windows 8 + appropriate UEFI Bios.
as soon as i got the system i formatted it and installed Windows 7-64bit. - switched Bios to LEGACY mode.

i also dont live in the USA, luckily mine is still within the 1 year global warranty.
i actually got this laptop as an RMA replacement because of MSI :censored:up.
i had the GT783R, the graphics card went bad just 1 month after the 1 year global warranty expired. had to send all the way to the USA to fix it (still a better option than buying a new laptop or a replacement graphics card - which almost none sell it.)
well, they replaced my GTX 580M 2GB with a GTX 670M 3GB, calling the 670M "better" than the 580M. if you know your graphics card, a little check up on google can tell u that no! its not better. the 670M is almost equal in performance to the 570M.
anyways after several calls to their tech support and speaking with a manager they agreed to take back my GT783R with them covering shipping expenses and giving me a new laptop, the GT70, in its stead.
luckily for me, Laptop warranty goes according to laptop serial number, meaning my GT70 is still under the 1 year global warranty.
so i can fix it in my own country.
why am i telling you all this?
because prior to sending my GT783R to the USA, i spent almost 2 months troubleshooting the problem and trying to solve it. so im trying to save u some time and headache.
i even tried contacting nvidia tech support to help me solve the problem
eventually the problem wouldnt go away and i had wasted 2 months without a laptop for nothing.
so basically if you run the following tests and everything is fine it most likely the graphics card and it needs to be replaced.
first you can make sure your laptop isnt full of dust inside and the vents arent clogged. then try these:
1) running memtest (several passes) with no errors
2) formatting the laptop to rule out software issues
3) testing several nvidia drivers (the ones the came with the laptop and the latest Stable nvidia release)
4) (nvidia tech rep suggestion) Open NVIDIA Control Panel --> Manage 3D settings.
Go to Program Settings tab.
In the setting window, change the ‘Power Management Mode’ to ‘Prefer Maximum Performance’.
5) (nvidia tech rep suggestion) Please try this registry fix and observe the computer performance.
a) Go to the Registry Editor (Press Windows Logo + R and type "regedit" in the Run window and click ok)
b) Navigate to HKEY_LOCAL_MACHINE - > System -> CurrentControlSet -> Control -> GraphicsDrivers (make sure Graphics Drivers is highlighted).
c) Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).
If that doesn't work, try disabling it, by adding the following DWORD: TdrLevel and setting the value to 0, then rebooting.
6) updating BIOS to latest version.
****obviously im not responsible for anything that happens to your laptop and you are trying the stuff i mentioned at your own risk.*****
btw, if your laptop suddenly doesnt even recognize your Graphics card i think its toast.
no point wasting time, send it RMA if u can.
Good Luck.

Nvlddmkm.sys on startup

OS - windows 7 home edition 64bit - updated to SP1 the other day
MOBO - ASUS P5B DLX/WIFI-AP Pentium 4/Celeron/Pentium D/PentiumEE/65nm dual-core/Core2Duo/Core2EE
PSU - Hiper 580W Type-R Modular PSU SLI/CrossFire Certified
GPU - MSI Nvidia GTX460/OC 1GB PCI-EX
HD - Western Digital WD2500KS Caviar SE 250GB 7200RPM SATAII/300 16MB Cache
RAM - Corsair TWIN2X 6400C4 DDR2, 2048MB CL4 Kit w/two 1GB Dimm's, E.P.P Technology (two of these 4Gb in total)
CPU - Intel Core 2 Duo E6600 (2.4ghz) Socket 775 FSB1066 4MB Cache Retail Boxed Processor
CPU cooler - Arctic Cooling (AC-FRZ-7P) Freezer 7 Pro Socket 775 CPU Cooler
DVD - NEC AD-5170A-0B 18xDVD±RW DL Black - Bare Drive
floppy drive - Sony OEM 3.5 Floppy Drive Black
Hi all,
After my MSI 8800GTX broke, i have now bought a MSI 560 GTX.
https://forum-en.msi.com/index.php?topic=146292.0
Im very pleased with it, but was very dissapointed to see an old problem reoccurring. I used to get nvlddmkm.sys errors during certain games (IL2 1946 was the main culprit) where the game would freeze, black out, and i would have to end task to get back to the desktop. When I got back to the desktop there would be an error saying 'a driver had stopped' and then something about nvlddmkm.sys. I started on Vista 64bit, then upgraded to windows 7. I had the problem on both, but more so on Vista.
Now I have tried every remedy under the sun for this, if you google it you will see what I mean, noone seems to have a clear idea of what causes it, and there are plenty of remedies(none worked for me). Nvidia blame windows, windows blame nvidia, some blame ram, some PSU, some the GPU, some the mobo.
Some claim updating drivers fixes it, some that you have to use the driver cleaner, or rolling back drivers, or looking for nvlddmkm.sys in your registry (multiple copies were rpesent, driver cleaner wasnt deleting them) or numerous other things.
The issue I am having is not quite the same, it hasn't happened in-game yet, but I have got a BSOD on startup a few times and the error message is the nvlddmkm.sys one.
I really hope this forum can help, Ithis is the 2nd MSI card I have bought i would like to enjoy this one.

Quote from: conorc on 31-March-11, 17:57:21
but if it calls for 31, and i have 30, thas close enough.
You have a bungeecord that stretches to 140 meters, the jump is 139 meters, close enough, but would you jump??
Close enough doesnt work in the computer/electricsworld
Dont go skimping on the psu, its your lifeblood for your system, if it goes it often takes other parts with it to the eternal electronicafields.
Get a Corsair, PC an Powercooling, Seasonic, Thermaltake or so, those are good quality psu's.
Read here for good reviews about psu's:
http://www.jonnyguru.com/index.php

Windows Server 2008 Enterprise SP2 64bit BugCheck 3B Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )

Hi Guys,
Has anyone come across this BSOD error and found a fix, as I'm at a lost as to what is causing the BSOD
Please see Windows Debugger output below:-
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Transfer\Minidumps\Mini051414-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer
Built by: 6002.23154.amd64fre.vistasp2_ldr.130707-1535
Machine Name:
Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01dd7e30
Debug session time: Wed May 14 12:01:16.178 2014 (UTC + 1:00)
System Uptime: 3 days 7:15:01.532
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff9600030271e, fffffa603d967ec0, 0}
Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )
Followup: MachineOwner
7: kd> !analyze -v
*                        Bugcheck Analysis
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600030271e, Address of the instruction which caused the bugcheck
Arg3: fffffa603d967ec0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!PFFOBJ::pPvtDataMatch+12
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
CONTEXT: fffffa603d967ec0 -- (.cxr 0xfffffa603d967ec0)
rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80369f6680 r10=fffffa803b6cdc48
r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
r14=000000000000301f r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b             efl=00010202
win32k!PFFOBJ::pPvtDataMatch+0x12:
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960003009b1 to fffff9600030271e
STACK_TEXT:
fffffa60`3d968720 fffff960`003009b1 : 00000000`0000301f 00000000`00004fbc 00000000`00000000 fffffa80`3b6cdbb0 : win32k!PFFOBJ::pPvtDataMatch+0x12
fffffa60`3d968750 fffff960`001aacb6 : fffff900`c2ade350 fffff900`c3fa59e0 00000000`00000000 fffffa80`369f6680 : win32k!PFTOBJ::bUnloadWorkhorse+0x55
fffffa60`3d9687d0 fffff960`001ab8d8 : fffff900`c2ade2d0 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
fffffa60`3d968810 fffff960`0019fbc0 : 00000000`00000000 fffff800`01ebfe00 fffff900`c277dd10 fffffa80`38d5b800 : win32k!NtGdiCloseProcess+0x4a8
fffffa60`3d968870 fffff960`0019f423 : 00000000`00000000 fffff900`c277dd10 00000000`00000000 fffff800`01ebfe48 : win32k!GdiProcessCallout+0x1f4
fffffa60`3d9688f0 fffff800`01ecc924 : 00000000`00000000 00000000`00000000 fffff800`01db6ec0 00000000`00000000 : win32k!W32pProcessCallout+0x6f
fffffa60`3d968920 fffff800`01ebfe65 : fffffa60`00000000 fffff800`01c89701 fffffa80`57c73810 00000000`78457350 : nt!PspExitThread+0x41c
fffffa60`3d968a10 fffff800`01c89881 : fffffa60`3d968ad8 00000000`00000000 fffffa80`382fe430 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffffa60`3d968a40 fffff800`01c8d935 : fffffa60`3d968ca0 fffffa60`3d968ae0 fffff800`01ebfe74 00000000`00000001 : nt!KiDeliverApc+0x441
fffffa60`3d968ae0 fffff800`01c6721d : fffffa80`3b6cdbb0 00000000`0038f2f4 fffffa60`3d968bf8 fffffa80`597301e0 : nt!KiInitiateUserApc+0x75
fffffa60`3d968c20 00000000`74c93d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2
00000000`000eebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c93d09
FOLLOWUP_IP:
win32k!PFFOBJ::pPvtDataMatch+12
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFFOBJ::pPvtDataMatch+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52f4cf4d
STACK_COMMAND: .cxr 0xfffffa603d967ec0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
BUCKET_ID: X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
Followup: MachineOwner
7: kd> lmvm win32k
start             end                 module name
fffff960`000e0000 fffff960`0039a000   win32k     (pdb symbols)          c:\symbols\win32k.pdb\E3E9D4C3813E470A90F52FAEC6461A252\win32k.pdb
    Loaded symbol image file: win32k.sys
    Mapped memory image file: c:\symbols\win32k.sys\52F4CF4D2ba000\win32k.sys
    Image path: win32k.sys
    Image name: win32k.sys
    Timestamp:        Fri Feb 07 12:19:25 2014 (52F4CF4D)
    CheckSum:         002AD344
    ImageSize:        002BA000
    File version:     6.0.6002.23325
    Product version: 6.0.6002.23325
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     win32k.sys
    OriginalFilename: win32k.sys
    ProductVersion:   6.0.6002.23325
    FileVersion:      6.0.6002.23325 (vistasp2_ldr.140207-0038)
    FileDescription: Multi-User Win32 Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
7: kd> .cxr 0xfffffa603d967ec0
rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80369f6680 r10=fffffa803b6cdc48
r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
r14=000000000000301f r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b             efl=00010202
win32k!PFFOBJ::pPvtDataMatch+0x12:
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
Thanks
JT

Getting BSOD's pointing to this dll also. Started at around the same date as Jitinder's post. Maybe a new issue introduced has been introduced?
7: kd> !analyze -v
* Bugcheck Analysis *
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600011fda0, Address of the instruction which caused the bugcheck
Arg3: fffffa6027acd1d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
"kernel32.dll" was not found in the image list.
Debugger will attempt to load "kernel32.dll" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh
CONTEXT: fffffa6027acd1d0 -- (.cxr 0xfffffa6027acd1d0)
rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa802800a288
r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
r14=000000001539ed50 r15=0000000000000001
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960002e66d4 to fffff9600011fda0
STACK_TEXT:
fffffa60`27acda30 fffff960`002e66d4 : 00000000`00000000 fffffa80`2735ab50 00000000`00000001 00000000`746e6647 : win32k!PFEOBJ::vFreepfdg+0xe8
fffffa60`27acda60 fffff960`002f0cb7 : 00000000`00000000 fffff900`c008f000 fffff900`c0010000 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x210
fffffa60`27acdac0 fffff960`002f0926 : 00000000`00000000 fffff900`c2bfcca0 fffff900`c0ae4010 00000000`00000000 : win32k!vRestartKillRFONTList+0xab
fffffa60`27acdb10 fffff960`00275c79 : 00000000`00000000 00000000`00000001 fffffa80`235762b0 fffff900`00000002 : win32k!PFTOBJ::bUnloadWorkhorse+0x196
fffffa60`27acdb90 fffff960`002978e2 : fffffa80`2800a060 fffff900`c0b932a0 fffffa60`27acdca0 00000000`7457c444 : win32k!GreRemoveFontMemResourceEx+0xad
fffffa60`27acdbf0 fffff800`01a64173 : fffffa80`2800a060 fffffa60`27acdca0 00000000`7ee9f000 fffffa80`25803040 : win32k!NtGdiRemoveFontMemResourceEx+0x12
fffffa60`27acdc20 00000000`74513d09 : 00000000`74513cc5 00000023`77300682 00000000`00000023 00000000`00000202 : nt!KiSystemServiceCopyEnd+0x13
00000000`1539ed48 00000000`74513cc5 : 00000023`77300682 00000000`00000023 00000000`00000202 00000000`1767d5e0 : wow64cpu!CpupSyscallStub+0x9
00000000`1539ed50 00000000`7457ab36 : 00000000`77120000 00000000`1539fd20 00000000`60c8f022 00000000`1539f450 : wow64cpu!Thunk0Arg+0x5
00000000`1539edc0 00000000`7457a13a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xa
00000000`1539edf0 00000000`771847c8 : 00000000`00000000 00000000`00000000 00000000`7efdf000 00000000`00000000 : wow64!Wow64LdrpInitialize+0x4b6
00000000`1539f350 00000000`771461be : 00000000`1539f450 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x1fba1
00000000`1539f400 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5202fc4d
STACK_COMMAND: .cxr 0xfffffa6027acd1d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
Followup: MachineOwner
7: kd> lmv m win32k
start end module name
fffff960`000d0000 fffff960`00389000 win32k (pdb symbols) c:\symcache\win32k.pdb\54B8C53009264F08A9D8CF1B4B56BCDC2\win32k.pdb
Loaded symbol image file: win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Thu Aug 08 04:02:53 2013 (5202FC4D)
CheckSum: 002B126B
ImageSize: 002B9000
File version: 6.0.6002.18912
Product version: 6.0.6002.18912
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 6.0.6002.18912
FileVersion: 6.0.6002.18912 (vistasp2_gdr.130807-1537)
FileDescription: Multi-User Win32 Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
7: kd> .cxr 0xfffffa6027acd1d0
rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa802800a288
r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
r14=000000001539ed50 r15=0000000000000001
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????

2008R2 server crash caused by srv2.sys, MS Netherlands SA support tells me to ..

Last night 1 of our 2008r2 sp1 Enterprise crashed and auto rebooted. With the debugger tool I checked the minidump and at the bottom it states:
Probably caused by : srv2.sys ( srv2+212e )
This is the SMB driver. There is a KB that acknowledges that there is a bug in this driver and a hot fix is available. However.. the date of the driver in the hotfix is older than the date of the driver in use by the server. Get my point? Should I install
the "older" hotfix or not.
This is the KB: http://support.microsoft.com/kb/2394911
I contacted MS SA support in the Netherlands and the literally stated that the server is now up and running so there is no problem hence they can not support this. Ridiculous. I told him that we have a server running that we can't rely on. They did not care..
I asked they guy to ask his manager and they just refuse to support me. Instead they sad I should contact a MS Partner because the question was about "implementation ".
Can you imagine that I not impressed at all by this...

Hello,
So it is a BSOD.
Please start by that:
Update all possible drivers
Uninstall all unused programs
Run chkdsk /r /f and sfc /scannow
Perform a clean boot: http://support.microsoft.com/kb/929135
Disable temporary all security softwares you have
Run memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
Once done, check results. If this does not help then use Microsoft Skydrive to upload dump files. Once done, post a link here.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Nvlddmkm.sys

Hello all this is my first posting:
I have a HP m8200n computer using Windows Vista, recently i tried to upgrade to the Microsofts SP2 update, then a power outtage happened, now the computer won't reboot entirely.
I am getting a message for nvlddmkm.sys after a crash dump it restarts and i can never get back into the login screen for my username.
Can someone please help me with this issue.
I also cannot use safemode it just keeps restarting, can i modify the bios or something?
any help is greatly appreciated.

Unfortunately yes, you does your motherboard have a integrated graphics card if so you may be able to remove your graphics card and plug into the integrated. That may be able to get you to the OS aso that you can see what is causing the issue. If that works then you may be able to get a new graphis card and it may work.
Brandon
Best Buy Associate | Geek Squad Agent
Forum Guidelines | Terms & Conditions | Community Guidelines | Blogging Guidelines
*Remember to mark your questions solved and click the star under the user's name to show your thanks!

Tracing complete, solution required bsod due to ACPI.sys

hi, hassaan here
i got a bsod today and i debugged it, the result i got, is you can find at:
https://skydrive.live.com/redir?resid=F80746862BC199FD!155&authkey=!AExsDmGkIac7haY&ithint=file%2c.txt
the main cause is ACpi.sys and showing reason, VISTA_DRIVER_FAULT;
i really required help, what is the cause and what solution is required.
awaiting for reply.
thanks.

Hi,
Please upload the source file to Skydrive, and then share to us.
Meanwhile, update all your drivers and then run sfc /scannow command:
Use the System File Checker tool to repair missing or corrupted system files
http://support.microsoft.com/kb/929833
Karen Hu
TechNet Community Support

Probably caused by : atikmdag.sys ( atikmdag+127f8 )

I just purchased a new HP ProLiant MicroServer G7 N54L
Here is a short history:
I replaced the 4GB ECC memory to 8GN non-ECC
I originally used a 25ft VGA cable on the on-board VGA port, but had a blue tinge, couldn't recognize the monitor properly, and a bluescreen shutdown, so I removed it.
There is nothing connected to the VGA port now
I now connect using RDP only
The computer freezes randomly and seems to happen when I launch the chrome browser (through RDP)
The dump files are at: https://onedrive.live.com/redir?resid=A19E045098FB769C!1399&authkey=!APLz-efriDf5wAs&ithint=file%2czip
According to my limited knowledge, it seems that the dump files indicate a video problem, but I am not completely sure. Can this be a problem with the motherboard?
Any help is greatly appreciated.

GG
These were related to your 5 year old video driver and may simply need a driver update. It is called a BCC116 and is either the driver or perhaps heat. I would start by removing the current driver and installing the newest driver available.
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\082614-25833-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0280a000 PsLoadedModuleList = 0xfffff800`02a4d890
Debug session time: Tue Aug 26 23:27:25.092 2014 (UTC - 4:00)
System Uptime: 8 days 2:58:31.684
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80093cd4e0, fffff88004cc57f8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+127f8 )
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80093cd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004cc57f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
STACK_TEXT:
fffff880`05a5f9c8 fffff880`05327134 : 00000000`00000116 fffffa80`093cd4e0 fffff880`04cc57f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`05a5f9d0 fffff880`05326e3e : fffff880`04cc57f8 fffffa80`093cd4e0 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05a5fa10 fffff880`04c0ff13 : fffffa80`093cd4e0 00000000`00000000 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05a5fa40 fffff880`04c39cf1 : 00000000`ffffffff 00000000`02ae8b02 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05a5fb20 fffff880`04c38437 : 00000000`00000102 00000000`00000000 00000000`02ae8b02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05a5fb50 fffff880`04c0b2d2 : ffffffff`ff676980 fffffa80`085ce010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05a5fbf0 fffff880`04c37ff6 : 00000000`00000000 fffffa80`08641830 00000000`00000080 fffffa80`085ce010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05a5fd00 fffff800`02b1b73a : 00000000`fffffc32 fffffa80`085cf610 fffffa80`06702040 fffffa80`085cf610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05a5fd40 fffff800`028708e6 : fffff800`029fae80 fffffa80`085cf610 fffff800`02a08cc0 fffff880`031b5801 : nt!PspSystemThreadStartup+0x5a
fffff880`05a5fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
SYMBOL_NAME: atikmdag+127f8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a8b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmdag.sys
FAILURE_ID_HASH: {7527b2fa-489f-c504-9452-1a10bd154401}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

0x7_8 stop error caused by NTFS.SYS , please help with dump file analysis

My 2003 server rebooted unexpected twice today and yesterday.
I've run Windbg to analysis the dump file, but i really don't know what to do next to resolve my problem.
Can any one give some suggestion? thanks in advance.
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: 0x7f_8_Ntfs+5f74
BUCKET_ID: 0x7f_8_Ntfs+5f74
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\temp\ads02 memory dump 20140218\MEMORY_20140217.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols.sympath
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_qfe.130703-1535
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8ee8
Debug session time: Mon Feb 17 08:37:34.653 2014 (UTC + 8:00)
System Uptime: 1 days 2:57:43.093
WARNING: Process directory table base BFF9C6C0 doesn't match CR3 005F2000
WARNING: Unable to reset page directories
Loading Kernel Symbols
Loading User Symbols
WARNING: Process directory table base BFF9C6C0 doesn't match CR3 005F2000
Unable to get PEB pointer
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80042000, 0, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Probably caused by : Ntfs.sys ( Ntfs+5f74 )
Followup: MachineOwner
0: kd> !analyze -v
*                        Bugcheck Analysis
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 0x28)
eax=00000000 ebx=8b4f1100 ecx=8ac87d03 edx=8687ddc0 esi=b83481a0 edi=b8348028
eip=f7addf74 esp=b8348000 ebp=b8348014 iopl=0         nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000             efl=00010202
Ntfs+0x5f74:
f7addf74 0000            add     byte ptr [eax],al          ds:0023:00000000=??
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from 00000000 to f7addf74
STACK_TEXT:
b8348014 00000000 00000000 00000000 00000000 Ntfs+0x5f74
STACK_COMMAND: .tss 0x28 ; kb
FOLLOWUP_IP:
Ntfs+5f74
f7addf74 0000            add     byte ptr [eax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs+5f74
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x7f_8_Ntfs+5f74
BUCKET_ID: 0x7f_8_Ntfs+5f74
Followup: MachineOwner

According to your post bug check 0x7F is recorded. Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
I suggest you check below link and troubleshoot it accordingly.
Bug Check 0x7F
Regards, Ravikumar P

Where is the form / forum to submit BSOD caused by Photoshop CS4 to the technical support ?

Where is the form / forum to submit BSOD caused by Photoshop CS4 to the technical support ?

But if it will make you feel better, the bug report form is here:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
As Bob said, though, this is generally a hardware/driver issue of some sort. I've just seen a case where some malware was causing BSOD when trying to run or install a scanner. When I got the malware off the machine the BSOD problem was instantly cured.

T410 NVIDIA BSOD caused by nvlddmkm.sys

Similar Messages

Maybe you are looking for