Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Multiple BSOD's on Windows XP Pro SP3 clean install, IRQL, PFN, and more


  • Please log in to reply
26 replies to this topic

#1 Wrathcaster

Wrathcaster

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 04:34 PM

Greetings,

I got a virus a while back (XP Antivirus 2011) and after managing to remove it I noticed autoupdates were disabled. After attempting to re-enable autoupdates (never could), I started experiencing periodic bluescreens while gaming in Warhammer 40,000: Dawn of War II: Retribution. I couldn't get Autoupdates to work, was tired of trying to nail down the problem, so I decided to start anew. At that time I was using XP Home Basic SP3.

The first thing I attempted was to install the Windows 7 Home Premium Upgrade. After booting from disc (I was getting blue screens trying to install it within windows) and formatting the partition, and installing on the formatted drive, I was unable to make it past entering product key after finished install. I would get blue screens before I could ever enter Windows.

Frustrated, I got a copy of XP Pro SP3 on a disc and used it to format the partition again and perform a fresh install of XP SP3 that way. I was able to get all the way through install and booted up fine. I went through and updated my drivers (mobo, sound card, video card, couldn't get any for my HDD or SCSI/RAID). The PC seemed stable for a while and I avoided installing any new software, but after I began using Internet Explorer, firefox, and later trying to play Dawn of War II, I was experiencing Blue Screens seemingly at random, the most common being IRQL_NOT_OR_LESS_EQUAL. Please note that I could not install the SCSI/RAID drivers in Windows XP boot-to-disk install because my PC does not have a floppy drive and the only drivers for the SCSI/RAID controller that came with my motherboard were on floppy. I've got a floppy drive shipping to me as I post this.

I have noticed a pattern in the blue screens. Most often, they occur when I:

1.) Open a new tab or two in firefox
2.) Open a folder or several folders in windows explorer
3.) 15-20 minutes into playing Dawn of War II
4.) Other times, randomly, when opening a program or performing an action such as copying/pasting something.

My system specs are as follows:

OS:
Windows XP Professional SP3

Motherboard:
EVGA Nforce 4 133-K8-NF41

CPU:
AMD Athlon 64 X2 4200+

RAM:
2gb Corsair XMS DDR2

Video:
PNY Geforce 250 GTS 1gb

HDD:
Maxtor 6 L160M0 SCSI Disk Device

Audio:
Sound Blaster X-Fi

I've got latest drivers available for the motherboard (legacy drivers from Nvidia's site), video card, Sound card
I've got all the latest updates from Microsoft as downloaded from Automatic Updates.

Other than Steam, Firefox, Dawn of War II: Retribution, Internet Download Manager, BlueScreenView, Seatools, and Nvidia Control Panel there are no installed programs apart from what came bundled with XP Pro SP3.

No recent hardware changes. After running chkdisk, HDD was reported fine. Last time I ran Memtest (about a week ago) RAM checked out fine. Windows 7 Installer tested RAM and it came back ok too. I'm thinking it may have something to do with the SCSI driver auto-installed by XP being out of date/wrong... But I don't really know how to confirm this and until I get the floppy drive installed I have no way of testing it that I know of. I'm fairly certain this is a driver issue but I need help. Appreciate any that can be lended.

Here's the latest report from BlueScreenView. I can post more if need be.

Mini061711-01.dmp
6/17/2011 4:49:20 AM
IRQL_NOT_LESS_OR_EQUAL
0x1000000a
0x00000004
0x00000002
0x00000000
0x804e7f0d
ntoskrnl.exe
ntoskrnl.exe+10f0d
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6055 (xpsp_sp3_qfe.101209-1646)
32-bit
ntoskrnl.exe+10f0d
ntoskrnl.exe+2d4e6
ntoskrnl.exe+c7bbc
ntoskrnl.exe+c63fb

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:39 PM

Posted 16 June 2011 - 04:42 PM

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Compliments of Broni

