Tag Info

New answers tagged

0

Looks like this is a bug in Windows 8.1/2012 R2. Microsoft tries to fix this in May 2015 via Update or Hotfix.


0

according to EightForums in windows it is caused mostly by updates. Try uninstalling updates from last 2-3 weeks and you will see. also try running memory test to see if there is no issue with memory. and lastly check if you are booting in EFI mode or legacy. legacy mode can cause this as well with some help from updates.


1

The dump shows that the AMD AHCI driver causes the issue: ******************************************************************************* * * * Bugcheck Analysis * * ...


0

You get a memory corruption (1 Bit) in the file win32k.sys. This causes the crash: ******************************************************************************* * * * Bugcheck Analysis * * ...


2

You get the bugcheck 0xCA - PNP_DETECTED_FATAL_ERROR: PNP_DETECTED_FATAL_ERROR (ca) PnP encountered a severe error, either as a result of a problem in a driver or a problem in PnP itself. The first argument describes the nature of the problem, the second argument is the address of the PDO. The other arguments vary depending on argument 1. Arguments: Arg1: ...


0

This could be happening for a variety of reasons. Drivers - you mentioned this so I'll put it first, but make sure all the necessary system drivers are installed properly. Faulty equipment - Your GPU, Mobo, RAM, HDD, all can produce BSOD messages. Since you mentioned you've got it working before this probably isn't the problem. But in my experience most ...


0

Your extremely old AMD Athlon 64 3000+ seams to be damaged. You get a BUSLG_GENERIC_ERR_*_TIMEOUT_ERR error: ******************************************************************************* * * * Bugcheck Analysis * * ...


1

According to VMWare's site this is the answer: This issue is resolved in vSphere 5.0 Update 3. To work around this issue, manually create a CPUID mask for the affected virtual machines: To manually create a CPUID mask for the affected virtual machines: Power down the virtual machine. Right-click the virtual machine and click Edit Settings. Click the ...


0

Yes, you can analyze the dumps on other computers. Inside Windbg, click File->Symbol File Path or press CTLR+S. Now enter this into the dialog: SRV*C:\Symbols\Microsoft*http://msdl.microsoft.com/download/symbols This configures Windbg to download the required debug symbols (PDB files) from Microsoft symbol server. Now run .reload /f /v to load all ...


0

I change Windows7 HDD SATA port to 1,and problem solved.Because before I install and boot windows7,I changed SATA port.


1

IMHO there are two important things to know when analyzing a blue screen. a) As you found out: the PROCESS_NAME: fsgk32.exe If it cannot directly be associated with a product, a Google search will usually give some hints. You found out F-Secure, which Google also indicates. b) The type of the problem, which is KMODE_EXCEPTION_NOT_HANDLED in this case. ...


1

The extended test hangs at 21% of the first pass every time. This seems to be a problem other people have come across over time, but there isn't a satisfactory answer on the whole internet that I can find. I think the standard answer is replace the RAM in Slot 1 or Bank 1 (using 1-based math, and assuming 21% puts it in the first slot or pair of banks). ...



Top 50 recent answers are included