Persistant BSOD on Win 7 - HP Z210 Workstation

Hello folks,
I have a HP Z210 Workstation that has been an absolute problem child ever since I got it. Ever since I've had it, after a few weeks or normal use, it hits a BCOD, and then slowly, from there, becomes unusable until I have to reinstall the whole OS. I think
the problem may be on the video card (I've been testing it as much as someone without detailed technical knowledge can), but I'm not sure. HP Support thinks it may be hardware problem, but I can't identify the hardware that may have failed. Hopefully someone
here can help a bit.
The problem does seem to happen most frequently from sleep state - but, it doesn't always, which makes this trickier. I've attached the basic dump data here, and can try and upload the minidump and the sysdata.xml files if that would help.
I've run the length of my limited tech knowledge, and now I'm looking for a savior. Any help would be greatly appreciated.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8006979060
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA80075DFB70
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\100714-20638-01.dmp
C:\Users\Jon\AppData\Local\Temp\WER-44741-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

AFLB-J
We do need the actual log file (called a DMP file) as they contain the only record of the sequence of events leading up to the crash, what drivers were
loaded, and what was responsible.
We prefer at least 2 DMP files to spot trends and confirm the cause.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
If you are using Blue screen view, who crashed, or a similar application, don't. They are wrong at least as often as they are correct
Wanikiya and Dyami--Team Zigzag

Similar Messages

Cannot upgrade Exchange 2010 SP1 Management Tools to SP2 on Win 8.1 workstation

I have a Win 8.1 workstation that I am trying to update the Exchange Management tools on from 2010 SP1 to SP2. I get an error that says:
Error:
The following error was generated when "$error.Clear(); &RoleBinPath\ServiceControl.ps1 EnableServices Critical" was run: "AuthorizationManager check failed.".
The WMI service is being disabled and not starting back up after, causing the error. I have tried the following:
-Confirmed that the ExecutionPolicy is set to undefined/unrestricted for the localmachine
-Confirmed no GPO exists in our domain to restrict this
Every single time I run the install the WMI service switches to disabled and the localmachine Execution Policy is switched to RemoteSigned.
I have tried the Google search steps except for the Setup /M:Recoverserver since I really don't know what that would do to our Exchange environment. I have seen some posts that the Exchange 2010 MGMT tools are not supported on Win 8, which I find hard to
believe. I get no unsupported error just this incredibly frustrating error.
Any ideas?

What you are doing is totally unsupported:
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
By the way, Exchange 2010 sp1 and SP2 are no longer supported, the minimum supported is SP3.
http://social.technet.microsoft.com/Forums/en-US/b3085dd9-6777-454e-af30-279dfccffb8b/exchange-2010-sp1-and-sp2-are-no-longer-supported?forum=exchange2010
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

BSOD in Win 7 Pro

Hi,
      My system is getting crashed frequently due to Blue Screen of Death. When i checked blue screen logs this BSOD is getting triggered due to CAUSED BY DRIVER
tcpip.sys and CAUSED BY ADDRESS tcpip.sys+6a1e7. Below is the dump view
080514-13899-01.dmp   05-08-2014 12:59:56   DRIVER_IRQL_NOT_LESS_OR_EQUAL   0x000000d1   0x00000000   0x00000002   0x00000008   0x00000000
tcpip.sys   tcpip.sys+6a1e7                   32-bit   ntkrnlpa.exe+40b7f
    E:\SHARE\Minidump\080514-13899-01.dmp   4   15   7601   147,376   05-08-2014 13:00:37
Hardware is Lenovo Laptop with OEM Win 7 Pro 32 bit.
Any solution on this will be appreciated.
Thanks
Amit

Hi,
I've analyzed the latest dump files, and all indicate a Appfilt.sys error.
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Unable to load image \??\C:\Windows\system32\Drivers\Appfilt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Appfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for Appfilt.sys
*** WARNING: Unable to verify timestamp for scfdriver.sys
*** ERROR: Module load completed but symbols could not be loaded for scfdriver.sys
Probably caused by : Appfilt.sys ( Appfilt+24a1 )
Appfilt.sys (Application Name Filter Plugin) might be related with Third-Party Application, such as programs developed by Citrix Systems, do you have such kind of programs installed, uninstall and reinstall it, check if issue persists.
Virus or malware infection can also corrupted the appfilt.sys file or related Third-Party Application program files, so it's also recommended to perform a virus scan.
Make sure to install latest version for drivers, if you have recently changed some hardware or software configuration, make sure that your configuration is correct.
Yolanda Zhu
TechNet Community Support

Frequent BSOD in Win 7. Memory Mangement, PFN_LIST etc

Dear Expert,
I have frequent win7 BSOD. the details are loaded in my skydrive named - vy,.
I have a three year old computer running on Zotac motherboard. Local computer expert says time to change the motherboard. But no solid explanatione with him except that the onboard GPU chip heats(as per his estimation).
I am not so sure. Kindly analyse and let me know if I need a mobo change. I have got the hard drive formatted and did a clean reinsatall of Win 7 twice, but it is not helping. The crashes happen more when computer is stressed(no of browser windows, videos,
pictures etc. ) but restarts on its own. No data has been corrupted so far. I don't play games.
Please respond ASAP. I will be grateful.

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Consistent BSOD in Win XP after creating partition

I have a 13" MacBook. I've set it up with OS X 10.6.7 & Windows XP on a Bootcamp partition. I partitioned my OS X HD once again to create space for a OS X 10.7 Developer Preview Installation. Now, when I try to boot up the XP partition, the OS crashed with a BSOD everytime during the bootup animation. When I deleted the Lion partition, the XP loaded perfectly. Basically, the BSOD crops up everytime I partition the main OS X partition. Any help would be greatly appreciated.
Thanks,
Aditya Raghuwanshi

Hi,
when adding a partition after Windows installation with BootCamp you change the partitioning structure/numbering on which Windows relys to find its partition.
You have to edit the Windows XP boot.ini file so that it can find its partition again.
Or use a second Mac with BootCamp.
Regards
Stefan

MSO PRO-E 7522 BIOS confusion and persistent BSoD

Hi there
A few months ago I switched from 775 to 1366.
Components changed:
CPU (from Q9550 to i7 950)
MOBO (from Asus P5QL PRO to MSI PRO-E
RAM (From 8gb 800Mhz DDR2 to 12GB 1333Mhz DDR3 ADATA)
PSU (from Antec 550W to Cooler Master Ultimate 900W
+1 GFX card (Another ATI XfX 5870 Black Ed.)
I did not overclock the old system and I haven't overclocked my current system.
Now the thing is, I've been having bluescreens ever since I got that MSI PRO-E.
I've tried: switching RAM (since it said 1 was faulty), switched harddrives, reinstalled windows +/-6 times and looking for driver updates.
Now finaly I went looking at the BIOS.
Since I got a new PRO-E I remembered that I had no idea what version of the BIOS was running.
It seems that currently version 8.C0 is running.
Now I need to know if it matters that I've got the 8.xx BIOS version while running a crossfire setup.
Because I've read this:
Version 7.xx (7.3 is supposed to be the latest) supports Crossfire
Version 8.xx (8.E is supposed to be the latest) supports SLI.
Now I understand that 7.3 won't support SLI, only crossfire.
But does version 8.xx support both SLI AND Crossfire? Or am I simple messing up my computer because I've got a wrong BIOS version?
BSoD info:
problem continues to be caused by: ntkrnlmp.exe I think.
Well the first blue screen does not:
Loading Dump File [C:\Windows\Minidump\010711-24296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
Debug session time: Fri Jan 7 08:06:29.587 2011 (UTC + 1:00)
System Uptime: 0 days 0:29:44.806
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880048e3817, fffff88006ffd8e0, 0}
Probably caused by : atikmdag.sys ( atikmdag+90817 )
Followup: MachineOwner
Second blue screen:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010711-22531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Fri Jan 7 08:36:18.533 2011 (UTC + 1:00)
System Uptime: 0 days 0:28:46.626
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8000496e00, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
Followup: MachineOwner
I have also tried: registry cleaner countless times. though it sometimes did find stuff I don't think anything could relate to some shortcut which the program thought to be useless but was actualy referring to the windows debugging program. And even without regsitry faults (being detected) it crashed.
So I just need to knowL could it be my BIOS version + Crossfire = blue screen
If not.. any idea's?
Details system info:
OS: Microsoft Windows 7 Ultimate x64 (Tried with and without updates and service pak, these bluescreens are from this morning while I was @ school.
CPU: i7 950
Mobo: MSI PRO-E 7522
RAM: 12 GB ADATA 1333 DDR3 (listed as supported)
Graphics Cards:
ATI XfX 5870 Black Ed. 1GB.
ATI XfX 5870 6 Eyefinity Black Ed. 2 GB (as main card)
(I know, not an ideal combination but the 1gb card will be replaced)
2x 1TB Samsung Hard drives
PSU: Cooler Master 900-1080W
Casing: Cooler Master HAF922
System @ stock speed, I do not overclock!

Quote
Ah, ok so its already running at 1066?
Yes.
Quote
CPU-Z showed 530.5
CPU-Z always shows the real frequency. Because of the DDR architecture (Double Data Rate) there are two transactions per clock cycle. That means 530.5 MHz effectively translates to 530.5 x 2 = DDR3-1061 [~DDR3-1066]. The small difference (DDR3-1061 vs. DDR3-1066) can have two causes: The Base Clock Speed is either not set to 133 MHz in BIOS Setup and/or Spread Spectrum in Enabled and causes small clock speed deviations.
Quote
Then what would you have me do now?
Leave the memory frequency setting @DDR3-1066. It is better for testing anyway. You can worry about that later. The only thing you may want to check is the Base Clock speed (make sure it is set to 133 MHz in BIOS) and the Spread Spectrum setting (disable it).

Win 7 sp1 workstations losing contact with ZEN-servers

Lately we have seen more and more of this phenomenon that seems to have been described earlier but I cannot find any clear solution anywhere.
ZAA is 11.2.3.24691 MU1 or 11.2.4.3271. Happens to ws that are known to have been working ok. ZAA properties goes almost blank, except Agent status show correct IP-address, Device state Managed. Configuration location says Default location, should be something else. Server properties Unavailable, Closest servers no available, no policies, no bundles.
zac ref "completes" in half a second but nothing happens. If device still has the IP-address that was known to ZEN it shows up green, otherwise "Unable to connect...".
Wireshark shows little communication with ZEN-servers and only when ws uses same IP-address as is known to ZEN. A refresh produces no communication.
Here's whats in zmd-messages.log after a couple of refreshes:
[DEBUG] [03/12/2014 08:12:34.048] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ParseArgs] [] []
[DEBUG] [03/12/2014 08:12:34.064] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ProcessCommand] [] []
[DEBUG] [03/12/2014 08:12:34.064] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Processing Command for handler cache-clear] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Finished Processing Command for handler cache-clear. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ProcessCommand. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ParseArgs. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to StopDisplaySpinner()] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ParseArgs] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ProcessCommand] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Processing Command for handler refresh] [] []
[DEBUG] [03/12/2014 08:12:39.648] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [ResendLocationUpdate : -1] [] []
[DEBUG] [03/12/2014 08:12:39.726] [1428] [ZenworksWindowsService] [30] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Finished Processing Command for handler refresh. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ProcessCommand. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ParseArgs. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to StopDisplaySpinner()] [] []
[DEBUG] [03/12/2014 08:12:48.682] [1428] [ZenworksWindowsService] [33] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:11:00.435] [1428] [ZenworksWindowsService] [6] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:11:17.117] [3192] [ZenUserDaemon] [1] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:11:21.362] [3288] [explorer] [1] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:34:23.928] [1428] [ZenworksWindowsService] [10] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:34:29.511] [1428] [ZenworksWindowsService] [52] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:35:04.998] [1428] [ZenworksWindowsService] [34] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:36:50.438] [1428] [ZenworksWindowsService] [29] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
I sort of have the impression that ZAA actually is working (the services are running) but something else blocks the connection. However, Windows fw is closed and no av software is present.
Uninstall - reinstall of ZAA normally solves the problem, but this is not very practical and the situation can appear anytime on basically any ws, after which the ws remains in this state. The situation is particularly annoying on desktops with DLU, where the ws is practically useless in this state.

