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 Crash on New Build

17 Jan 2011   #1
awinterton

Windows 7 Home Premium 64-bit
 
 
BSOD Crash on New Build

This was my first attempt at a new complete system build. I bought the computer off a friend in need of cash and had to replace a dead mobo and psu. Its been giving me a BSOD from the very beginning. No idea what's causing it except it seems to happen more frequently when watching a video clip or playing a game (maybe a problem with the graphics card?). All the drivers appear to be up to date.

Windows 7 64-bit 6.1.7600 Build 7600 Full retail version

Thanks so much for your help!!


My System SpecsSystem Spec
.
17 Jan 2011   #2
Tews

64-bit Windows 8.1 Pro
 
 

The dmp(s) point to ntkrnlmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable Driver Verifier to help pinpoint the faulting module...

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

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009a2180, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009a21b0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
17 Jan 2011   #3
awinterton

Windows 7 Home Premium 64-bit
 
 

wow. I did that and rebooted. Now it crashes just after I log into windows. Doesn't even finish pulling up the desktop or give me time to click on anything. This time the BSOD is pointing to clbudf.sys

What's next?
My System SpecsSystem Spec
.

17 Jan 2011   #4
Tews

64-bit Windows 8.1 Pro
 
 

That is the purpose of driver verifier ... upload the NEW .dmp files..
My System SpecsSystem Spec
17 Jan 2011   #5
Tews

64-bit Windows 8.1 Pro
 
 

clbudf.sys is your Cyberlink UDF Driver ... you can download the latest version from http://www.cyberlink.com/downloads/s...dex_en_US.html but we still need the new .dmp file..
My System SpecsSystem Spec
19 Jan 2011   #6
awinterton

Windows 7 Home Premium 64-bit
 
 

Ok. Sorry that took me so long. I had to restart in safe mode as it kept giving a BSOD as soon as I logged in. I've attached the latest dump files. Each time it would BSOD I removed the related program from the startup list in msconfig or uninstalled (some was bloatware). Then rebooted the computer, which would give me a new BSOD. Seems like this might be a never-ending trend. Insights please?

Adam
My System SpecsSystem Spec
19 Jan 2011   #7
awinterton

Windows 7 Home Premium 64-bit
 
 

I've been getting BSOD referencing my graphics card driver, a seagate driver, and the cyberlink driver. I think I've resolved those by either uninstalling the software and driver or updating to the most current driver. Now I'm getting these 2 dumps. Is this ever going to end? lol
My System SpecsSystem Spec
24 Jan 2011   #8
awinterton

Windows 7 Home Premium 64-bit
 
 

Anyone?
My System SpecsSystem Spec
25 Jan 2011   #9
Siddy1

Windows 7 Ultimate 32 bit
 
 

PLEASE HELPPPPPPP =(

==================================================
Dump File : 012411-17390-01.dmp
Crash Time : 1/24/2011 7:19:48 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xfdeddf40
Parameter 3 : 0xfdeddf80
Parameter 4 : 0x4a0800ab
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+ce508
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\012411-17390-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 139,440
==================================================



==================================================
Dump File : 012611-24421-01.dmp
Crash Time : 1/26/2011 5:45:23 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x9a9c0c00
Parameter 3 : 0x9a9c0c00
Parameter 4 : 0x0a000601
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+117c4e
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\012611-24421-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 139,440
==================================================
My System SpecsSystem Spec
25 Jan 2011   #10
fimble

windows 7 ultimate
 
 

Hi awinterton,

AVG is known to be a cause of BSOD's on some Win 7 systems so you need to uninstall it. Download the correct AVG Remover for your system. AVG Remover(64bit) or AVG Remover(32bit). If you have AVG ID protection installed, download the AVGID Protection Remover as well (it won't hurt to d'load and run it anyway). Download Microsoft Security Essentials as its replacement. Re-boot to Safe Mode. In Safe Mode run the AVG Removal tools. Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled!

PC Tools is known to be a cause of BSOD's on some Windows 7 systems. Uninstall PC Tools.
If you've already uninstalled PC Tools, go to C:\Windows\System32\Drivers and rename PCTCore64.sys to PCTCore64.old

More to follow.
My System SpecsSystem Spec
Reply

 BSOD Crash on New Build




Thread Tools




Similar help and support threads
Thread Forum
New build BSOD 0x0000124 Blue screen crash - DM log uploaded!
Hi guys - new to the forum and any help would be fantastic! Just installed Windows 7 on a 1gb Samsung spinpiont, keeping my old pc set up. All was good for the first day but now I'm getting regular blue screen crashes - increasing in regularity as the pc is on a while. I wonder if it's my psu as...
BSOD Help and Support
BSOD New Computer Build ntoskrnl.exe? Multiple crash dumps
Hey Everyone, This is a new system build and it was working fine, until a week after I had built it. The first blue screen I got was when I was uploading a video to youtube and now I seem to get them randomly fairly often (apart from when I’m playing games, which is odd), just browsing the...
BSOD Help and Support
Recent PC Build. CRASH...CRASH...CRASH
Okay guys, I'd love some help with some issues I am having. About two months ago I decided to start putting together parts to build my own rig(first time builder here) After scrounging around for a bit and getting the deals I liked I decided to put it all together and make my PC. Since then, Ive...
BSOD Help and Support
Home build crash
My son called last night to ask how to get his $3K build up and running again as after some Windows updates on the 16th it boots up to the post / the Windows "lights" then very briefly to a blue screen with white lettering - far too brief to read and back to the post then to start up repair. ...
BSOD Help and Support
System crash, BSOD's on new HTPC build
Hey there everyone, I've been a long time lurker on seven forums, and have used the info on your theads to get my google chrome working when win7 first came out. However, this time, I've decided to Move out of Tom's hardware threads and post here for a conclusive answer. I have put together a...
BSOD Help and Support
Another Crash Win 7 7100 RC 64 Build
Ok lets see: you can have the dmp report and the XML with all the system specs on it. Fast Reading Specs: Core i7 2.6 Asus P6T Deluxe Mobo 6GB of ram 1TB (2x 500GB Raid 0) ATi 4870 1GB Problem signature:
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 21:28.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App