• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD after OS installed

Goldorak

Junior Member
Hi!

I have a brand new system:
DFI Lan Party nForce 4 Ultra-D
Athlon 64 X2 3800+
OCZ EB DDR PC-4000 2x1024MB Platinum Edition Dual Channel Kit
XFX nVidia 7800GT
2 x Hitachi Deskstar T7K250 160 GB (configured as RAID 0 and bootable)
BenQ 1640 DVD writer

So just after installing Windows XP Pro SP2 on my RAID and the nVidia drivers I get this BSOD

BSOD capture

I do not overclock the system, everything is stock and brand new! I logon and after a few minutes, Windows goes nuts... Anybody have an idea about what can be causing this BSOD? Nothing is installed except the nVidia drivers (latest release) on top of Windows XP SP 2.

Thanks a bunch.

 
I'm curious about the bottom part of the message where it says "http.sys" Would dthat mean that the problem is actually related to that file?
I was wondering about that and searched for that file name, didn't get too many hits.
I didn't see anything that "shouted" at me about it.

Bump😕
 
do you have norton installed?

Does the computer boot OK in safe mode....does your BSOD still appear in safe mode...

go into safe mode and use msconfig to remove everything that starts at start-up and try again.. If it works fine then enable the programs again 1 by 1 until it dies again then you know your problem!
 
go to the repair console and run chkdsk on your drives. also try system file checker on the drive with the OS - the command is "sfc /scannow" i believe.

i've had this BSOD before... for some reason i seem to remember it being related to the hard drives. best of luck
 
Searched the internal MS KB for ya.

Only one case on record of a Stop D1 in http.sys and the dump revealed a bitflip in a bad CPU.




Fuzzynavel's initial troubleshooting steps sound good.
 
Originally posted by: Smilin
Searched the internal MS KB for ya.

Only one case on record of a Stop D1 in http.sys and the dump revealed a bitflip in a bad CPU.




Fuzzynavel's initial troubleshooting steps sound good.

Well if it's the CPU that's really bad news... If I need to return the CPU, it's going to be hard as hell to prove that the CPU is the cause of the problem:disgust:

I'll try the msconfig approach first.

Thanks guys.

 
I did not mean to imply you have a bad CPU. That was just what someone else had. I mostly meant to convey that there are no real known issues with http.sys


Finding out if safemode works is step 1.
 
Back
Top