Originally Posted by wtbt
Lately we have seen more and more of this phenomenon that seems to have been described earlier but I cannot find any clear solution anywhere.
ZAA is 11.2.3.24691 MU1 or 11.2.4.3271. Happens to ws that are known to have been working ok. ZAA properties goes almost blank, except Agent status show correct IP-address, Device state Managed. Configuration location says Default location, should be something else. Server properties Unavailable, Closest servers no available, no policies, no bundles.
zac ref "completes" in half a second but nothing happens. If device still has the IP-address that was known to ZEN it shows up green, otherwise "Unable to connect...".
Wireshark shows little communication with ZEN-servers and only when ws uses same IP-address as is known to ZEN. A refresh produces no communication.
Here's whats in zmd-messages.log after a couple of refreshes:
[DEBUG] [03/12/2014 08:12:34.048] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ParseArgs] [] []
[DEBUG] [03/12/2014 08:12:34.064] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ProcessCommand] [] []
[DEBUG] [03/12/2014 08:12:34.064] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Processing Command for handler cache-clear] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Finished Processing Command for handler cache-clear. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ProcessCommand. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ParseArgs. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:34.126] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to StopDisplaySpinner()] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ParseArgs] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [Before call to ProcessCommand] [] []
[DEBUG] [03/12/2014 08:12:39.586] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Processing Command for handler refresh] [] []
[DEBUG] [03/12/2014 08:12:39.648] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [ResendLocationUpdate : -1] [] []
[DEBUG] [03/12/2014 08:12:39.726] [1428] [ZenworksWindowsService] [30] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [ZMD] [] [Finished Processing Command for handler refresh. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ProcessCommand. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to ParseArgs. Result = SUCCESS] [] []
[DEBUG] [03/12/2014 08:12:40.179] [1428] [ZenworksWindowsService] [30] [] [CLM] [] [After call to StopDisplaySpinner()] [] []
[DEBUG] [03/12/2014 08:12:48.682] [1428] [ZenworksWindowsService] [33] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:11:00.435] [1428] [ZenworksWindowsService] [6] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:11:17.117] [3192] [ZenUserDaemon] [1] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:11:21.362] [3288] [explorer] [1] [] [ZenCache] [] [SqliteConnection:Setting for Asynchronous IO operation to sqlite DB read from registry is null so setting it to default to true] [] []
[DEBUG] [03/12/2014 08:34:23.928] [1428] [ZenworksWindowsService] [10] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:34:29.511] [1428] [ZenworksWindowsService] [52] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:35:04.998] [1428] [ZenworksWindowsService] [34] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
[DEBUG] [03/12/2014 08:36:50.438] [1428] [ZenworksWindowsService] [29] [] [Settings Module] [] [Settings could not be refreshed on the device. Service Manager returned null on a call to enumerate services.] [] []
I sort of have the impression that ZAA actually is working (the services are running) but something else blocks the connection. However, Windows fw is closed and no av software is present.
Uninstall - reinstall of ZAA normally solves the problem, but this is not very practical and the situation can appear anytime on basically any ws, after which the ws remains in this state. The situation is particularly annoying on desktops with DLU, where the ws is practically useless in this state.
We seen this also on some workstation, zac cc, zac ref and then a restart usually solved it. Have not seen this error anymore after we updated to 11.2.4MU1.
Thomas

