Solved BSOD at random times BCCode: 1000007e

[Awesomemaxx]

A few months ago my brother started using my laptop (bad idea i know) and ever since I have been getting a blue screen message whenever i boot up safely i get the following message:

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: 1000007e
BCP1: FFFFFFFFC0000094
BCP2: FFFFF880042BEE26
BCP3: FFFFF88003196858
BCP4: FFFFF880031960B0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem are included in my attachments:
C:\Windows\Minidump\033012-66004-01.dmp
C:\Users\...\AppData\Local\Temp\WER-101260-0.sysdata.xml

About my computer:
HP G72 Notebook PC
Pentium(R) Dual-Core T4500 @ 2.30 Ghz
3 GB of RAM
Windows 7 Home Premium x64

 

[zigzag3143]

Related to RTL81892SE NDIS Driver from Realtek Semiconductor Corporation. I would re-install the newest version available.

 

[Awesomemaxx]

Re:RTL81892SE NDIS Driver

Now that i have the sys file how do I install it

 

[kegobeer]

Download the entire driver and install it - don't just try to copy a system/dll file.

 

[zigzag3143]

Now that i have the sys file how do I install it

You need to go to the mfr and get the installer. The sys file wont do you any good. It may be an old file, the wrong bit, etv.

 

[Awesomemaxx]

New Problem BSOD Strikes back

I went to realteck and downloaded their version of the driver that had the install with it. after getting the same blue screen twice while installing it. It finally said i had a successful install. My brother goes on Skype and I wake up to find this message on my laptop:


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: 1000009f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: FFFFFA800241B040
BCP4: FFFFF800046004D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\040212-21028-01.dmp
C:\Users\...\AppData\Local\Temp\WER-108467-0.sysdata.xml

The instaler for the driver from realtech:
Realtek

 

[Awesomemaxx]

New Problem BSOD Strikes back (cont.)

these are the files

 

[zigzag3143]

these are the files

Unfortunately still Related to rtl8192se.sys RTL81892SE NDIS Driverr from Realtek Semiconductor Corporation.

Has anything been changed on PCI?

One other possibility is your Avast but lets hold off on changing that till later.

 

[pwood]

I too have been having this BSOD randomly coming up, driving me nuts!! I have included the dump file, I hope someone can help because soon I am going to say heck with it and just reload my computer, which will suck considering I love how it is setup right now and would take a long time to get it back to anywhere near what I have now.

 

[JMH]

These crashes were caused by memory corruption/exception (`c0000005) (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[pwood]

Well being that I have a 6core, and running 16 Gigs of Sniper RAM, all that are not that old I am pretty sure that it is NOT the memory, I did what you said though and turned on the driver verifier, well my computer slowed to a very bad crawl, took my computer about 5 minutes to even load, and considering I have a SSD it usually only takes about 5 seconds. Then with that verifier going my computer blue screened a number more times, much more than usual, I was only able to catch one thing after I think the second BSOD, atcdm64a.sys SOOO loaded up a program that I know works really well when it comes to drivers and it found a bunch that said they were out of date even though the manufactor website didn't have any showing, but it BSOD again while trying to get the updated drivers. I shut my computer down completely since I had to go to work and was NOT trying to mess with it right then, I got home and turned my computer back on since I had also turned the verifier off before I left, and went straight to loading the drivers program. I was able to dl all of them and install, so far so good.... but will only truly be satisfied and happy after I know it doesn't do it anymore.

Thanks for you help!

 

[zigzag3143]

pwood

There are several other obvious problems we would be happy to address if you start your own thread.

You can post a link to it here and if you have any more DMPS please upload them there.

 

[Awesomemaxx]

I have too use a different method because the person who owns the laptop is too cheap too have any back up for it

 

[Awesomemaxx]

BSOD and Blackouts from idleness

The person who owns the computer im working with is too cheap to get any back up for the computer in addition to the previous problem now when ever the computer goes idle it freezes. i would give you the message i received after i restarted the computer from the idle mishap but the message i was going to post was interrupted by yet another a blue screen. so in the first zip file is the idel data the second is the blue screen data.

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: 50
BCP1: FFFFFA809DA40609
BCP2: 0000000000000001
BCP3: FFFFF880044F9CC8
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\051112-21574-01.dmp
C:\Users\...\AppData\Local\Temp\WER-69654-0.sysdata.xml

 

[writhziden]

Is the system still under warranty? Has the owner run Memtest86+ yet as described in post #10 by JMH?

 

[Awesomemaxx]

No it is no longer under warranty and i cant run the mem test because if it crashes the system and i cannot fix it then all the data is lost because the owner is to cheap to get back up.

 

[writhziden]

There is very little danger in Memtest86+ crashing the system. Verifier is more dangerous and should be avoided if you are concerned about that, but Memtest86+ is 99.99% safe. To be honest, the 0.01% chance of it causing a system failure is due to a hardware failure that will occur on the system anyway if it is on the verge of doing so. So there is no risk unless the system is already going to fail whether the user runs Memtest86+ or not.

I highly doubt a system failure is imminent, so Memtest86+ is safe.

 

[Awesomemaxx]

conducted a memtest hp already provided in the bios mo errors detected

 

[Awesomemaxx]

is Gold Memory or Prime95 better tests or is memtest the only way

 

[writhziden]

Prime95 is a better test than Gold Memory: . Memtest86+ is also a really good test, and I highly recommend doing 7-10 passes.

Further reading: Finicky RAM.


Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• 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.