BSOD on shut down three times in last week.

OS Windows 7 64bit sp1 4gb Ram


HI i was shuting down my pc last week after using it all day with no problems when a blue screen appeared and the machine rebooted.I shut it down properly and it was fine the next few days . then i the same thing happened twice in a week.only on shutdown.the most recent program i installed a few weeks ago was Protools8.



using whocrashed i got this report.

System Information (local)
computer name: RICO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 440 @ 2.00GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 3479691264 total
VM: 2147352576, free: 1945632768


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 14/12/2011 00:57:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-29608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C2FCC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F13FCC, 0xFFFFF880020FF838, 0xFFFFF880020FF090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 14/12/2011 00:49:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-21278-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88004E34210, 0xFFFFF88004E342B0, 0xFFFFF80002CF8590)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Thu 08/12/2011 01:18:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-19858-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C31C9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ED31C9, 0xFFFFF88002F38838, 0xFFFFF88002F38090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


I also followed your instructions on the help page and created the below zip files.

batrico said:

OS Windows 7 64bit sp1 4gb Ram


HI i was shuting down my pc last week after using it all day with no problems when a blue screen appeared and the machine rebooted.I shut it down properly and it was fine the next few days . then i the same thing happened twice in a week.only on shutdown.the most recent program i installed a few weeks ago was Protools8.



using whocrashed i got this report.

System Information (local)
computer name: RICO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 440 @ 2.00GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 3479691264 total
VM: 2147352576, free: 1945632768


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 14/12/2011 00:57:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-29608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C2FCC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F13FCC, 0xFFFFF880020FF838, 0xFFFFF880020FF090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 14/12/2011 00:49:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-21278-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88004E34210, 0xFFFFF88004E342B0, 0xFFFFF80002CF8590)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Thu 08/12/2011 01:18:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-19858-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C31C9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ED31C9, 0xFFFFF88002F38838, 0xFFFFF88002F38090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


I also followed your instructions on the help page and created the below zip files.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- 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).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users


Also Old drivers needing updating

Code:

regi.sys    4/16/2007 10:19:10 AM        fffff880`04736000    fffff880`0473e000    0x00008000    0x462393ee                        
irsir.sys    1/19/2008 1:36:11 AM        fffff880`043f2000    fffff880`043fe000    0x0000c000    0x47919a5b                        
Rtnic64.sys    3/31/2008 12:39:38 AM        fffff880`037da000    fffff880`037ee000    0x00014000    0x47f0791a                        
MDPMGRNT.SYS    7/6/2009 4:05:22 PM        fffff880`01969000    fffff880`01976000    0x0000d000    0x4a526712

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

i did the verifier process and it crashed on start up.here is the crash dump report.

On Wed 14/12/2011 20:26:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-27877-01.dmp
This was probably caused by the following module: dgmbx2fu.sys (dgmbx2fu+0xA36)
Bugcheck code: 0xC9 (0x23B, 0xFFFFF88004C79A36, 0xFFFFF9800631ACA0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\dgmbx2fu.sys
product: Digidesign Mbox 2
company: Avid Technology, Inc.
description: Mbox 2 Firmware Driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dgmbx2fu.sys (Mbox 2 Firmware Driver, Avid Technology, Inc.).
Google query: dgmbx2fu.sys Avid Technology, Inc. DRIVER_VERIFIER_IOMANAGER_VIOLATION

batrico said:

i did the verifier process and it crashed on start up.here is the crash dump report.

On Wed 14/12/2011 20:26:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-27877-01.dmp
This was probably caused by the following module: dgmbx2fu.sys (dgmbx2fu+0xA36)
Bugcheck code: 0xC9 (0x23B, 0xFFFFF88004C79A36, 0xFFFFF9800631ACA0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\dgmbx2fu.sys
product: Digidesign Mbox 2
company: Avid Technology, Inc.
description: Mbox 2 Firmware Driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dgmbx2fu.sys (Mbox 2 Firmware Driver, Avid Technology, Inc.).
Google query: dgmbx2fu.sys Avid Technology, Inc. DRIVER_VERIFIER_IOMANAGER_VIOLATION

And again we need the most recent dmp.

Sorry how would i do that?

batrico said:

Sorry how would i do that?

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

crash dump is below.Im 99percent sure its the mac2 pro tools audiobox driver since i hadnt any blue screens till i installed it.

current situation is ive been using pc all day .no errors.only noticed there was a problem when i hit shutdown08/12/2011 01:18:52 GMT a blue screen appeared. then it didnt happen till 14/12.both occasions i had the mbox 2 connected via usb.also the blue screens also only appeared once after i reboooted - no blue screen.

batrico said:

crash dump is below.Im 99percent sure its the mac2 pro tools audiobox driver since i hadnt any blue screens till i installed it.

Could be but nothing in the DMP points to it.


I notice your avast which is often at least a contributing cause of BSOD'S . Please remove and replace your Avast with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

Hi Zigzag sorry its been 6 days but i wanted to give my system a few days to see if i have any more problems.I have made sure I have the mbox disconnected when i shut down my computer at night and hence ive had no bsod errors.Thanks for your interest in my problem.