Logging on to Win 8.1 workstation with domain credentials

Hi All.
I been on Windows 8 Pro(now 8.1 update 1) for over a year now. Until now, I've always logged on to my workstation with my MS account. I recently decided to join my workstation to a domain where the Primary DC is running Server 2008 r2. I joined the domain
without a hitch, but when I try to log on to the workstation using domain credentials, the logon screen seems to insist on a MS account. It wants user name to be in email form only. When I tried to use my domain credentials in that format ([email protected])
it told me that the password is wrong and I should make sure to use my MS account password.
I tried disconnecting my MS account from my local account, but it didn't help.
Any ideas?

I'm not sure if what you are doing is supported, to have a local MS sign-in account as well as a corporate domain account residing side by side, you might have to give up your MS sign-in and use a local ID for the domain logon to work
you may however consider setting this up using the Workplace Join feature in 8.1 which should work much better
http://blogs.technet.com/b/keithmayer/archive/2013/11/08/why-r2-step-by-step-solve-byod-challenges-with-workplace-join.aspx

GT70 20D BSoD on win 8.1 - Nvidia driver

Hello,
I have several BSod (blue screen of death) under windows 8.1. (around one every days) i try to run driver verifier on ALL the drivers, one by one (it's take me few hours) and finally discover
that it's the driver for nvidia (nvlddmkm.sys exactly) that do all the time the BSoD ! (in driver verifier it's do BSoD few seconds after windows start)
I try everything possible, uninstalling nvidia driver (no more bsod but not perfect solution because compatible vga driver is used in place), using the last nvidia
driver (9.18.13.3182 but it's not work) and even the beta driver (not work either)
What the solution i have now ? is someone really have one GT70 20D and win8.1 with the laster nvidia driver without any BSoD ??
Also my win8.1 is a clean install from iso DVD
thanks by advance

Quote from: loki5100 on 03-January-14, 21:53:52
but i can't go to windows 8 ! the only previous version i can go (supported by our company) it's windows 7 ! but on the website on msi they said we can not update the bios with a windows 7 version when the bios was originally with a windows 8 version :( this can brick the laptop they say ... so what i can do ???
and sorry but when i read here :
http://www.msi.com/product/nb/GT70-2OD.html
it's clearly say it's work with Windows 8.1 !
So i buy it regarding this ! but it's false advertising because it's never work on windows 8.1 !
it's msi that choose to work with nvidia, so it's their responsibility to say that it's not compatible with windows 8.1 !
anyone with the windows 8.1 can try driver verifer on the nvidia driver to see that it's immediately crash after few minutes
First off, calm down. You're being rather irrational.
The BIOS doesn't matter if it's a Windows 7 or a Windows 8 BIOS. It will work with the OS. You can install Windows 7 perfectly fine on a GT70 20D with it having a Windows 8 or 8.1 BIOS. The bios doesn't effect the OS. The reason they state information regarding the OS is that GT70 0NX's can come with both Windows 7 or Windows 8 pre-installed. Those notebooks can only upgrade to the same BIOS that corresponds to the OS originally installed.
That being said, you don't seem to understand what I said. MSI cannot control NVidia's drivers. If the NVidia drivers don't work well with Windows 8.1, that doesn't mean the notebook is incompatible. The notebook runs Windows 8.1 just fine. The problem lies more with NVidia and the drivers provided for Windows 8.1. I've been over this a million times on many different websites, getting mad at MSI over NVidia's drivers is the same as getting mad at Microsoft for printer manufacturer's not putting out updated printer drivers for Windows 8.1. Microsoft can't control what those manufacturer's do. Get mad at them.
As zipper has said, it does work, but look at what he did...he went through many different versions of both the Intel and NVidia drivers. Most likely you will have to do the same. This is not something we can do for you, you're going to have to do it on your own.

Re: Satellite A200 (PSAE3E) Enabling Bluetooth cause BSOD using Win 7 64bit

Heallo,
I have a problem with Bluetooth in Satellite A200 (PSAE3E).
My operating system is Win7 Profwessional 64 bit.
When I'm installing a driver for BT system is making everything correctly, then restarting (after prompting).
When WiFi and BT switch is off everything is ok but after turning wireless connection with this switch after fiew second computer is showing dump memory and doesn;t want to work anymore... Restert helps until next turning on the switch on front panel.
What is wrong ? I was trying to install drivers, unistalling everything and installing...
Thank you for help.
Jan

Hi buddy,
Your posting is a little bit confusing I have checked the specifications on Toshiba website of Satellite A200 and some models are equipped with Bluetooth. What Satellite A200 model you have exactly and does it have Bluetooth model?
If yes I would try to reinstall the whole BT software. Uninstall, restart and install it again
Has Bluetooth worked on preinstalled Vista from Toshiba?

Persistent 205 Error (Win 7) when installing Creative Cloud Desktop

Please help. I am at wit's end here. I am getting a perpetual 205 error when trying to install the Creative Cloud Desktop App.
I've reviewed these forums and have tried everything:
Disabling firewalls, anti-virus, and anti-malware programs;
Clearing cache;
Logging on as a different Windows 7 user;
Dowloading under a different Adobe ID;
Three different web browsers.
I even tried using my phone as a mobile hotspot for a download to see if a different internet connection would work. No dice.
VERY frustrated with Adobe right now. Any help would be appreciated.

Click on the below link and download Lightroom cc 2015 installer file and install the Lightroom cc app :
http://trials3.adobe.com/AdobeProducts/LTRM/6/win64/Lightroom_6_LS11.exe
Same thing again :
Access Denied error ?
Open below link and then try to download Lightroom cc 2015 setup:
https://helpx.adobe.com/photoshop-elements/kb/photoshop-elements-10-11-downloads.html

Z87-gd45 Virtu MVP BSOD after win 8.1 update

Virtu MVP was working but broke with update to 8.1
Uniinstall this and it's "fixed".
Any patch incoming to get Virtu MVP working with 8.1?

Quote
will there be an official MSI update available for this?
Quote from: flobelix on 04-November-13, 02:01:52
>>How to contact MSI.<<
If MSI answers are unclear comtact them again.

BSOD Windows 8.1 System Service Exception (memory_corruption)

Hello,
I have a new computer with AMD processor and AMD Radeon R9 graphic card.
Several times a day, usually when I play a game I receive BSOD on Win 8.1 (with latest updates +
http://support.microsoft.com/kb/2818604 microcode Update for AMD procs+ latest AMD drivers).
Here from the dump:
FOLLOWUP_IP:
nt!MiGetVadWakeList+180
fffff802`48257740 488b11          mov     rdx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetVadWakeList+180
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52718d9c
IMAGE_VERSION: 6.3.9600.16452
STACK_COMMAND: .cxr 0xffffd00029a0eaf0 ; kb
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: 180
FAILURE_BUCKET_ID: 0x3B_nt!MiGetVadWakeList
BUCKET_ID: 0x3B_nt!MiGetVadWakeList
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_nt!migetvadwakelist
FAILURE_ID_HASH: {89f10555-061f-eab8-c95d-da0ab622d7bc}
Followup: MachineOwner
Full DUMP and last 2 mini dumps here :
https://skydrive.live.com/redir?resid=D618163590ABA072!3129&authkey=!AMS2YI4mfjMRRfc&ithint=folder%2c.dmp
Any input will he appreciated! Thanks!
I think it`s maybe the AMD drivers.. but have no idea how to further address this issue..

Hello,
Thanks,
Reinstalled AMD Drivers -issue still persists.
Updated Firmware for the 290 Card.
This particular error went away, however I still receive BSOD with another message which is related to Direct X?
: kd> !analyze -v
*                        Bugcheck Analysis
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffae0088bace0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8038d27851a, address which referenced memory
Debugging Details:
READ_ADDRESS: fffffae0088bace0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiUnlinkPageFromLockedList+35a
fffff803`8d27851a 483301          xor     rax,qword ptr [rcx]
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: witcher2.exe
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: ffffd0002a526f40 -- (.trap 0xffffd0002a526f40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00024053d0000000 rbx=0000000000000000 rcx=fffffae0088bace0
rdx=00fffff000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8038d27851a rsp=ffffd0002a5270d0 rbp=ffffd0002a527138
r8=fffffa800cbd0e60 r9=000000000024053d r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiUnlinkPageFromLockedList+0x35a:
fffff803`8d27851a 483301          xor     rax,qword ptr [rcx] ds:fffffae0`088bace0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8038d3607e9 to fffff8038d354ca0
STACK_TEXT:
ffffd000`2a526df8 fffff803`8d3607e9 : 00000000`0000000a fffffae0`088bace0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2a526e00 fffff803`8d35f03a : 00000000`00000000 fffffa80`08c1e880 ffffd000`2a526f00 ffffd000`2a526f40 : nt!KiBugCheckDispatch+0x69
ffffd000`2a526f40 fffff803`8d27851a : ffffc000`0fe7e201 fffff803`8d98e1e9 00000000`00000000 ffffa09c`b7fb0f31 : nt!KiPageFault+0x23a
ffffd000`2a5270d0 fffff803`8d3e9e85 : e3b00002`eb4d8b04 00000000`00000000 00000000`00000000 fffff680`00000004 : nt!MiUnlinkPageFromLockedList+0x35a
ffffd000`2a527160 fffff803`8d311b6e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff680`001a2010 : nt!MiActOnPte+0x529
ffffd000`2a5271c0 fffff803`8d3074c1 : 00000000`343d0000 ffffe000`06f2a900 00000000`343d0000 00000000`01000000 : nt!MiWalkVaRange+0x34a
ffffd000`2a527340 fffff803`8d5bba86 : 00000000`00000000 00000000`0010a000 00000000`00000000 7fffffff`fffffffc : nt!MiResetVirtualMemory+0x79
ffffd000`2a527380 fffff803`8d3604b3 : fffff900`00000020 00000000`00000080 00000000`000000c0 00000001`ffffffff : nt!NtAllocateVirtualMemory+0xba6
ffffd000`2a527580 fffff803`8d358900 : fffff800`015db414 ffffe000`06f2a900 ffffd000`2a5277c8 ffffc000`021cd880 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`2a527788 fffff800`015db414 : ffffe000`06f2a900 ffffd000`2a5277c8 ffffc000`021cd880 ffffe000`04bc4460 : nt!KiServiceLinkage
ffffd000`2a527790 fffff800`015d7e10 : ffffe000`00000404 ffffc000`00000000 00000000`0010a000 00000000`343d0000 : dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+0x88
ffffd000`2a5277f0 fffff800`015d7b39 : ffffd000`2a527960 fffff800`014127dc ffffc000`0878d6a8 ffffc000`1172c8b0 : dxgmms1!VIDMM_GLOBAL::ReclaimOneAllocation+0x290
ffffd000`2a5278f0 fffff800`01419f3d : ffffe000`009fa260 00000000`00000001 ffffe000`029ba000 ffffe000`003dbc50 : dxgmms1!VIDMM_GLOBAL::ReclaimAllocation+0x69
ffffd000`2a527930 fffff800`014717e9 : ffffc000`0878d640 ffffd000`2a5279f0 ffffd000`2a527b00 ffffc000`10829230 : dxgkrnl!VIDMM_EXPORT::VidMmReclaimAllocation+0x45
ffffd000`2a527960 fffff800`01471425 : ffffc000`10362000 ffffc000`10362000 00000000`00000001 00000000`1f590000 : dxgkrnl!DXGDEVICE::ReclaimAllocations+0x199
ffffd000`2a5279c0 fffff803`8d3604b3 : ffffe000`06926080 ffffc000`10362000 ffffc000`10362000 ffffe000`0678aa60 : dxgkrnl!DxgkReclaimAllocations+0x1b5
ffffd000`2a527a80 00000000`77cc77ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1f49e818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cc77ba
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+88
fffff800`015db414 4863d8          movsxd rbx,eax
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+88
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5277b2b7
IMAGE_VERSION: 6.3.9600.16455
BUCKET_ID_FUNC_OFFSET: 88
FAILURE_BUCKET_ID: AV_dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo
BUCKET_ID: AV_dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_dxgmms1!vidmm_process_heap::resetundo
FAILURE_ID_HASH: {7c538bc2-031b-7ae2-d86c-aa05a5a8b9ff}
Followup: MachineOwner
0: kd> lmvm dxgmms1
start             end                 module name
fffff800`0159a000 fffff800`015fb000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\7B195D90422146629D865602E8D4B39B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Nov 04 16:44:07 2013 (5277B2B7)
    CheckSum:         00063EA3
    ImageSize:        00061000
    File version:     6.3.9600.16455
    Product version: 6.3.9600.16455
    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:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.3.9600.16455
    FileVersion:      6.3.9600.16455 (winblue_gdr.131103-1206)
    FileDescription: DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Windows Overlay Filter (wof.sys), file in Windows 8.1, is associated with BSOD in Windows 10 bld 9879

BSOD in Win 10 build 9879 is with bug check 0x1e. Wof.sys is a file that is in Win 8.1. HP g7-1310us (refurbished) laptop has been having BSOD's even when it had Win 7 installed. Checked RAM, hardware, and SATA disk but there is no specific lead to why BSOD's
happen routinely. Interestingly, there were no problems while this laptop was running Ubuntu 14. Any details on what Windows Overlay Filter driver named wof.sys does? Also, could this error be caused by faulty CPU? It has an Intel i3-2350M CPU @2.3Ghz, x64
based processor.
==================================================
Dump File         : 121114-22984-01.dmp
Crash Time        : 12/11/2014 5:23:05 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000008
Parameter 4       : 00000000`00000000
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+1e40
File Description : Windows Overlay Filter
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.4.9879.0 (fbl_release.141103-1722)
Processor         : x64
Crash Address     : ntoskrnl.exe+161109
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121114-22984-01.dmp
Processors Count : 4
Major Version     : 15
Minor Version     : 9879
Dump File Size    : 282,776
Dump File Time    : 12/11/2014 5:26:16 PM
==================================================
Gilda Sanchez

Here is the CPU data:
Intel(R) Processor Identification Utility
Version: 5.01.20140910
Time Stamp: 2014/12/11 19:28:20
Operating System: 6.2-9200-
Number of processors in system: 1
Current processor: #1
Active cores per processor: 2
Disabled cores per processor: 0
Processor Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
Type: 0
Family: 6
Model: 2A
Stepping: 7
Revision: 29
Maximum CPUID Level: D
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache: 2 x 256 KB
L3 Cache: 3 MB
Packaging: µPGA/BGA
Enhanced Intel SpeedStep(R) Technology: Yes
MMX(TM): Yes
Intel(R) SSE: Yes
Intel(R) SSE2: Yes
Intel(R) SSE3: Yes
Intel(R) SSE4: Yes
Intel(R) AES-NI: No
Intel(R) AVX: Yes
Enhanced Halt State: Yes
Execute Disable Bit: Yes
Gilda Sanchez

BSOD Windows 7 32/64 bit - I will never buy a sb again

Creative knows the problem for years! And they are not able to fix the problem. What problem? The bluescreen of death you get when activating hw 3D audio in special games under Windows 7 32/64 bit. First I used the x-fi xtreme fidelity (2003) card under windows xp without any problem, than in 2009 I switched to windows 7. When playing my favourite game I got BSOD each time? I enabled the creative driver. I was searching for solutions, I read a lot and found out that many other x-fi users have the same problem. I had the hope that I could get rid of the problem by installation a newer x-fi card (titanium 2007, pci-e). But it didnt help. For 2 years I had to play in stereo mode. I thought all the time that creative will release a driver update. But nothing happenend. 2 days ago I had enough of playing in stereo mode, not being able to locate other players in game by their noices. I bought an Asus Xonar DS (not the newest card, from 2007), installed it, enabled the HW 3D audio settings with eax effects. No BSOD anymore! You know what, the sound is even much better. I can hear audio details I never noticed before in the game. Best 5. system I ever had.

I'm having BSOD under win 7 (64) with my x-fi gamer AND my old audigy 2 zs
It happens more when listening to music on youtube then when gaming and it sometimes happes on boot up.
I've checked all the other compontents to make sure it wasn't something else.
PC has been running smooth with onboard sound and neither of the cards gave any problems under XP or Vista (64)
Also the audigy 2 zs is working fine in my old pc.
Not sure where the problems is, ill give the beta drivers a shot. But it seems that alot of people are having problems with creative cards and windows 7

Persistant BSOD on Win 7 - HP Z210 Workstation

Similar Messages

Maybe you are looking for