Main Forum > General Computer Support
[SOLVED] BSOD 0x50 drivers windows 7
Boggin:
You could right click on it in Device Manager and select Uninstall then click on Action/Scan for hardware changes or just reboot, where it should reinstall perhaps with an older driver, but create a restore point first.
I have it on this Win 7 laptop upgraded to Win 10 and the driver is dated 29/09/2015 with the version 11.0.0.1007 and I've never had any BSODs because of that or anything else.
I see you've edited your last post - what did you do to get that error message ?
Angelika:
Windows 7 detects at the beginning of the installation as digitally signed.
This driver is digitally signed.
It's not true!
But when I try to install it, a pop-up window appears with this information.
I have tested all drivers, but I will force to unninstall this, each driver causes BSOD in random events.
There are no appropriate drivers on the internet, even on the manufacturer's website.
I want to Win7x64, not Win10x64.
Download Intel WDT Driver 11.0.0.1007 for Windows 10 64 bit
Not compatible with Windows 7!
https://www.catalog.update.microsoft.com/Search.aspx?q=watchdog
Boggin:
The Win 10 upgrade must have updated mine and I've just checked and it's Digitally Signed.
You may have to contact either your computer vendor if OEM build or Intel for legacy drivers.
It may not be that driver that is causing the BSODs but something else - what are you doing when you get the BSODs ?
Download BlueScreenView to see what it gives for your Memory Dump files.
http://www.nirsoft.net/utils/blue_screen_view.html
I'd suggest going into Device Manager or your computer support site to see if there are any updates for the Intel Chipset drivers - these may also update the WDT.
Angelika:
For example, BSOD occurs randomly when I try to uninstall or install any program. It does not matter what program (each)
Not always only sometimes.
Blue Screen View is a shit tool. Nothing shows.
Windbg is a better debugging tool.
PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050
--- Code: ---ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff8000325f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 59b946d1
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffffffffffffd0
FAULTING_IP:
nt+625b1
fffff800`032c15b1 f048830301 lock add qword ptr [rbx],1
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000334c70e to fffff800032cfe00
STACK_TEXT:
fffff880`037fc488 fffff800`0334c70e : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`037fc5f0 : nt+0x70e00
fffff880`037fc490 00000000`00000050 : ffffffff`ffffffd0 00000000`00000001 fffff880`037fc5f0 00000000`00000000 : nt+0xed70e
fffff880`037fc498 ffffffff`ffffffd0 : 00000000`00000001 fffff880`037fc5f0 00000000`00000000 00000000`00000020 : 0x50
fffff880`037fc4a0 00000000`00000001 : fffff880`037fc5f0 00000000`00000000 00000000`00000020 fffff8a0`00001670 : 0xffffffff`ffffffd0
fffff880`037fc4a8 fffff880`037fc5f0 : 00000000`00000000 00000000`00000020 fffff8a0`00001670 00000000`000007ff : 0x1
fffff880`037fc4b0 00000000`00000000 : 00000000`00000020 fffff8a0`00001670 00000000`000007ff fffffa80`09d36000 : 0xfffff880`037fc5f0
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt+625b1
fffff800`032c15b1 f048830301 lock add qword ptr [rbx],1
SYMBOL_NAME: nt+625b1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
--- End code ---
Boggin:
And you can analyse that can you ?
Is your computer set to create memory dump files ?
What have you done about looking for updates for your Chipset drivers ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version