Windows 7 Unknown Blue screen

M

MCalgar

New Member
Joined
Dec 28, 2012
Messages
40
Hi friends,

I've finally decided to ask you to help me because I'm really confused about a blue screen I recive. At first I thought the problem was an audio card I used to djing (I couldn't use it and it gave always a blue screen) but then, using a beta patch they released I could fix the problem. I'm explaining that because at first I always received the blue screen due to driver problems with this audio card.

But now, sometimes another blue screen appears, with the error 0x0...c4.
It seems to me that is because any hardware I have connected to the computer, also it only appears (or it is what I think) when I turn on the laptop, not after that.
I don't know, but it is really strange, because normally I turn on the laptop without anything connected, only the cooling pad. Could it be due to energy problems?

I attach all the files you ask for.

Thanks a lot.

Link Removed
 
Solution
If you've updated the video drivers and the problem still remains, then it's time (IMO) to try another video card.
If you have to purchase a new one, make sure that you purchase it from a place that will return your money if it's not needed.

Good luck!
Sort by date Sort by votes
Alcohol 120% (and Daemon Tools software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

The 2 latest errors are Driver Verifier errors. Have you enabled Driver Verifier? If not, please check to ensure that it's not enabled (and let us know). To do this, please open verifier.exe and select "Delete existing settings". Then click on "Finish" and reboot the computer for the changes to take effect.

Both memory dumps point to video drivers, so the next step (IMO) would be to:
- download a fresh set of the latest, Win7 compatible video drivers from the laptop manufacturer's website
- un-install the current video drivers
- install the freshly downloaded video drivers
- monitor for further BSOD's

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ASMMAP64.sys Thu Jul 2 05:13:26 2009 (4A4C7A36)
LENOVO ATK Hotkey ATK0101 ACPI UTILITY
Link Removed

kbfiltr.sys Mon Jul 20 05:21:42 2009 (4A643726)
Dritek Keyboard Filter Driver
Link Removed

AiCharger.sys Thu Sep 22 22:04:40 2011 (4E7BE938)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed



Analysis:
The following is for informational purposes only.
Code: 
[font=lucida console]**************************Mon Apr  1 04:47:24.163 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040113-27003-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:01:07.038[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1bb6c5 )[/B]
BugCheck [B]C4, {91, 2, fffff80003a4ecc0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80003a4ecc0
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc4_91_nvlddmkm+1bb6c5[/B]
CPUID:        "Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: [B]2294[/B]
  BIOS Version                  K55VD.203
  BIOS Release Date             03/12/2012
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar 31 04:38:54.598 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\033113-26145-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:04:04.473[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1bb6c5 )[/B]
BugCheck [B]C4, {91, 2, fffffa800d4ca3d0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa800d4ca3d0
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0xc4_91_nvlddmkm+1bb6c5[/B]
CPUID:        "Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: [B]2294[/B]
  BIOS Version                  K55VD.203
  BIOS Release Date             03/12/2012
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[font=lucida console]**************************Mon Apr  1 04:47:24.163 2013 (UTC - 4:00)**************************
[COLOR=RED][B]ASMMAP64.sys                Thu Jul  2 05:13:26 2009 (4A4C7A36)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]kbfiltr.sys                 Mon Jul 20 05:21:42 2009 (4A643726)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
Rt64win7.sys                Tue Aug 23 09:55:41 2011 (4E53B15D)
atkwmiacpi64.sys            Tue Sep  6 21:44:52 2011 (4E66CC94)
[COLOR=RED][B]AiCharger.sys               Thu Sep 22 22:04:40 2011 (4E7BE938)[/B][/COLOR]
athrx.sys                   Tue Oct  4 02:49:29 2011 (4E8AAC79)
AsusVBus.sys                Tue Nov  1 03:24:17 2011 (4EAF9EA1)
AsusVTouch.sys              Mon Nov  7 06:48:23 2011 (4EB7C587)
iaStor.sys                  Tue Nov 29 22:39:19 2011 (4ED5A567)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
aex7x5ug.SYS                Wed Dec 28 04:10:52 2011 (4EFADD1C)
iusb3hub.sys                Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys                Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3hcs.sys                Fri Jan 27 04:37:23 2012 (4F227053)
RtsBaStor.sys               Wed Feb  1 03:06:18 2012 (4F28F27A)
RTKVHD64.sys                Tue Feb 14 05:55:35 2012 (4F3A3DA7)
igdkmd64.sys                Tue Feb 14 13:47:30 2012 (4F3AAC42)
ETD.sys                     Mon Feb 20 05:11:23 2012 (4F421C4B)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys                Sat Feb  9 18:13:08 2013 (5116D804)
nvpciflt.sys                Sat Feb  9 18:13:33 2013 (5116D81D)
aswRvrt.sys                 Wed Mar  6 18:21:43 2013 (5137CF87)
aswVmm.sys                  Wed Mar  6 18:21:46 2013 (5137CF8A)
aswFsBlk.SYS                Wed Mar  6 18:22:01 2013 (5137CF99)
aswMonFlt.sys               Wed Mar  6 18:22:08 2013 (5137CFA0)
aswTdi.SYS                  Wed Mar  6 18:22:10 2013 (5137CFA2)
aswrdr2.sys                 Wed Mar  6 18:22:24 2013 (5137CFB0)
aswSP.SYS                   Wed Mar  6 18:23:05 2013 (5137CFD9)
aswSnx.SYS                  Wed Mar  6 18:23:10 2013 (5137CFDE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar 31 04:38:54.598 2013 (UTC - 4:00)**************************
aliwbw67.SYS                Wed Dec 28 04:10:52 2011 (4EFADD1C)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aex7x5ug.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswRvrt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
aswVmm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
aswrdr2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
aliwbw67.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
Upvote 0 Downvote
thanks! =)

AS I understand, I should focus in the first part of your answer, right? Second and third part are there only for information, am I right?
I'll do these updates asap, and I will reply with the results. Do you want me to post the results with the differents programs I used to test/find the errors in my computer?

PD: I didn't remember to say that I have two SO in my computer, two Windows 7 installed, don't know if it's important.
 
Upvote 0 Downvote
Everything after this can be ignored:
Analysis:
The following is for informational purposes only.
Click to expand...
I include it for both my information (when reviewing your subsequent posts) and for those who might be interested in some of the reports that I get my info from.

**********************************
After that, all the stuff from the top down is done in the order that I review the reports - it has no specific sequence of importance. The reason for this is that the actual cause may not be obvious - so fixing it all (or as much as possible) is what we'd like to see.

In this case I think it's the Alcohol/Daemon Tools software - but the Driver Verifier memory dumps threw us a curve ball. So we have to check out both of them.

Older drivers can also cause problems, so we routinely ask you to update those that are older than the last release of a major change to that Operating System.

No need to post updates on the individual tasks - unless you have a problem with them. What happens next is we wait and see if you get any more BSOD's. If you do, run the data collection tool again and attach it to the next post.
 
Upvote 0 Downvote
Just to add on;
The two provided dumps point to nvlddmkm.sys, or, your NVIDIA drivers (Graphic, 3D, PhysX whatever they may be) - it would be better to update those drivers from: Drivers | GeForce
This is because computer manufacturers tend to upload outdated drivers to their support sites, and as a rule of thumb the later the driver the better performance it gives.

By all means follow John's analysis and suggestions first, I'm just giving a tip that I've seen happen to other people.
 
Upvote 0 Downvote
then I have a question, when I update drivers, do I have to update them in the two systems, or only in one? I think it's in both, but then I should post another report from the second so, right?
 
Upvote 0 Downvote
I was unaware that this was from 2 different systems.
Each problem is different - even if the systems are very similar.
Please start a new topic for the other system and submit a set of reports for that
 
Upvote 0 Downvote
usasma said:
I was unaware that this was from 2 different systems.
Each problem is different - even if the systems are very similar.
Please start a new topic for the other system and submit a set of reports for that
Click to expand...

ok, I'll do it asap =)

anyway, I can follow with your instructions for the first SO?
 
Last edited:
Upvote 0 Downvote
I'm afraid that I'm confused.
Is this just one computer with 2 OS (Operating System) installed?
Or is it 2 different computers?

If the reports only came from one Operating System, then you can perform those "fixes" on that Operating System.
 
Upvote 0 Downvote
hi, sorry for the confusion

is one computer with 2 OS. The report I'veposted in this thread comes from one OS, the other report I've posted today comes from the 2nd OS
 
Upvote 0 Downvote
hey! I attach the minidump files of this SO, hope it'll help, 'cause today I've received again the blue screen.

I don't know but, could it be related to a cooler I have connected to the computer via usb? Maybe something related to energy problems or whatever.

thanksLink Removed
 
Upvote 0 Downvote
Still blames video and still says that Driver Verifier is enabled.
Have you run the Video Stress tests that I suggested? If so, what were the results?
As this is a laptop, please be sure to blow out the air vents with canned air (DO NOT use a vacuum or an air compressor as they can damage parts). Then, be sure to use the laptop on a hard surface (and use a laptop cooling pad if possible).

It appears that this laptop has a discreet nVidia graphics card, so you may be able to get it replaced. Prices that I saw were from $70 to $130 US.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

kbfiltr.sys Mon Jul 20 05:21:42 2009 (4A643726)
Dritek Keyboard Filter Driver
Link Removed

AiCharger.sys Thu Sep 22 22:04:40 2011 (4E7BE938)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed

sptd.sys Sat Aug 18 17:05:38 2012 (503003A2)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
Link Removed



Analysis:
The following is for informational purposes only.
Code: 
[font=lucida console]**************************Sun Apr 28 04:50:57.703 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042813-37377-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:59.577[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1bb8c5 )[/B]
BugCheck [B]C4, {91, 2, fffff80003a5acc0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80003a5acc0
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc4_91_nvlddmkm+1bb8c5[/B]
CPUID:        "Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: [B]2294[/B]
  BIOS Version                  K55VD.203
  BIOS Release Date             03/12/2012
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Apr 27 11:12:01.416 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042713-28704-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:04:13.290[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1bb8c5 )[/B]
BugCheck [B]C4, {91, 2, fffffa800d4a74c0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa800d4a74c0
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0xc4_91_nvlddmkm+1bb8c5[/B]
CPUID:        "Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: [B]2294[/B]
  BIOS Version                  K55VD.203
  BIOS Release Date             03/12/2012
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[font=lucida console]**************************Sun Apr 28 04:50:57.703 2013 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]kbfiltr.sys                 Mon Jul 20 05:21:42 2009 (4A643726)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
Rt64win7.sys                Tue Aug 23 09:55:41 2011 (4E53B15D)
atkwmiacpi64.sys            Tue Sep  6 21:44:52 2011 (4E66CC94)
[COLOR=RED][B]AiCharger.sys               Thu Sep 22 22:04:40 2011 (4E7BE938)[/B][/COLOR]
athrx.sys                   Tue Oct  4 02:49:29 2011 (4E8AAC79)
AsusVBus.sys                Tue Nov  1 03:24:17 2011 (4EAF9EA1)
AsusVTouch.sys              Mon Nov  7 06:48:23 2011 (4EB7C587)
iaStor.sys                  Tue Nov 29 22:39:19 2011 (4ED5A567)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
iusb3hub.sys                Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys                Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3hcs.sys                Fri Jan 27 04:37:23 2012 (4F227053)
RtsBaStor.sys               Wed Feb  1 03:06:18 2012 (4F28F27A)
RTKVHD64.sys                Tue Feb 14 05:55:35 2012 (4F3A3DA7)
igdkmd64.sys                Tue Feb 14 13:47:30 2012 (4F3AAC42)
ETD.sys                     Mon Feb 20 05:11:23 2012 (4F421C4B)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
aswRvrt.sys                 Wed Mar  6 18:21:43 2013 (5137CF87)
aswVmm.sys                  Wed Mar  6 18:21:46 2013 (5137CF8A)
aswFsBlk.SYS                Wed Mar  6 18:22:01 2013 (5137CF99)
aswMonFlt.sys               Wed Mar  6 18:22:08 2013 (5137CFA0)
aswTdi.SYS                  Wed Mar  6 18:22:10 2013 (5137CFA2)
aswrdr2.sys                 Wed Mar  6 18:22:24 2013 (5137CFB0)
aswSP.SYS                   Wed Mar  6 18:23:05 2013 (5137CFD9)
aswSnx.SYS                  Wed Mar  6 18:23:10 2013 (5137CFDE)
nvlddmkm.sys                Thu Mar 14 21:37:00 2013 (51427B3C)
nvpciflt.sys                Thu Mar 14 21:37:25 2013 (51427B55)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswRvrt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
aswVmm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
aswrdr2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
 
Last edited:
Upvote 0 Downvote
hi! I'm almost sure that the problem is the video card, because when I open the hardware window in "my Computer", it appears that the video has a problem, that windows has detected. what could I do?

thanks
 
Upvote 0 Downvote
If you've updated the video drivers and the problem still remains, then it's time (IMO) to try another video card.
If you have to purchase a new one, make sure that you purchase it from a place that will return your money if it's not needed.

Good luck!
 
Upvote 0 Downvote
Solution

Actually when I reinstall the drivers, I found that there's a problem with one of the components of the driver, something called "video Physx" or something similar, could it be the problem?

Because it seems that the video driver installs correctly.
 
Upvote 0 Downvote
I don't have any knowledge about that depth of detail in video cards. I'd suggest posting over in the hardware forums - or in the nVidia forums for more expert advice.
 
Upvote 0 Downvote
usasma said:
I don't have any knowledge about that depth of detail in video cards. I'd suggest posting over in the hardware forums - or in the nVidia forums for more expert advice.
Click to expand...

ok, many thanks for all your help =). nice to see that there're people like you

thanks for all ^^
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
Resolving the Blue Screen of Death (BSOD) in Windows: Causes & Fixes
Replies
0
Views
89
ChatGPT
  • Featured
  • Article Article
Windows 11 24H2 Update Urgency: Gamers Face Crashes and Blue Screen Issues
Replies
0
Views
96
ChatGPT
  • Featured
  • Article Article
Windows 11 September Update KB5043145: Reboot Loops and Blue Screens
Replies
0
Views
63
ChatGPT
  • Featured
  • Article Article
KB5043145 Update Chaos: Windows 11 Users Face Blue Screens and Reboots
Replies
0
Views
109
ChatGPT
  • Solved
Fixing CrowdStrike Blue Screen of Death (BSOD) | Automated Script Solution
Replies
2
Views
584
Neemobeer