BSOD Internet Explorer,MSE, uTorrent, etc. BCCode: be

[goldenz]

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: be
BCP1: AE83128A
BCP2: B34AA121
BCP3: 8E3BB6FC
BCP4: 0000000B
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

My Windows 7
====================
Windows 7 Ultimate 32x
Service Pack 1
Hardware age ( Brand new mother board/VGA/Proccessor) 1 week ago.
Installed a new Windows recently.

Kindly Advice,
Thanks.

 

[zigzag3143]

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: be
BCP1: AE83128A
BCP2: B34AA121
BCP3: 8E3BB6FC
BCP4: 0000000B
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

My Windows 7
====================
Windows 7 Ultimate 32x
Service Pack 1
Hardware age ( Brand new mother board/VGA/Proccessor) 1 week ago.
Installed a new Windows recently.

Kindly Advice,
Thanks.

uTorrent attempted to write to rom.

These crashes were caused by memory corruption (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!!!


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



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

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[goldenz]

zigzag3143,

Thanks for caring to help me fix this out. I did memory scan and all is clean. And i did the verifier setting and will restart in a while.

However I read that Dmp file is for detecting which driver causing the problem, thats why i attached as instruction. Also the Computer is crashing randomly everyday,even in idle status So i will not know what cause the problem, but anyway i will get it a try.

Can you just know what causes this from the dmp file?

Note: I tried WinDbg but i didn't success to understand how the whole thing work.

Kindly Advise,
Thanks!

 

[zigzag3143]

zigzag3143,

Thanks for caring to help me fix this out. I did memory scan and all is clean. And i did the verifier setting and will restart in a while.

However I read that Dmp file is for detecting which driver causing the problem, thats why i attached as instruction. Also the Computer is crashing randomly everyday,even in idle status So i will not know what cause the problem, but anyway i will get it a try.

Can you just know what causes this from the dmp file?

Note: I tried WinDbg but i didn't success to understand how the whole thing work.

Kindly Advise,
Thanks!

Windbg isnt rocket science but there is a steep learning curve and you need to download the symbols (abt 4 gigs).

 

[goldenz]

Well, I had some problems with Silverlight Updates its installed but cannot update with windows update And cannot be Uninstalled from the Add/Remove. So I have downloaded the fix from Microsoft "MicrosoftFixit.ProgramInstallUninstall.Run.exe" Fully Uninstalled it. Also I have a problem with the "MSE" And Re-installed it, And Run A Registry cleaner with CCleaner. No Crash So far, System is stable ( 3 hours running no crash). I Removed the setting from Verifier.exe back to the old state. Verifier.exe has detected one crash before i did the Microsoft fix and the Registry Cleaner. So I Just Guess till now the Winning fix goes to Microsoft tool and the Registry Cleaner ( Hopefully so ).

I will Leave the machine working all night long and test it for couple of days till i'm sure that everything works as it should.

 

[goldenz]

My Computer crash today when i tried to move some file from a path to another
0x0000001A ( 0x00041790, 0xC0802F6, 0X0000FFFF, 0X00000000

I believe i'm still stuck with the crash thing

 

[zigzag3143]

My Computer crash today when i tried to move some file from a path to another
0x0000001A ( 0x00041790, 0xC0802F6, 0X0000FFFF, 0X00000000

I believe i'm still stuck with the crash thing

Driver verifier DMP file? upload it please.

 

[goldenz]

Well if you mean the Minidump then i have attached 2 recently DMP files responsible for The "0x0000001A" , Other than that let me know if you need other files.

Note: those dmp's are created while the Verifer.exe is disabled.

Regards

My Computer crash today when i tried to move some file from a path to another
0x0000001A ( 0x00041790, 0xC0802F6, 0X0000FFFF, 0X00000000

I believe i'm still stuck with the crash thing

Driver verifier DMP file? upload it please.

 

[zigzag3143]

Well if you mean the Minidump then i have attached 2 recently DMP files responsible for The "0x0000001A" , Other than that let me know if you need other files.

Note: those dmp's are created while the Verifer.exe is disabled.

Regards

My Computer crash today when i tried to move some file from a path to another
0x0000001A ( 0x00041790, 0xC0802F6, 0X0000FFFF, 0X00000000

I believe i'm still stuck with the crash thing

Driver verifier DMP file? upload it please.

Neither was driver verified but caused by memory management.

These crashes were caused by memory corruption (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!!!


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



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

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[goldenz]

Is it a "MUST" to provide you these dmp file while the verifier.exe is Running? Because the files i attached it created while the verifier.exe was not running.

Kindly Advise.

 

[goldenz]

So Basically you wanted me to Run the verifier.exe and wait till a crash happen (BSOD) and then attach my dmp files located under c:/windows/Minidump

Is that all what needed in this process?

Note: I Already Ran the "RAM - Test with Memtest86+" and all are ok

 

[zigzag3143]

So Basically you wanted me to Run the verifier.exe and wait till a crash happen (BSOD) and then attach my dmp files located under c:/windows/Minidump

Is that all what needed in this process?

Note: I Already Ran the "RAM - Test with Memtest86+" and all are ok

Yes re: verifier. It will usually find the driver causing the problem.

 

[goldenz]

Fixed the problem by Installing A Fresh New windows (As i always do), I always believe that BSOD is non Fixable maybe it is fixable. Anyway Thanks for the Great Support and help in here
//close

Regards

 

[goldenz]

Hello,

After I thought Installing an 64x bit of Windows Proffessional Will fix the prob, another BSOD appear 0x000000c1 and When Verifier.exe is enable, the Blue Screen popup After the login to the windows at once.

Attached is the Windows_NT6_BSOD_jcgriff2 Folder With Verified.exe enabled.

Kindly Advice,
Thanks in Advance

 

[zigzag3143]

Hello,

After I thought Installing an 64x bit of Windows Proffessional Will fix the prob, another BSOD appear 0x000000c1 and When Verifier.exe is enable, the Blue Screen popup After the login to the windows at once.

Attached is the Windows_NT6_BSOD_jcgriff2 Folder With Verified.exe enabled.

Kindly Advice,
Thanks in Advance

This crash was verified and Related to gdrv.sys Microsoft Register Server. Usually a result of modifcation of the OS.

May be fixed if you update to SP-1, but if there is any modification of the system files by you it may not.

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[goldenz]

After I Installed the New System I Ran full Update and I Installed Sp1 And the BSOD Appear. The system is Retail Un-modified Windows With Valid Serial from Microsoft. I Made a Restore from Earlier point to see if the Updates + Sp1 caused the Crash. But nothing Still the same before and after Update.

I did not Install Any Antivirus nor firewall 3rd party application, Although I'm Using Microsoft Security Esstential

 

[zigzag3143]

After I Installed the New System I Ran full Update and I Installed Sp1 And the BSOD Appear. The system is Retail Un-modified Windows With Valid Serial from Microsoft. I Made a Restore from Earlier point to see if the Updates + Sp1 caused the Crash. But nothing Still the same before and after Update.

I did not Install Any Antivirus nor firewall 3rd party application, Although I'm Using Microsoft Security Esstential

On the only dmp file I have you do not have sp-1 installed.

 

[goldenz]

Yes Sir, Because I Already Restored to an earlier point to Undo anything I made to see if the Crash gone, So Basically The crash was exist on SP1, The I restored to old Point that has no Sp1 There. And still the BSOD Appear Immediallty when I enable Verifier.exe

Do you want me to Install SP1 Again and Run Verifier.exe? will that help?

 

[zigzag3143]

Yes Sir, Because I Already Restored to an earlier point to Undo anything I made to see if the Crash gone, So Basically The crash was exist on SP1, The I restored to old Point that has no Sp1 There. And still the BSOD Appear Immediallty when I enable Verifier.exe

Do you want me to Install SP1 Again and Run Verifier.exe? will that help?

Since the faulting file is an OS file you need to repair it. If not the update to sp-1 you can do a repair install if you have the win 7 dvd.

 

[goldenz]

Okay, I will Do That.
Thanks.