BSoD sad face

[Toxi]

- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
yes?
- an OEM or full retail version? OEM - What is the age of system (hardware)?
about 2 years
- What is the age of OS installation (have you re-installed the OS?)
yes about 4 times total but recently 3 days ago


Issues
i just got my computer back from a repair shop as the outlet for the charger was lose and it would not charge.
after getting the computer back the batter is completely dead and laptop must be plugged in at all times.
And now i've received a few BSoD problems. They happen while playing very simple games

Driver mistakenly marked part of it's imaging pagable instead of non pagable

also:
Bccode 1E

Any other information needed?

 

[americancritic]

Hello and welcome to the forum.

I will look at your minidumps in just a little bit.

 

[americancritic]

Hello the stopcode errors are as follows.

1. 0x3B - ntkrnlmp.exe
2. 0x119 - igdkmd64.sys
3. 0xlE - volsnap.sys
4. 0x3B - win32k.sys
5. 0x1E - ntkrnlmp.exe
6. 0x1E - ecache.sys

Please follow the memtest instructions and then post the results with your next post...

Note: If you are OverClocking or use any automatic overclocking BIOS features, Turbo Mode (Disable it), then drop back to the stock speed as a starting point.
Disconnect any other internal hard drives and external USB devices.
Check for any loose hard drive power or SATA cables, Graphics card or other power cables.
First try running Memtest86+: RAM - Test with Memtest86+ - Windows 7 Forums
This runs from a boot disk or CD and should eliminate or confirm if your one or more of your memory sticks are bad or the SPD values in the BIOS are correct. Let it run for as long as you can: 2,4,6,8 or more hours (at least 3 full passes), if no errors by then your ram is OK.

 

[Toxi]

okay will do thanks

 

[americancritic]

Please take your time no rush and while your running the test I will be taking a closer look into your minidump files, and will keep you informed as we go.

 

[Toxi]

kay ran the memtest for 9 hours 50 minutes got 8 passes and 0 errors

i don't think i am overclocking
and don't have anything else plugged into the computer

 

[americancritic]

Hello now we know it is not a bad stick.

Please follow the instructions here and this should give us the bad driver or drivers.

Using Driver Verifier to identify issues with Drivers - Windows 7 Forums

 

[Toxi]

Alright did driver verifier now waiting for it to BSoD on me

 

[americancritic]

Ok as soon as it BSOD's on you it should give us the driver that is causing the problems...

 

[Toxi]

Kay BSOD on me
gave me the system_service_Exception
Stop 0x3B

 

[americancritic]

What else it sould give you more info, the name of the driver etc, don't turn it off leave it on and continue doing what ever you do on your computer, we want it to verifiy all the drivers that are behaving badly...

I would like for it to BSOD say 3 times or more while the driver verifier is on then we can norrow it down to what we must do to repair it...

Your doing a great job, it's nice to know that you care about your system and when theres a problem you get help right away. Very nice

 

[Toxi]

=]
would you like me to redo the system health check afterwards?

 

[americancritic]

Ok you can stop all tests right now except the driver verifier lets keep it going at least until tomorrow, you can just leave it running tonight and make sure no one uses the computer, by then it should give us what we need.

Any more reports that come up please post them to us and word for word, as other codes in the mix can be very important for us to properly diagnose your system.

Very important if your system blue screens then follow the posting instructions and upload all of them. Thank you and you are doing great.

 

[Toxi]

Okay i got it to BSOD a few times and this is what i got

I uploaded the pictures of the BSOD

and after rebotting the comp i got the send crash report to microsoft and the detils were as followed:
[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\MEMORY.DMP[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Read our privacy statement:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409[/FONT]

was that enough or do you want a few more BSOD?

 

[americancritic]

If it BSOD's with a different number then the ones you sent to me then yes if the same I won't need those. I am now looking up your codes and will be back with you in a little bit.

 

[Toxi]

I think i got a new one

 

[Toxi]

Could some of the problem be caused by the computer requiring to much power? as i basically have no battery =/ I have the computer running on balanced power

 

[americancritic]

Hello I am sorry I have just now logged on as I have some some children issues to deal with today.

I am now looking at all the things you have sent.

Please turn off the driver verifier, let your computer BSOD and upload me the file.

Thank you

 

[americancritic]

Hello Toxi

Please go to this link and test you hard drive and then let me know the results with your next post. Thank you

HD Diagnostic

 

[americancritic]

Hello yes I am afraid you need to the the ram test in the tutorial that I posted for the memtest.

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.