BSOD randomly locale id 1033

[squat251]

Just recently (last couple days) been randomly BSODing on me while its idle and sometimes right after start up. its frustrating because I dual boot with linux and that auto loads on restart when it happens while I'm away. also stops downloads... the minidump is the attachment had to .rar it which seems silly, dunno why .dmp files arent allowed.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 000000000015ED06
BCP3: 0000000000000002
BCP4: 000000000015EC4E
OS Version: 6_1_7601
Service Pack: 1_0

 

[squat251]

thats the most recent dmp i could do the other 5 too if you need

 

[panais]

Hi.

In this order.

Update or uninstall this old (2006) software\driver.

ElbyCDIO Filter Driver


Cdrtools (Cdrecord) release information


Also update whatever is possible,software\drivers and of course windows using the windows update.


First read carefully this tutorial then run


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



Finish with the above steps and post back with any results.

 

[squat251]

isnt memtest86 for 32bit windows?

 

[panais]

isnt memtest86 for 32bit windows?

No.

Is for all.


First read carefully the tutorial then run


RAM - Test with Memtest86+

 

[squat251]

ran the test, passed 4 tests no errors. no log file since there was an option for memtest in grub loader.

 

[squat251]

new BSOD

just turned on my monitor to find another blue screen today. attaching dump. ive read it to see that ntsokrnl.exe is causing the problem, but since this is part of the OS that seems like an unlikely candidate. the memory is running clean btw. run memtest a couple of times.

 

[squat251]

um bump? do you want me to make a new thread?

 

[zigzag3143]

just turned on my monitor to find another blue screen today. attaching dump. ive read it to see that ntsokrnl.exe is causing the problem, but since this is part of the OS that seems like an unlikely candidate. the memory is running clean btw. run memtest a couple of times.

Memory corruption probably caused by a plugin. Your system uptime was 3 + days.
System Uptime: 3 days 15:58:22.721


I would run driver verifier to check which driver is at fault.

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).

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 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.