#3 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 04:44 PM

I only have info from two .dmp files because I reinstalled Windows XP SP3 early last night. Give me a few more hours and I'll have plenty more, if needed.

==================================================
Dump File : Mini061711-01.dmp
Crash Time : 6/17/2011 4:49:20 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804e7f0d
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+10f0d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646)
Processor : 32-bit
Crash Address : ntoskrnl.exe+10f0d
Stack Address 1 : ntoskrnl.exe+2d4e6
Stack Address 2 : ntoskrnl.exe+c7bbc
Stack Address 3 : ntoskrnl.exe+c63fb
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061711-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini061611-01.dmp
Crash Time : 6/16/2011 6:59:31 AM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x805b0550
Parameter 2 : 0x005b0121
Parameter 3 : 0xb0483b6c
Parameter 4 : 0x0000000a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+12402
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646)
Processor : 32-bit
Crash Address : ntoskrnl.exe+12402
Stack Address 1 : ntoskrnl.exe+2940d
Stack Address 2 : ntoskrnl.exe+b7c50
Stack Address 3 : ntoskrnl.exe+29667
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061611-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:39 PM

Posted 16 June 2011 - 04:45 PM

How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    Posted Image
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    Posted Image

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    Posted Image
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :)

Compliments of Billy O'Neal.

#5 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 06:26 PM

Running Memtest now. It's been at work for 34 minutes now. How long can I expect it to continue until I get the "Pass complete, no errors" message?

#6 killerx525

killerx525

    Bleepin' Aussie


  • Members
  • 7,220 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Melbourne, Australia
  • Local time:08:39 AM

Posted 16 June 2011 - 06:31 PM

Varies time. Let it pass 10 times not just once.

>Michael 
System1: CPU- Intel Core i7-5820K @ 4.4GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws 16GB Kit(4Gx4) DDR3 2133MHz, SSD/HDD- Samsung 850 EVO 250GB/Western Digital Caviar Black 1TB/Seagate Barracuada 3TB, GPU- 2x EVGA GTX980 Superclocked @1360/MHz1900MHz, Motherboard- Asus X99 Deluxe, Case- Custom Mac G5, PSU- EVGA P2-1000W, Soundcard- Realtek High Definition Audio, OS- Windows 10 Pro 64-Bit
Games: APB: Reloaded, Hours played: 3100+  System2: Late 2011 Macbook Pro 15inch   OFw63FY.png


#7 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 06:42 PM

Done. Memtest reported no errors.

#8 killerx525

killerx525

    Bleepin' Aussie


  • Members
  • 7,220 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Melbourne, Australia
  • Local time:08:39 AM

Posted 16 June 2011 - 06:43 PM

Tested the hard drive yet for errors?

>Michael 
System1: CPU- Intel Core i7-5820K @ 4.4GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws 16GB Kit(4Gx4) DDR3 2133MHz, SSD/HDD- Samsung 850 EVO 250GB/Western Digital Caviar Black 1TB/Seagate Barracuada 3TB, GPU- 2x EVGA GTX980 Superclocked @1360/MHz1900MHz, Motherboard- Asus X99 Deluxe, Case- Custom Mac G5, PSU- EVGA P2-1000W, Soundcard- Realtek High Definition Audio, OS- Windows 10 Pro 64-Bit
Games: APB: Reloaded, Hours played: 3100+  System2: Late 2011 Macbook Pro 15inch   OFw63FY.png


#9 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 07:07 PM

I ran chkdisk and defrag, but is there something else I should try?

#10 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:39 PM

Posted 16 June 2011 - 07:12 PM

If memory tests out okay, then I would suspect a bad cpu. check to make sure that there is ample thermal paste on it.

#11 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 07:32 PM

There appears to be an ample amount of thermal paste... But I'm not totally sure, how do I determine if the CPU's bad? It's reading out fine in CPUID... Not really sure what to do?

#12 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 07:56 PM

While waiting on any more posts, I ran DoWII again to reproduce another BSOD. I managed to snag 2 more. First happened approximately 20 minutes into a LAN session against 2 AI opponents.

==================================================
Dump File : Mini061711-03.dmp
Crash Time : 6/17/2011 6:26:16 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x8780870c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x80702a16
Caused By Driver : hal.dll
Caused By Address : hal.dll+2a16
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5687 (xpsp_sp3_qfe.080930-1426)
Processor : 32-bit
Crash Address : hal.dll+2a16
Stack Address 1 : ntoskrnl.exe+953be
Stack Address 2 : ntoskrnl.exe+96dc2
Stack Address 3 : ntoskrnl.exe+9c46b
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061711-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini061711-02.dmp
Crash Time : 6/17/2011 6:25:09 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x0000000d
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+126581
File Description : NVIDIA Windows XP Display driver, Version 275.33
Product Name : NVIDIA Windows XP Display driver, Version 275.33
Company : NVIDIA Corporation
File Version : 6.14.12.7533
Processor : 32-bit
Crash Address : nv4_disp.dll+126581
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061711-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

#13 dpunisher

dpunisher

  • BC Advisor
  • 2,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South TX
  • Local time:04:39 PM

Posted 16 June 2011 - 08:24 PM

Just a few observations after doing this for awhile.

2 things cause BSODS during OS installs- bad/dirty install media, bad memory. I am sure I had other install problems on occasion, but I don't remember them (it was the 90's).

Memtest, and Windows Memory Test many times don't catch borderline memory. Too many times in the early days I got bitten by bad memory and it sticks with me. Couple of things- if you have the BIOS option, bump memory voltage a tenth and see if that changes anything. You can also pull one stick at a time as well.

I am a retired Ford tech. Next to Fords, any computer is a piece of cake. (The cake, its not a lie)

3770K @4.5, Corsair H100, GTX780, 16gig Samsung, Obsidian 700 (yes there is a 700)


#14 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 09:08 PM

We can probably eliminate the bad/dirty media issue. All OS install disks I used were brand new.

It may be the memory issue, but I'm somewhat perplexed as to how it's cropped up just recently. Until I tried to Re-enable automatic updates, I could play games, surf the web, etc. fine without Blue Screens. I screwed with some registry and services settings I most likely should not have, and went above my own expertise and knowledge a bit, but I had not BSOD issues until after I'd performed virus removal and attempted the Automatic Update enable... Should be worth noting that after the virus removal, the Automatic Updates service wasn't even on my PC in services list, in registry, anything... I was following along another guy's post over at techsupportguy.com since I couldn't get a response from them, and ran several tools I shouldn't have without personal expert assistance (ComboFix, OTL, AOSS). I don't know if these could have corrupted my memory somehow? I figured anything I may have mucked up in Windows with these would've been alleviated with a clean install... But I was wrong.

#15 Wrathcaster

Wrathcaster
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:04:39 PM

Posted 16 June 2011 - 09:55 PM

dpunisher-

I bumped my VRAM setting down a tenth as suggested. Ran DoW2 for around 30 minutes before the program crashed (no bluescreen, the game itself crashed citing AI error). After ~30 minutes I tried running the game again and got another bluescreen this time apparently citing Nvidia Display Drivers:

==================================================
Dump File : Mini061711-04.dmp
Crash Time : 6/17/2011 10:50:39 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xa5a1643c
Parameter 2 : 0x00000000
Parameter 3 : 0xbd0a1168
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+8f168
File Description : NVIDIA Windows XP Display driver, Version 275.33
Product Name : NVIDIA Windows XP Display driver, Version 275.33
Company : NVIDIA Corporation
File Version : 6.14.12.7533
Processor : 32-bit
Crash Address : nv4_disp.dll+8f168
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061711-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users