Dam this gotta suck, first, a windows 7 genuine-related problem, and now this POS BSOD...
Here's the error message AFTER the laptop is restarted due to the BSOD.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000047
BCP2: FFFFF80002CB85FC
BCP3: 0000000000000000
BCP4: FFFFFA80050A1C02
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\060411-18096-01.dmp
C:\Users\Heavenly\AppData\Local\Temp\WER-57548-0.sysdata.xml
this isn't the first time this happened. It happened to me a couple of months ago, but I don't know how I fixed it. Anyways that solution is a mere temporary one. Anyone know how I can fix this permanently? Ask for system specs if need. Thanks :]
Note: The BSOD ALWAYS pop up when I'm gaming. (I play Combat Arms only, just in case anyone needs to know what) It would appear randomly, like when I'm customizing my equipment or, when I'm in an actual game playing.
Monitor your temps next time you play the game, it could be overheating you laptop.
I have a thermaltake cooling fan under my laptop. The fan is like 200mm wide.. ( its one giant fan right in the middle of the pad under the laptop)
That doesn't guarantee no overheating.
The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.
[editline]5th June 2011[/editline]
Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.
Ah I see.. coincidentally I had just updated my driver and firmware for my Razer Deathadder 3500DPI mouse. I had suspected that it might be the problem, but I didn't wanna do anything about it until I get a verification. Thanks jordguitar :] really appreciated. However, today, I was about to game w/o an incident of the BSOD... if the BSOD pops up again, I'll follow your advice. Thanks again :D
Sorry, you need to Log In to post a reply to this thread.
