BSOD shortly after start up, 0x0000001e

[ivNKj]

Title says it all, minidump file attached.

 

[writhziden]

It is difficult to find patterns with only one .dmp file. Yours indicates Catalyst Control Center/AMD Vision Engine Control Center as a possible culprit. You can install your drivers without Catalyst.

• You should already have the installer downloaded and installed the drivers/Catalyst software, so your drivers probably exist in C:\AMD\Support\xx-x_vista_win7_64_dd_ccc where the x's replace your version number of the driver software.
  
• Uninstall all AMD software related to your graphics card by uninstalling AMD Catalyst Install Manager in Start Menu -> Control Panel -> Uninstall a program
  
• Restart your computer.
  
• Re-install your drivers from the C:\AMD\Support\xx-x_vista_win7_64_dd_ccc folder using a similar method to that in OPTION TWO of http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html

If you continue to have problems after the above, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash reports and more information.

 

[ivNKj]

Ok I got a different BSOD now this time, "0x0000001a MEMORY_MANAGEMENT"

minidump attached

 

[writhziden]

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.


Crash indicates memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 214669
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Again: Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

 

[ivNKj]

I've uploaded the msinfo32.nfo file and also minidump of the BSOD I get when having Driver Verifier enabled (I tried 3 times and each time I got the exact same error). The BSOD happens just as the system enters the Windows 7 welcome screen.
I will leave Memtest86 running for the night once I go to sleep in a few hours.

 

[writhziden]

In case you had not determined the cause, it is the ESL Wire Anti-Cheat software you have installed. It is probably not the cause of your crashes, but it will hinder the Verifier investigation. You can either uninstall the software or see if disabling/unchecking it in Verifier allows the system to start normally.

You can also see if getting the latest ESL Wire Anti-Cheat software helps: ESL: ESL Wire - Main - ESL Wire - Europe - ESL - The eSports League

 

[ivNKj]

Ok so I left Memtest86 running for almost 12 hours and during that it made 20 passes. I took a pic of the final result. I guess this means my memory is damaged?

http://i50.tinypic.com/2gwcohz.jpg

The system booted without BSOD and seems to be working without problems with Driver Verifier enabled after I unticked ESLwire drivers from the list.

 

[writhziden]

Yes, it would indeed appear to be a memory problem. See if Verifier finds anything else conclusive by running for 24-36 hours. Otherwise, we will look closer at your RAM if you then get crashes with Verifier disabled.

To be clear: you want to keep Verifier enabled for 24-36 hours. At that time, you may disable it to see if your system is stable. If it crashes with Verifier disabled, then we will check the RAM more closely.

 

[ivNKj]

I've been using my PC for around 24 hours with Driver Verifier enabled and haven't had a single crash so far. I ran Memtest86 again last night and this time it found 2793 errors in 11 passes.

EDIT: Interesting, I just received one BSOD during the boot process after rebooting my pc to disable Driver Verifier. After that the PC booted normally. Minidump here:

 

[writhziden]

Crashes indicated a network related problem. I would recommend re-installing network related drivers, audio drivers, and your antivirus software. Uninstall ESET first, then download a fresh copy, and install it again with the fresh installer.

• How do I manually uninstall my Windows ESET security product? - ESET Knowledgebase
  
  
• Your drivers will appear under Network adapters and Sound, video and game controllers. To fully re-install a driver, use the following steps.
  1. First, download the latest driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the latest driver for the device.
  
  Alternatively:
  1. Login as an adminstrative user.
  2. First, download the latest driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Find the device you are trying to uninstall by expanding the appropriate set of devices
  8. Right click the device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the latest driver for the device.
  
  
• Please fill in your system specs in your profile and not in a post in this thread to get help finding drivers: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html.

Also, let's check your RAM settings.

• 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.
  
  Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)
  
  Thanks to Dave76 for help learning RAM Stability

 

[ivNKj]

I've uninstalled ESET and replaced it with MSE. I haven't reinstalled/upgraded any drivers yet. The system specs are filled in. Here are the CPU-Z tabs:

http://i46.tinypic.com/qpgv9h.jpg

BIOS settings:

CPU Vcore 1.26875V [Auto]
QPI/Vtt Voltage 1.100V [Auto]
PCH Core 1.050V [Auto]
CPU PLL 1.800V [Auto]
DRAM Voltage 1.500V [Auto]


I can see the actual used voltages for only DRAM and CPU Vcore from BIOS which are:
Vcore 1.232 V
DRAM Voltage 1.584V

Frequencies:
BLCK 133.28 Mhz
CPU Frequency 2.798.99 Mhz
Memory Frequency 1332.69 Mhz

Memory timings:
9-9-9-24

I've also lately noticed that it takes my PC around 10 seconds to establish the internet connection when I log in to the system instead of instantly. This weird delay doesn't really cause me much issues since its duration is so little but I wonder if it's related to this?

 

[writhziden]

Quite possibly related to your problem. May be that your network drivers are corrupted or need updating. Thank you for the memory information. We will look into that further if the driver updates do not resolve the crashes.

 

[ivNKj]

I have reinstalled all the drivers for the mentioned devices (I checked from the motherboard manufacturer's website that they're the latest version). I still have that ~10 sec delay in establising internet connection when logging into the system and most likely still get those errors in Memtest86 (haven't ran it yet after reinstalling the drivers).

Here is screenshot of what the internet connection error looks like to me when I open Chrome right after logging in and it tries to open the tabs of the previous session:

http://i47.tinypic.com/xq49x.png

Here is what it says if I try to refresh one of those pages when the connection is still off:

http://i50.tinypic.com/2yzaivl.png

 

[writhziden]

Strange. I am wondering if a http://www.sevenforums.com/tutorials/3413-repair-install.html is needed.

• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

 

[ivNKj]

I ran it once and it said:

Windows Resource Protection did not find any integrity violations.

I also noticed yet another small glitch. If I drag a window with a fullscreened window on the background, for example Google Chrome or Paint, the dragged window leaves a trail of its edges. Here is a screenshot:

http://i49.tinypic.com/2ebycjr.jpg

 

[Outlander]

I had odd things like this not long ago and it kind of looks like I was bitten by the Sandforce bug. Better check your SSD controller and if it is an early Sandforce start backing up NOW!

 

[ivNKj]

I had odd things like this not long ago and it kind of looks like I was bitten by the Sandforce bug. Better check your SSD controller and if it is an early Sandforce start backing up NOW!

Well I just found out that the windows leaving trails when dragged only happens with the classic Windows theme, with Aero enabled it doesn't happen so I'm not sure what is causing it. How do I check if my SSD uses an early SandForce?

 

[Outlander]

Google the Model of your SSD and see if you can find the spec's? Then check for controller #/type and Google that to see if it is one of the early model Sandforce units. Having gone through a similar experience your situation makes me feel uneasy. I would back up everything of value ASAP! Hopefully you do not have one of the problematic controllers.

 

[ivNKj]

Well after some googling I'm fairly sure my Intel X-25M is not a SandForce using SSD. Atleast most of the topics I found were along the lines of "Intel or SandForce?". Official specs in Intel's website say nothing about SandForce.

 

[writhziden]

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.