Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue Screen (BSOD)


  • Please log in to reply

#76
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You would have to get into the bios to find the USB and see if you can disable on boot.
  • 0

Advertisements


#77
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

You would have to get into the bios to find the USB and see if you can disable on boot.

What is STOP: 0X7E? (STOP: 0X0000007E) No error name or anything...
  • 0

#78
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.




Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

#79
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.




Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

Restarted, then it was 0xB8, restarted again now its 0x8E. Can't access desktop so I can't download software. I was trying to access my system recovery partition by alt + f10, and that is what I get. Is it common to change like that on each restart?
  • 0

#80
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

Can't access desktop so I can't download software.


Got your OS installation disk?
  • 0

#81
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

Can't access desktop so I can't download software.


Got youfr OS installation disk?

The computer I am on right now did the same thing before my other laptop started continuing blue screen. This computer I'm on right now did a blue screen similar to the one that first started the other blue screens on my other laptop, luckily it didn't continue on this one. But, is there a way I can post the minidump log from this computer, that could maybe give me an answer to what caused it on the other one? The blue screen that just happened on this one was like some dump, and it had a counter on the bottom going up from 0-100. I tried taking a picture but i was too slow. I will try and attach the dump log.
  • 0

#82
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#83
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

==================================================
Dump File : Mini082412-01.dmp
Crash Time : 8/24/2012 8:25:24 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : 0xe5e17000
Parameter 2 : 0x3816e121
Parameter 3 : 0x8d16fb60
Parameter 4 : 0x0000000b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+98339
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18607 (vistasp2_gdr.120402-0336)
Processor : 32-bit
Crash Address : ntoskrnl.exe+98339
Stack Address 1 : ntoskrnl.exe+4dd94
Stack Address 2 : ntoskrnl.exe+a8f93
Stack Address 3 : ntoskrnl.exe+1d5eb4
Computer Name :
Full Path : C:\Windows\Minidump\Mini082412-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 170,416
==================================================
  • 0

#84
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.




What OS is on this system?
  • 0

#85
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.




What OS is on this system?

Windows Vista Home. My other one is Windows 7 Home.
  • 0

Advertisements


#86
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK did you recently update a driver?
The issue is located in the OS itself either with a driver or a service so that is where I want to start.
  • 0

#87
jay012992

jay012992

    Member

  • Topic Starter
  • Member
  • PipPip
  • 73 posts

OK did you recently update a driver?
The issue is located in the OS itself either with a driver or a service so that is where I want to start.

On this computer no I didn't recently update a driver, on the other one, the main one I'm having problems with, I believe there was some sort of update before it happened but it started out rarely then just finally quit.
  • 0

#88
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK just to keep everything easy to follow lets not worry about the other system right now and concentrate on this one. Let check to see if a service if causing this.




Lets see what you have in your startup services area

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP