Solved Random BSOD (might be Caused from being Over loaded)

[Zeldafan1993]

Hello
I think this is my 3Rd time making a BSOD Post (the first 2 where solved I filed for a RMA for my RAM and CPU and Motherboard)

but any ways so i got about 2 BSOD's Yesterday and 1 Today and I dono why i got them i was installing a game left the room for a second came back and pc was restarting from a BSOD

Is Windows 7 . . .
- x64
- Full Retail
- RAM CPU and MOBO Are less then 3 months old just got them back from RMA


any Help would be greatly Appreciated.

Thanks
Matt (Zeldafan1993)

 

[writhziden]

Problematic Software:

Start Menu\Programs\SlimCleaner	Public:Start Menu\Programs\SlimCleaner	Public
Start Menu\Programs\SlimComputer	Public:Start Menu\Programs\SlimComputer	Public
Start Menu\Programs\SlimDrivers	Public:Start Menu\Programs\SlimDrivers	Public

How long have you been using the above software? If you have been using it since your previous blue screens, the software may be the root to all of your issues present and past...

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.
  
  
• We do not recommend automated driver update software. It often finds drivers for devices similar to but not exactly the same as the hardware actually on the system. This can lead to conflicts and blue screen crashes. If you need help finding driver updates for a certain device, please start a thread in Drivers - Windows 7 Forums instead of using software. Driver updates are not always necessary and some updates can actually decrease system stability rather than increase it, so it is usually better not to update unless a device or its driver is causing problems with the system. If it ain't broke, don't fix it.

 

[Zeldafan1993]

I was getting the Blue Screens before I installed those Programs i got the driver checking program to see if i had any driver problems that where causing the problem but it didn't solve anything

 

[writhziden]

Crashes are pointing to 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 213393
  • 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.

 

[Zeldafan1993]

I wonder if it is this 1 GB Ram stick my friend game me I have my 2x2GB sticks in there (like Usual) plus a 1GB stick he gave me do you think that could be the problem?

 

[writhziden]

Quite probable. Best way to find out would be to remove the 1 GB and see if the problems persist.

NOTE: It is not a good idea to mix and match RAM of different brands, sizes, timings, etc.

 

[writhziden]

How is the system responding with the 1 GB removed?

 

[Zeldafan1993]

ok well i just took the 1gb out this morning turned off the PC went to work came home and now i had it running for about 10-15 mins then got another BSOD (MEMORY_MANAGEMENT) im running my Vista dual boot from the same PC as i write this

dono what else to do to stop getting BSOD on WIN 7

cuz as of right now im running my Dual boot of Vista and its been going for 42 mins no problems

 

[writhziden]

Do the Verifier steps. It may just be a conflicting driver as was suspected initially.

 

[Zeldafan1993]

OK well i was just about to log on to my PC and do that (i had set it to run Memtest86+ it ran for 4hours and had 3 passes no errors). was logged int my windows 7 and then boom withing 5 mins i got a dif blue screen it was like IRL_LESS or somthing like that so i got nooo clue what to do now )

 

[Zeldafan1993]

OK so I think im in Driver Verify Mode, there was like no pop up or anything once i rebooted after enabling driver verify following the steps you posted before. as I write this im in "driver Verify Mode' and no crash or anything yet

 

[writhziden]

IRQL_NOT_LESS_OR_EQUAL: Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

You can make sure Verifier is enabled by opening a Command Prompt and typing

verifier /query​

Start Menu -> All Programs -> Accessories -> Command Prompt

 

[Zeldafan1993]

IRQL_NOT_LESS_OR_EQUAL: Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

yes that's the error so once again it comes back to driver, hmmm

IRQL_NOT_LESS_OR_EQUAL: Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

You can make sure Verifier is enabled by opening a Command Prompt and typing

verifier /query​

Start Menu -> All Programs -> Accessories -> Command Prompt

did this and it popped up another cmd window and stuff was scrolling by for 1 Min then closed

 

[writhziden]

Sounds correct. Your drivers should now be verifier enabled and we will await new crashes. Upload your latest crash reports in a minimum of 24 hours, preferably 36 hours.

 

[Zeldafan1993]

Sounds correct. Your drivers should now be verifier enabled and we will await new crashes. Upload your latest crash reports in a minimum of 24 hours, preferably 36 hours.

OK so do I just leave it running in this mode for a day or so and see if it crashes?

 

[writhziden]

Do your normal routine for 24-36 hours. Try to do the things you normally do that cause crashes; if crashes are random, just don your normal routine and accumulate the crashes over that time period. We will analyze the new crash reports at that time to see if we can pinpoint the cause(s).

 

[Zeldafan1993]

ok cuz i find in driver verify mode its kinda "laggy" even on the desktop and things took longer to start up etc

 

[writhziden]

That is common, and it is something you will have to be patient with for a day or so. Sorry for the inconvenience, but it is necessary to narrow down the problem.

 

[Zeldafan1993]

ok well I had 1 crash already , and when it crashes I don't have to "re-enable" driver verify mode right? and after 1 of my blue screens I noticed some of my programs (some that start with windows) and stuff like JRE are not functioning

 

[writhziden]

You do not have to re-enable Verifier after a crash. it will stay enabled until you disable it or use system restore to a date/time prior to when you enabled it.