Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD Multiple reasons, totally random


  • Please log in to reply

#1
rafale

rafale

    Member

  • Member
  • PipPip
  • 12 posts
Hi


I am currently upgrading my computer with the following configuration

CPU - intel Core i3 2100 3.10ghz SandyBridge
Motherboard - intel DH67CL
RAM - G.Skill DDR3 2GB x2, 1.5v, 1333mhz, Dual Channel
HDD - Seagate 1TB SATA 6gb/s
DVD Writer
Onboard Graphics
Onboard Audio

Drivers - All original updated from intel.com
No Overclocking, stock BIOS
USB pendrive drivers
USB 2.5" WD Passport for backup

WinXP Pro SP3

New installation from on PC after full format, no imaging

Problem
PC isgiving me intermittent BSOD's with two reasons. I cannot reproduce or anticipate the BSOD, they might occur after 1hr or after 3hrs ??

PAGE_FAULT_IN_A_NON_PAGED_AREA fastfat.sys
IRQL_NOT_LESS_OR_EQUAL

I am at my wits end trying to understand the reason behind this. I have installed no new software, no device drivers. All external peripherals are old and well tested. I did have a hairy time moving WinXP to AHCI after installation, but it was working fine after that.

I have included dump files from several events to help understand the problem. I am currently not in front of this PC, so please bear me out.

What causes these BSOD's and how to remove them ??

Attached Files


  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

#3
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
rshaffer61:


I have included the report below. I am also including the dumps made by Windows_NT6_BSOD_jcgriff2.


System Information (local)
--------------------------------------------------------------------------------

computer name: COREI3
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Core™ i3-2100 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3663020032 total
VM: 2147352576, free: 2031251456



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Fri 27-01-12 5:29:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012712-01.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0xD4E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x1, 0xFFFFFFFFA5B3E4E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 25-01-12 10:02:40 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012512-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6AF0D)
Bugcheck code: 0x1000000A (0x70, 0xFF, 0x0, 0xFFFFFFFF80541F0D)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 25-01-12 6:31:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012512-01.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0xD4E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x1, 0xFFFFFFFF92E044E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 24-01-12 9:59:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012412-03.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0xD4E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x1, 0xFFFFFFFF940174E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 24-01-12 6:19:49 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012412-02.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0xD4E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x1, 0xFFFFFFFF940814E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 24-01-12 5:21:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012412-01.dmp
This was probably caused by the following module: fastfat.sys (Fastfat+0xD4E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFFC, 0x1, 0xFFFFFFFF940694E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Attached Files


  • 0

#4
AceInfinity

AceInfinity

    Visiting Staff

  • Visiting Consultant
  • 34 posts
  • MVP
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.111025-1623
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jan 25 03:02:40.640 2012 (GMT-7)
System Uptime: 0 days 3:31:08.565

First dump (most recent) pinpoints the NT kernel as the culprit, which is definitely not the case. I see invalid and/or corrupt pool headers however, and a BSOD exception caused by a write operation to memory in the second BSOD.

CPUID:        "        Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3092

You're not overclocking anything which is good.

968cb000 968cc800   avgio    avgio.sys    Thu Feb 22 07:57:32 2007 (45DDAF5C)

This old Avira driver needs to be removed. Replace this with MSE (Microsoft Security Essentials) downloadable from Microsoft.com.

Lastly, run a memory diagnostics test in case of memory corruption.

Download and run Memtest86 on boot: http://www.memtest86.com
  • Download Memtest86 and burn to disk. (If you need software to do so I would highly recommend a program called ImgBurn, and it's also free)
  • Reboot your computer and boot from the CD drive for which you have your Memtest86 disk.
    • You may need to load the Boot menu which will enable you to choose a device to boot from, otherwise you'll have to change the boot order in the BIOS to boot from CD drives as first priority before the HDD
  • Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.
  • If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.

Fastfat!FatDeferredCleanVolume+0xed:
940694cf 158ce70594      adc     eax,offset Fastfat!_imp__FsRtlIsNtstatusExpected (9405e78c)
940694d4 f6d8            neg     al
940694d6 1bc0            sbb     eax,eax
940694d8 f7d8            neg     eax
940694da c3              ret
940694db 90              nop
940694dc 90              nop
940694dd 90              nop

FastFAT.sys - FAT_FILE_SYSTEM

This driver refers to the FAT file system, and used in raid or scsi setups in Microsoft Operating System's. These kind of BSOD errors can occur if the program attempts to send in a query instruction for the filename or volume information by using an Async FileObject function. It's not standard, and very uncommon. I'd like to see what the Memtest comes up with though first.

Edited by AceInfinity, 27 January 2012 - 02:48 AM.

  • 0

#5
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
AceInfinity:

Thanks for taking the time to suggest solutions.

I had replaced Avira today with MS Security Essentials, the last BSOD happened after this. RAM had been checked through Windows Memory Diagnostics, I'll be able to conduct tests with memtest only on Saturday night. I'll report the results to you asap.

One thing I wish to add here, which might be of importance

The motherboard used by me is intel DH67CL. At the time of WinXP installation I did not use the F6 floppy route to install SATA AHCI drivers. Rather I used the workaround to update SATA AHCI Drivers from within WinXP.

There was a bit of confusion as to which was the correct driver, the AHCI download from intel site gave 13 options in the same driver file.

1) "Intel Rapid Storage Technology Driver"
2) "Intel AHCI Controller"
3) "Intel® ICH7R/DH SATA AHCI Controller"
4) "Intel® ICH7M/MDH SATA AHCI Controller"
5) "Intel® ICH9R/DO/DH SATA AHCI Controller"
6) "Intel® ICH9M-E/M SATA AHCI Controller"
7) "Intel® ICH10D/DO SATA AHCI Controller"
8) "Intel® ICH10R SATA AHCI Controller"
9) "Intel® 5 Series 4 Port SATA AHCI Controller"
10) "Intel® 5 Series 6 Port SATA AHCI Controller"
11) "Intel® 5 Series/3400 Series SATA AHCI Controller"
12) "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller"
13) "Intel® Mobile Express Chipset SATA AHCI Controller"

