1 Crash at win32k.sys with bugcheck of 50:
Quote:
|
The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
|
2 Crashes at win32k with a bugcheck of 0A:
Quote:
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Possible Resolutions:
• A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
• A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
|
sorry for the technical jargon, its harder to diagnose problems when core windows files are referenced (for me at least lol).
try testing your ram using
Memtest and let it run for at least 7 passes.
for some reason, windbg wouldnt open the last dump, im not sure why that happened.
Pay-as-you-go options starting at $10/user/month
05-29-2006
Driver IRQL Not Less or Equal
