BSOD BCCode 1e

[Billsy]

System Specs:

Intel Quad Core Q8400 @2.66Ghz
Nvidia Geforce GTS 450
MSI G41TM-P31
4GB DDR2 PC2-6400
1TB Samsung HDD
Corsair TX 500W PSU
Windows 7 Home 64-Bit

Hello there, I have been having a lot of BSOD problems for the past month or so which coincided with when I purchased Arma II for the popular DayZ mod. I don't know if this is a coincidence or the route of the problem. I'm experiencing:

Random BSOD
Random freezing (I might be web browsing and listening to music and then my computer will freeze and cease my computer to function)

I've tried a lot to resolve the problem, such as performing checks through Windows such as checking memory, performing system restore, resolving problems on startup etc. Below I have created a .rar file as listed in the stickied thread.

Thanks in advance.

 

[James7679]

Hello Billsy. Welcome to Seven Forums.

This looks like a memory issue. Please, test your http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Also, there have been 4 BIOS revisions since your current was released. It may not be necessary to update your BIOS. There are some stability issues addressed though. If you choose to update your BIOS, you do so at your own risk. MSI Global ? Mainboard - G41TM-P31

 

[James7679]

Billsy, were you able to resolve this? If so, please mark the thread as solved.

 

[Billsy]

Hello, no it hasn't been resolved yet. I haven't ran the memtest yet as I haven't had the chance but I have ordered more RAM as I knew it needed upgrading anyway and so if that is the cause of the problem it will be rectified when it arrives and I have had chance to install it. However, I do continue to get BSOD and I noticed that some of the BCCodes are new ones that I haven't seen before, do you mind looking at the new logs please? I also recieved a message on startup "Cmos checksum bad" I don't know if that has anything to do with the problem but that has never occured before. I appreciate the help.

Thankyou.

 

[James7679]

Your crash reports indicate a possible problem with your Windows installation. Please follow the Windows Genuine and Activation Issue Posting Instructions. Post the results in your next post; do not start a new thread.

NOTE: The MGADIAG report does not contain any sensitive or personal information, and is best posted un-edited for us to be able to help.

7. Select (highlight) all of the MGADiag report that you just pasted, and click on the code box # toolbar icon to wrap the report in a code box when posted. (see screenshot below)

View attachment 218732

Thank you,

James

Please do the above.

 

[Billsy]

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-J82F3-2JTVV-733D2
Windows Product Key Hash: 5UR6fwI9xv2haR/sC+0a+rfixxo=
Windows Product ID: 00359-OEM-8992687-00236
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {EA8E52D6-3214-4A06-85C6-7301DE2B6B39}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{EA8E52D6-3214-4A06-85C6-7301DE2B6B39}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-733D2</PKey><PID>00359-OEM-8992687-00236</PID><PIDType>2</PIDType><SID>S-1-5-21-2511612708-356393647-2880048203</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MJ-7592</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.10B2</Version><SMBIOSVersion major="2" minor="5"/><Date>20100921000000.000000+000</Date></BIOS><HWID>96053E07018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>cmscom</OEMID><OEMTableID>zoostorm</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800236-02-2057-7600.0000-3072010
Installation ID: 013454469796456214823370002794473711615386594710649072
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: 733D2
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 28/06/2012 15:11:31
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x80072EE7
HealthStatus: 0x0000000000000000
Event Time Stamp: 6:1:2012 16:25
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:

HWID Data-->
HWID Hash Current: MAAAAAEABAABAAEAAAABAAAAAQABAAEA6GGOFPyLqnZI5PxTEItyeoQf9oXUy0xY
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name OEMID Value OEMTableID Value
  APIC   7592MJ  A7592100
  FACP   7592MJ  A7592100
  HPET   7592MJ  OEMHPET 
  MCFG   7592MJ  OEMMCFG 
  SLIC   cmscom  zoostorm
  OEMB   7592MJ  A7592100
  GSCI   7592MJ  GMCHSCI 
  SSDT   DpgPmm  CpuPm

 

[James7679]

Billsy, when did you build this computer?

 

[Billsy]

I didn't build it, I brought it, why? It's about 2 years old I think.

 

[James7679]

I didn't build it, I brought it, why? It's about 2 years old I think.

No, it's okay, just checking something.

I also recieved a message on startup "Cmos checksum bad" I don't know if that has anything to do with the problem but that has never occured before.

With this error. Please explain, step by step your encounter with this error. When did it happen, were you able to boot, how were you able to get past this?