Based on some blog posts, I selected the #12 driver.

Is this right ??
  • 0

#6
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
Okay

The SATA Driver issue has been sorted out in intel forums, the one used by me is the recommended one.

I will test both RAM sticks individually and report the rest results by memtest tomorrow.
  • 0

#7
AceInfinity

AceInfinity

    Visiting Staff

  • Visiting Consultant
  • 34 posts
  • MVP

Okay

The SATA Driver issue has been sorted out in intel forums, the one used by me is the recommended one.

I will test both RAM sticks individually and report the rest results by memtest tomorrow.


Sounds good, sorry for my delayed reply. I'll check back on this thread tomorrow to see what updates you have :)

~Ace
  • 0

#8
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
AceInfinity:


The memory test passed, I took a photograph and have attached it FYI.


The BSOD's appeared without any warning. I mean I installed the OS from scratch, updated it, installed all drivers, all softwares etc. After I had made all the necessary tweaks and settled in, they came out of nowhere

After BSOD's I replaced Avira Antivirus with MS Security Essentials, I have no backup software, I backup manually.

I have taken an image of the system and am trying to reinstall the OS again from scratch, will report again on the results.

What else can I do ??

Attached Thumbnails

  • MemTest86 Report 29th Jan 2012.jpg

  • 0

#9
AceInfinity

AceInfinity

    Visiting Staff

  • Visiting Consultant
  • 34 posts
  • MVP
If you're really going to install the entire Operating System from scratch, then I can't suggest anything to you until you have your new OS installed, and if you get another BSOD. Just a reminder though that you should keep me updated on ALL of the most recent BSOD crash dump files so I can analyze them.

I've had past events where BSOD's were actually caused by a combination of factors, both with faulty RAM and bad drivers. So when one thing doesn't work, it's always important to keep checking the latest ones to see what's going on.

Edited by AceInfinity, 29 January 2012 - 05:44 AM.

  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Let me ask did you format the system and reinstall the OS when you upgraded?
  • 0

Advertisements


#11
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
AceInfinity:

I had 4 more BSOD's yesterday, but WhoCrashed did not find a record of them. They were of the same variety as before "fastfat.sys".

My system has been reinstalled, I am checking everything before loading additional software. Taking images after ever crucial step. Last time, BSOD's appeared after 3-4 days of successful running without any warning.

I am going to set the system on a burn in during the night.


rshaffer61:

This is a new system, so I did full format the system after partition and then installed OS from scratch. The upgrade was for hardware only.
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Once you upgrade any of the following:
  • Motherboard
  • CPU


The OS must be reinstalled as in most cases the OS will not have the correct drivers for the new stuff. If the OS is OEM then you run into a issue with the OS being married to the hardware.
  • 0

#13
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
Rshaffer:

no, you misunderstood, I have installed the OS from scratch. It is a new system, new CPU, new MB, new HDD.

The Harddisk was fully formatted after partitioning, OS was installed from nothing.
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK no problem. Is the OS disk Genuine from Microsoft or a recovery disk from a name brand system?
Since Whocrashed found no drivers causing the issues then we need to see the events that caused the issue. Also could you provide the following.

Go to Start then to Run
Type in compmgmt.msc and click Enter
On left side click on Disk Management
On right side you will see you hard drive.
Now I need you to take a screenshot and attach it to your next reply. Do the following to take a screenshot while the above is open and showing on your desktop.

To do a screenshot please have click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start and then to All Programs
Scroll to Accessories and then click on Paint
In the Empty White Area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop


Attach it to your next reply





  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Double-click VEW.exe
  • Under 'Select log to query', select (as appropriate):
    • Application
    • System
  • Under 'Select type to list', select (as appropriate):
    • Error
    • Information
    • Warning
Then use the 'Date of events' or 'Number of events' as follows:

Either:
  • Click the radio button for 'Number of events'
    Type 3 in the 1 to 20 box (or any number from 1 to 20)
    Then click the Run button.
    Notepad will open with the output log.

  • Click the radio button for 'Date of events'
    In the From: boxes type today's date (presuming the crash happened today) 28 01 2012
    In the To: boxes type today's date (presuming the crash happened today) 29 01 2012
    Then click the Run button.
    Notepad will open with the output log.
Please post the Output log in your next reply
  • 0

#15
rafale

rafale

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
rshaffer61:

I have just reinstalled my system, I'll wait for a day after burning in. I should be in a position to post this information after a day or so.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP