Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Using Google Chrome, error 0x0000001E


30 Nov 2012   #1

Windows 7 Home Premium 64bit
 
 
BSOD Using Google Chrome, error 0x0000001E

I've been working on this one all day, as it only just started occuring, but it is to the point that it is random. Sometimes the website will open, and sometimes it will flash to the blue screen and restart. It was doing this every time I tried to shutdown, but a rollback of the display drivers out of the BETA version fixed that.

It seems to be most occuring when I multitask but the memory scanner came up with nothing, any help would be most wonderful, as I need this computer and its files for college, and reinstalling Windows 7 is a deadly option due to the lack of install disk that came with the computer.

(The occurrence detailed in the minidump was from me clicking on a link from a Skype window, and the computer crashing as Chrome attempted to load the page.)

EDIT: Ran CCleaner, didn't help.

My System SpecsSystem Spec
.

30 Nov 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

Code:
Start Menu\Programs\Alcohol 120%	Public:Start Menu\Programs\Alcohol 120%	Public
Please uninstall Alchohol %. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Perform a clean boot:
Your crash dump does not give a probable cause. So we'll enable Driver verifier.

Driver Verifier

Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier
I'd suggest that you first backup your data 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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 [/B][B]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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
30 Nov 2012   #3

Windows 7 Home Premium 64bit
 
 

Alright, I'll do the SPTD fix first, and see how that goes, as the roommate's computer has been doing a similar thing, and he also uses Alcohol.

If that doesn't work I will use the Driver Verify and get back to you on that starting tomorrow after work, so I'll have more time to nuance it. Thank you for your help in the mean-time!
My System SpecsSystem Spec
.


01 Dec 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Take your time, good luck
My System SpecsSystem Spec
01 Dec 2012   #5

Windows 7 Home Premium 64bit
 
 

I tried it, then got another BSOD error, reading 0a as the BC this time.

However, I found remnants of the driver you named afterwards, and once I removed that, opening up a link through skype came without a hassle, this time. I'll do more extensive testing on it tomorrow but it may be solved
My System SpecsSystem Spec
01 Dec 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Take some time before marking as solved, there are a few more test we should do.

See you soon
My System SpecsSystem Spec
01 Dec 2012   #7

Windows 7 Home Premium 64bit
 
 

Ran Driver Verifier, blue screened before logging in, the screen citing "stdriver.sys". Safe mode just freezes up while loading the drivers. Doing a startup repair with System Restore, and if that works I will try to get the file uploaded in an edit to this post.

EDIT: Question though, how do I tell if it is actually working or just stuck "attempting repairs" and wont do anything further? Is it surefire there will be a failure message or should I give it a certain amount of time (Hour or so?) And wouldn't the restore itself negate the creation of the memory dump from the previous crash?

Double EDIT: The restore worked, but like I suggested, there are no minidump files to be had from that crash. However I will send what the Diagnostic tool can grab for now.

Look ma, more edits!: After some research I discovered STdriver is Sound Tap, used by NCH Software (Of which I was using their Debut software). I've now removed that and its driver, going to try another driver verifier, and if that works I will repost with the working log-file.
My System SpecsSystem Spec
01 Dec 2012   #8

Windows 7 Home Premium 64bit
 
 

Bump:

So I made the restore point, about to run the driver verify, and upon restarting to make sure it stayed, windows wouldn't boot. I've run Startup repair once now using that restore point (since all the others have wondrously disappeared for whatever reason) and it still refuses to boot. Not particularly sure what to do, it wont give me the option to run in safe mode.
My System SpecsSystem Spec
01 Dec 2012   #9

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Do you mean you are unable to disable verifier?
You can go to safe mode from Advanced Boot Options and disable it.

PS: No bumping please.
My System SpecsSystem Spec
01 Dec 2012   #10

Windows 7 Home Premium 64bit
 
 

Sorry about that. I even winced when I did it, not sure what I was thinking.

And no. Verifier was disabled, and I was running the computer normally after that meltdown. After uninstalling the program that made verifier quit out on start-up, I restarted. All good, so I made a restore point, seeing as there were no other restore points and restarted. If it had started up I would have continued to start a clean boot and then Verifier. Instead, it did not fully start, and no matter how many times I try to repair it, go into safe mode, or anything else, in no way shape or form will my computer load. I've moved RAM around, I've gone through every motion to try and fix it that I know of short of reinstalling the OS.

I have Windows 7 saving to my USB drive just in case.
My System SpecsSystem Spec
Reply

 BSOD Using Google Chrome, error 0x0000001E




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:23 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33