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: Random BSOD New build 0x800... event id 1001

24 Apr 2013   #1

Windows 7 64-bit OEM
 
 
Random BSOD New build 0x800... event id 1001

I recently built a new pc, installed windows 7 64bit, installed mobo drivers, installed video card drivers, then got all of windows updates. I got a BSOD randomly and it rebooted to windows fine. The next day it happened again about 2 hours after boot. The second time I saw it said: Page fault in nonpaged area, but then it flashed away and rebooted before I could read more. Then last night I fell asleep downloading something and woke up to it saying it recovered from an unexpected shutdown.

Not sure if this is related but Applications are crashing as well. I get error messages such as:
Catalyst Control Center: Host application has stopped working.
McAfee service host crash
Windows Explorer has stopped working
Also Chrome crashed very frequently when I tried to upload multiple photos.

Specs:
Cpu: AMD FX6300 6core
Motherboard: Gigabyte 990fxa-ud3 revision 3.0
Ram: Patriot Viper 2x4gb 1866mhz
Gpu: Sapphire 7870xt

Sorry for the long post, just trying to get as much info that is needed.

I have attached the .zip file from the Sf diagnostic tool, hope I did it right...
Thank you in advance for any help, it is MUCH appreciated!

My System SpecsSystem Spec
24 Apr 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck 109, {a3a039d89ac8d7b2, b3b7465eed45a718, fffff800037567c1, 1}

Probably caused by : ntkrnlmp.exe ( nt!CmpParseKey+721 )
Code:
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
The bugcheck indicates that the Windows kernel has detected that some form of critical data corruption has occurred, this could be due to failing RAM whereby the kernel objects are being held, causing the held data to become corrupted. Poorly written drivers can cause this problems by directly modifying kernel code.

Remove:

Code:
Start Menu\Programs\McAfee
Start Menu\Programs\McAfee Online Backup
McAfee is known to cause BSODs with Windows 7, and uses many poorly written drivers which tend to cause memory access violations, the best method is remove all McAfee products completely using the McAfee Removal Tool, and then install these free and proven alternatives which work best with Windows 7.

Install and perform full scans with:
information   Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:The bugcheck also indicates memory corruption, and illegal modification of code.

Code:
1: kd> !error ffffffffc000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
My System SpecsSystem Spec
24 Apr 2013   #3

Windows 7 64-bit OEM
 
 

Quote   Quote: Originally Posted by x BlueRobot View Post
Code:
BugCheck 109, {a3a039d89ac8d7b2, b3b7465eed45a718, fffff800037567c1, 1}

Probably caused by : ntkrnlmp.exe ( nt!CmpParseKey+721 )
Code:
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
The bugcheck indicates that the Windows kernel has detected that some form of critical data corruption has occurred, this could be due to failing RAM whereby the kernel objects are being held, causing the held data to become corrupted. Poorly written drivers can cause this problems by directly modifying kernel code.

Remove:

Code:
Start Menu\Programs\McAfee
Start Menu\Programs\McAfee Online Backup
McAfee is known to cause BSODs with Windows 7, and uses many poorly written drivers which tend to cause memory access violations, the best method is remove all McAfee products completely using the McAfee Removal Tool, and then install these free and proven alternatives which work best with Windows 7.

Install and perform full scans with:
information   Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:The bugcheck also indicates memory corruption, and illegal modification of code.

Code:
1: kd> !error ffffffffc000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
Thank you for the quick reply. I will remove Mcafee and install MSE and MalwareBytes and get back to you. It is worth noting that I got the first and possibly second crash before I installed Mcafee. I had MSE and only installed Mcafee because I had a license on my Windows 7 laptop. As for the illegal modification of code... I don't know what happened there as I am no programmer and I would not do anything illegal on purpose...
My System SpecsSystem Spec
.


24 Apr 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Don't worry, you didn't do anything illegal, it means a driver did something which it didn't have permission to do so, and will look forward for the update.
My System SpecsSystem Spec
24 Apr 2013   #5

Windows 7 64-bit OEM
 
 

Okay literally 20 seconds after my last post my computer restarted, no blue screen, but it was strange... anyway I unistalled Mcafee in add/remove programs, downloaded MSE and malwarebytes, updated everything (including one windows update), then rebooted and ran full scans in MSE and Malwarebytes which came up with nothing. What should I do now? Wait and see if I get anymore Issues or...?

Edit: Well that didn't take long. Just now my screen completely froze up and waiting didn't do anything. I had to press the reset button. Then I got a message that said Your computer was unable to start. Then startup repair checked my system and it prompted me to do system restore. This issue is different and it seems to be evolving... I was reading files in event viewer and it said it could have been caused by sudden power loss...maybe one of my connections are loose? Also my 8 pin cpu power I routed behind the mobo, but I had to push down slightly to tighten the mobo... would this cause issues? Ugh I am no good at this and its really worrying me.
My System SpecsSystem Spec
25 Apr 2013   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Check that all the slots on the motherboard are clear of dust, and then check all the cards (e.g. RAM) are properly connected, make sure your power cables are also connected properly.

What is the brand of your PSU? Do you know the specifications page for it?
My System SpecsSystem Spec
25 Apr 2013   #7

Windows 7 64-bit OEM
 
 

Okay so my PC was pretty clean as I have just built it a few days ago, but I went ahead and blew out any dust and checked all my connections again(RAM, Gpu, 24pin,8pin, etc) As far as the model of PSU it is a Cooler Master Silent Pro M700 RS-700-AMBA-D3 700W ATX12V V2.3 80 plus bronze certified:
Silent Pro M 700W - Cooler Master

There's the specs on the manufacturers website.

Edit: Also I was just thinking that it indicated RAM corruption. Now I ran the Windows memory diagnostic 3 times and it checked out ok. Maybe its just not catching it, should I try something like Memtest to make sure?
My System SpecsSystem Spec
26 Apr 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Testing the RAM wouldn't be a bad idea, here's the usual troubleshooting method we use:Run Memtest86+ for least 7-9 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Quote   Quote: Originally Posted by Arc View Post
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
It is a motherboard issue. The particular slot is bad.
My System SpecsSystem Spec
26 Apr 2013   #9

Windows 7 64-bit OEM
 
 

Quote   Quote: Originally Posted by x BlueRobot View Post
Testing the RAM wouldn't be a bad idea, here's the usual troubleshooting method we use:Run Memtest86+ for least 7-9 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Quote   Quote: Originally Posted by Arc View Post
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
It is a motherboard issue. The particular slot is bad.
Okay Ill give it a shot. But it will have to wait until tomorrow because I work graveyards and it sounds like the test takes some input and isn't automatic. Ill let you know when its done.
My System SpecsSystem Spec
27 Apr 2013   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Okay, and the test will run itself, it's just when you get errors you will need to start doing some more through testing and swapping around etc.
My System SpecsSystem Spec
Reply

 Random BSOD New build 0x800... event id 1001





Thread Tools



Similar help and support threads for2: Random BSOD New build 0x800... event id 1001
Thread Forum
Solved BSOD 0x000000c5 (Event ID-1001) Windows 7 BSOD Help and Support
Event 1001 BugCheck Event 41 Kernel-Power Event 4 k57nd60a BSOD Help and Support
Random Event 1001 Bugcheck 0x00000116 reboots, did not see bluescreen BSOD Help and Support
BSOD Event 1001 Source Bug Check BSOD Help and Support
Recent random BSOD event ID 1001 BSOD Help and Support
BSOD Event ID 1001 BSOD Help and Support
BSOD then restart Event ID: 1001 BSOD Help and Support

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 09:04 AM.
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