Your windows is crashed at win32k.sys and it is windows GDI routine. The culprit maybe faulty ram, video device driver or firewall. As you only...
The 2nd dump is exactly same as the 1st dump. Most likely the culprit is bxvbdx.sys (Broadcom NetXtreme driver). Upgrade or fallback the device...
One mimidump is insufficient to confirm the root cause. If you have 3 to 5 minidumps and all of them are crashed at the same module. The failing...
Hardware problem The most debug information of your problem is 0xC000001D which means IP misalignment. This is the symptom of hardware problem....
http://support.microsoft.com/default.aspx?scid=kb;en-us;901150
If it is hardware problem, the minidump have different symptoms. Software errors always have consistent symptoms. The failing hardware maybe CPU,...
The latest crash is also related to faulty ram. Try reseating the ram and clean up dust inside the ram slot. If it still crashes, replace the ram.
2 minidumps are crashed due to memory corruption. This culprit is ram. Reseat the memory module to another ram slot may resolve the blue screen.
The debug report is incomplete as there have no module list. Please attach the complete debug report. From the stack trace, I believe it is...
Your windows is crashed at win32.sys and it is GDI (graphical Display routine) and your version nVidia Display Card has known software problem....
Your debug report is the user.dmp and not the minidump. Minidump is used for diagnostic BSOD problem and user.dmp is used for diagnostic...
According to the debug report, bxnd52a.sys is the culprit. One minidump is insufficient to conform the root cause. Attach more debug reports here...
The debung report is incomplete as it does not have module list and it is very useful to find out the root cause of the problem. The crash was...
Your Norton AV is at year 2004 and it has known software problem. You had better upgrade or de-install Norton AV. Does your server install HP USB...
Yes, emu10k1m has known software problem. Upgrade the sound card driver. Refer the following problem...
lm tn is windbg subcommand. It is typo error and ! is not required . You must issue windbg and enter lm tn
Your debug report is incomplete, the output of !analyze has the module list and you only attach the first half of the debug report. If you suspect...
The first dump is crashed with bugcheck 0A with IRQL x'1c' and this is the symptom of hardware error. The second dump has "Mini Kernel Dump does...
Can you attach the output of !lm tn of the last minidump here? It is very useful to find out the culprit of the problem.
The problem maybe related to faulty ram. BTW your windows has two software and their version has known software problem and they are daemon tools...
Separate names with a comma.