Also, your current BCCode is x7f_8 It looks like we are dealing with a hardware issue here. Given the cmos eror, this makes it even more likely. You need to run Memtest86 as already advised.
RAM test with Memtest86+
Certain Bug Check Codes(BCCodes) or combination of BCCodes, are indicative of faulty RAM. Memtest86+ is an offline program specifically written to test RAM and uncover errors. Memtest86+ tries to verify that the RAM will accept and correctly retain arbitrary patterns of data written to it, and that there are no errors where different bits of memory interact, and there are no conflicts between memory addresses. Memtest86+ is open source, which means it is free to use.

Systems may have one or more sticks of RAM. These individual sticks are called DIMM. If Memtest86+ finds ANY errors, most likely, you have defective RAM. There are some cases where the DIMM slot, themselves, can be bad.

**Important!**
Should you receive any errors during the tests, stop the test. You will need to test each stick independently in each DIMM slot. Follow proper ESD Safety! Remove all but the first stick. Resume testing. If you receive(or dont) errors, note on a piece of paper that DIMM 1 failed(or passed) in Slot A1. Stop the test, move the stick to slot A2, resuming testing and taking notes in this manner, until all DIMMs have been tested in all DIMM slots.

** Memtest86+ V4.20 (25/01/2011) **
​

• Download - Pre-Compiled Bootable ISO (.gz)
• Download - Pre-Compiled Bootable ISO (.zip)
  
  
• Download - Pre-Compiled Bootable Binary (.gz)
• Download - Pre-Compiled Bootable Binary (.zip)
  
  
• Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*
• Download - Pre-Compiled package for Floppy (DOS - Win)
  
  Above download links are directly from Memtest.org
  
  

Should you need more help with any of the testing or setting up for it, you may either post back with any questions, or refer to our tutorial here http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Billsy]

The "cmos checksum bad" error came up once and stated that a flashdrive was required in order to flash the bios which you have already stated might be required although not definitely. I got around this by just letting my PC search for a flash-drive which wasn't present and then reset my computer and the error didn't occur again. I've ordered further RAM and plan on flashing my bios to the latest version. Which would I go about doing first? Implement the new RAM and then flash the bios or vice-versa?

Thankyou once again.

 

[James7679]

You should, first, check the RAM you currently have. If there is nothing wrong with your RAM, and we find that the problem is the CPU or Motherboard, you will want to return the RAM you bought. Seriously, run Memtest86 first, now. Please follow the instructions I have given you.

Thanks,

James

 

[Billsy]

Hi James, I finally got around to running the memtest and left it on for around 7 hours, and recieved 8 passes with no errors. Given what you've said previously and given the results, it seems as though the RAM isn't the issue. I've had a few more crashes since my last post, and I can upload the reports for further examination if you deem it useful.

You mentioned that it could be something to do with the operating system, it's funny that you mentioned that as today, one of the problems I encountered was that when attempting to access the computer, my desktop wouldn't load, I did get an error prior to entering my password and being able to view my desktop (which was blank and all shortcuts were not visible). Unfortunately I can't remember what the error actually said. This problem only occured once and when I reset the computer and switched it back on, my desktop seemed fine. Could this possibly be linked the BSOD occuring?

You also mention flashing the bios? I've not done that since I stopped the memtest, would you suggest doing so?

I cannot upload the new reports at present as i'm using a different computer, if it would be helpful, I will do so as soon as you have replied.

Thanks for your time once again, hopefully I can finally resolve the problem in the near future.

 

[Billsy]

I've took note of the text that occurs at the top left of my screen when a BSOD occurs, the text that was displayed when the last BSOD occured read "IRQL_LESS_OR_NOT_EQUAL" if that helps.

 

[Billsy]

Although I haven't recieved a reply yet, here are the dump files:

 

[Billsy]

I have a feeling it might be my operating system. When attempting to turn on my computer today, it randomly restarted twice, I did a system restore, but it's since occured once more, as my entire computer froze at my desktop and so I had to switch off power at the mains. I would appreciate any comment by you experts to just confirm/reiterate the cause of the problem. I know it's definitely not the RAM and Graphics Card, which leaves th motherboard, CPU and my operating system as potential causes of the freezing and BSODs.

Thanks in advance.

 

[writhziden]

System Specs:

We know very little about your system. If you need help, please fill in your system specs in your profile and not in a post in this thread: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

Hardware Compatibility:

Also, we should check hardware compatibility:

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.​

Analysis:

Given the wide variety of BugCheck codes, this appears to be a hardware problem. Before giving steps to troubleshoot your hardware, may I ask if you have done the BIOS update/re-flash yet?​

 

[Billsy]

System specs I have done as requested, please refer to my profile.

I have provided screenshots of CPU-Z and no I haven't flashed the bios yet.

Thankyou for your assistance, I look forward to your response.

 

[FredeGail]

Hello Billsy,

You should take advantage of Writhziden's and James' suggestions first off, but I thought I'd add a little.

BSOD Analyse

Update/Uninstall these drivers

s616bus      Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          81,920     0      03/04/2007 15:36:46    C:\windows\system32\DRIVERS\s616bus.sys          4,096     
s616mdfl     Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          8,192      0      03/04/2007 15:38:54    C:\windows\system32\DRIVERS\s616mdfl.sys         4,096     
s616mdm      Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          118,784    0      03/04/2007 15:39:07    C:\windows\system32\DRIVERS\s616mdm.sys          4,096     
s616mgmt     Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          102,400    0      03/04/2007 15:41:06    C:\windows\system32\DRIVERS\s616mgmt.sys         4,096     
s616nd5      Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          16,384     0      03/04/2007 15:35:14    C:\windows\system32\DRIVERS\s616nd5.sys          4,096     
s616obex     Sony Ericsson Device 6 Sony Ericsson Device 6 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          98,304     0      03/04/2007 15:43:03    C:\windows\system32\DRIVERS\s616obex.sys         4,096

You have a large amount of old Sony Ericsson drivers. I recommend to uninstall or update them by the looks of it.

http://www.carrona.org/drivers/driver.php?id=s616obex.sys
http://www.carrona.org/drivers/driver.php?id=s616nd5.sys
http://www.carrona.org/drivers/driver.php?id=s616mgmt.sys
http://www.carrona.org/drivers/driver.php?id=s616mdm.sys
http://www.carrona.org/drivers/driver.php?id=s616mdfl.sys
http://www.carrona.org/drivers/driver.php?id=s616bus.sys

WacomPen     Wacom Serial Pen HID D 
Serial Pen HID D Kernel        Manual     Stopped    OK         FALSE       FALSE        9,856      8,448      0      14/07/2009 01:02:07    C:\windows\system32\DRIVERS\wacompen.sys         2,176

The Wacom driver is a known BSOD causer. Consider finding Q&A's, updates, or fixes for this device. Also do not use the driver that came with the drive, it's usually old.

Wacom Drivers

Memory

If Memtest86+ gave no errors, it's likely a driver. We'll probably proceed to Driver Verifier once you have had your BIOS updated as it contains stability fixes as James mentioned, and after you've dealt with the mentioned drivers above.

SFC Command

We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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: 0000000000000010, 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: fffff800030c8fe0, address which referenced memory

Best Regards,
Frederik.

 

[Billsy]

Hi FredeGail, I've done as you suggested and removed all of those drivers listed. I ran the SFC Command yesterday and the day before without any problems and errors arising. With regards to the Wacom Driver, it's a driver for tablets as far as I can gather, I don't have a tablet. I've located the driver in this directory (C:\windows\system32\DRIVERS\wacompen.sys) Can I simply delete it here or will it appear like the other drivers in Device Manager?

Thankyou for your time, I will repost if I encounter any further problems such as any more BSODs.

 

[FredeGail]

Hello again Billsy.

God call on the allocation at %root\system32\DRIVERS\wecompen.sys. Have you never had this tablet before? Maybe you've used it before, borrowed it from some friends and just plugged it out again.

Safely Remove Drivers:
To remove this safely, please do the following:
- ensure that you have a bootable DVD to use to get into Startup Repair (the Win8 installation DVD will do). If you don't have one, then use this procedure to create a System Repair disk: System Repair Disc - Create in Windows 8
- set a System Restore point (to use with the System Repair disk if you can't get back into Windows).

- download this free program: Autoruns for Windows Use it to disable any entries that name the wacompen.sys driver or the Wacom Software (by removing the checkmark in the far left column)
- check for any services related to this driver and/or program (use services.msc) and disable them
- check in Device Manager (use devmgmt.msc) for any devices related to this driver and/or program. Make sure to enable the viewing of hidden devices. Uninstall any that you find. DO NOT rescan or reboot yet!
- search your system for the wacompen.sys driver and rename it to wacompen.BAD

Then reboot and see if it's removed.

Try that method, and return with results.

Best Regards,
Frederik.