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: third time BSOD lucky. help!


08 Apr 2010   #1

Microsoft Windows 7 Home Premium, 64-bit
 
 
third time BSOD lucky. help!

I am getting really depressed about this, I have never really had BSOD problems before, after all the smack talk about Vista, I already miss it. I have run Memcheck CD and it passed 6 times, shall I try it again? Or is something else amiss, some chaps have suggested network drivers for the Broadcom Gigabit 57xx but I am not sure how to do this since when I tried downloading the latest, it does not seem to change the driver version number, even though the date of that is older than implied on the download webpage.


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 2010-04-08 17:48:48 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CF5694)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\040810-15693-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 2010-04-08 15:06:12 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009FA7118, 0xFFFFF88009FA6970, 0xFFFFF80002CD4105)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040810-19827-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 2010-04-08 06:18:57 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008E2FBC8, 0xFFFFF88008E2F420, 0xFFFFF80002CAB77E)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040810-16270-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 2010-04-06 01:34:41 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A775F98, 0xFFFFF8800A7757F0, 0xFFFFF80002CF1B74)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040610-16270-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 2010-04-05 19:43:59 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0xD1 (0xFFFFF8800150DC7C, 0x2, 0x8, 0xFFFFF8800150DC7C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040510-18891-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 2010-04-05 01:01:20 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880099EE0A8, 0xFFFFF880099ED900, 0xFFFFF80002D3A1DB)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040510-17035-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 2010-04-02 09:49:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002CFD090)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040210-23400-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 2010-04-02 09:00:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1 (0x74B8FEDA, 0x0, 0xFFFF0000, 0xFFFFF880095BD320)
Error: APC_INDEX_MISMATCH
Dump file: C:\Windows\Minidump\040210-15256-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 2010-03-29 17:32:48 your computer crashed
This was likely caused by the following module: netio.sys
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF80002CFE35F)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032910-14383-01.dmp
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 2010-03-27 13:14:52 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFAD505CF1F90, 0x2, 0x0, 0xFFFFF80002D2CA8F)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032710-14913-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 2010-03-25 22:42:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8002074680, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032510-17409-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 2010-03-22 16:36:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A8CD54)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\032210-14866-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 2010-03-17 05:08:52 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000B9A2E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\031710-22916-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 2010-03-14 14:35:03 your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0xFE (0x5, 0xFFFFFA8008C5B1A0, 0x80863B34, 0xFFFFFA8009369C50)
Error: BUGCODE_USB_DRIVER
Dump file: C:\Windows\Minidump\031410-15132-01.dmp
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 2010-03-14 12:50:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AB24A8, 0xFFFFF880033E0888, 0xFFFFF880033E00E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\031410-19437-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



My System SpecsSystem Spec
.

08 Apr 2010   #2

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hello Welcome to SF !!

I guess multilple issues are going on. First NETIO.sys is a Network bug so i would recommend to reinstall your Ntwork driver. Update your BIOS Firmware. If your Overclocking please stop. Uninstall any third party Antivirus or Firewall. Also i see Memory corruption.

Quote:
Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW
Code:
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002cf5694
Debugging Details:
------------------

BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  Azureus.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002c77469 to fffff80002c77f00
STACK_TEXT:  
fffff880`0311bde8 fffff800`02c77469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0311bdf0 fffff800`02c75932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0311bf30 fffff800`02cf5694 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0a1cdf00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x409ec

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
32 errors : !nt (fffff80002c77a06-fffff80002cf57be)
fffff80002c77a00  48  83  ec  28  48  8b *cd  40  0f  ae  08  48  8b  41 *d5  66 H..(H..@...H.A.f
fffff80002c77a10  0f  6f  70  30  66  0f *58  78  40  66  44  0f  6f  40 *19  66 .op0f.Xx@fD.o@.f
fffff80002c77a20  44  0f  6f  48  60  66 *6a  0f  6f  50  70  66  44  0f *e0  98 D.oH`fj.oPpfD...
fffff80002c77a30  80  00  00  00  66  44 *2b  6f  a0  90  00  00  00  66 *23  0f ....fD+o.....f#.
...
fffff80002cf5680  41  f6  c4  01  0f  85 *d0  04  00  00  48  bf  00  d0 *3e  7d A.........H...>}
fffff80002cf5690  fb  f6  ff  ff  41  f6 *91  02  75  10  49  8b  cc  e8 *57  58 ....A...u.I...WX
fffff80002cf56a0  f7  ff  3c  01  0f  84 *02  04  00  00  42  f6  04  d7 *fa  0f ..<.......B.....
fffff80002cf56b0  84  e8  1a  00  00  f6 *4d  01  0f  84  df  1a  00  00 *e5  8b ......M.........
...
fffff80002cf5700  8b  c0  49  8b  d5  b9 *f8  00  00  00  48  c7  44  24 *d7  0a ..I.......H.D$..
fffff80002cf5710  00  00  00  e8  e8  27 *f1  ff  cc  41  f6  c7  08  0f *ef  e2 .....'...A......
fffff80002cf5720  00  00  00  49  bb  00 *5f  00  00  00  00  00  80  4d *ed  c3 ...I.._......M..
fffff80002cf5730  0f  84  cf  00  00  00 *9a  8b  cc  49  8b  d5  b9  fc *e3  00 .........I......
...
fffff80002cf5780  ff  cc  48  c1  e8  0c *dc  b9  ff  ff  ff  ff  0f  00 *80  00 ..H.............
fffff80002cf5790  48  23  c1  48  8d  0c *09  48  b8  00  00  00  00  80 *c8  00 H#.H...H........
fffff80002cf57a0  00  48  c1  e1  04  48 *f9  c8  48  8b  41  28  48  c1 *c1  39 .H...H..H.A(H..9
fffff80002cf57b0  a8  01  0f  85  e5  19 *f0  00  66  83  79  18  01  77 *ac  8b ........f.y..w..
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  STRIDE
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
Hope this helps,
Captain
My System SpecsSystem Spec
09 Apr 2010   #3

Microsoft Windows 7 Home Premium, 64-bit
 
 

Hi
Well, I have run Memtest 3 times now, all 3 times it ran 6 passes over 10+ hours and detected no errors, is there anything else that could look like memory corruption that is not the physical memory itself?

I also suspect the network driver, but am not sure about the best/safest way to do that, since I am worried about finding myself without a working network connection. Do I uninstall something via control panel, or device manager?

I am not overclocking, but am running Avira antivirus, if I take that down, what should I use instead?

I have "hunches" that Internet Explorer has misbehaved (had a few crashes when I tried to close tabs or with pages that didnt display properly due to missing flash or java etc). Also Vuze torrent program is often running,and Truecrypt to access my external hard drive, which I have seen errors about in the event viewer.

So frustrating!
My System SpecsSystem Spec
.


09 Apr 2010   #4

Microsoft Windows 7 Home Premium, 64-bit
 
 

OK

in device manager, I can see

Broadcom Netlink (TM) Gigabit Ethernet
Driver Provider: Broadcom
Driver Date: 2009-08-06
Driver Version: 12.2.2.2
Digital Signer: Microsoft Windows Hardware Compatability Publisher

I can see an uninstall option here, problems are

1. Where do I see what chipset this card is
Broadcom.com - Ethernet NIC Driver Downloads

I dont know which of that list mine is, and it seems important since there about 20 different downloads for each 57xx chipset

2. when I find that, the pages for each one seem not to have Windows 7 options. eg
Broadcom.com - Ethernet NIC NetLink Driver Downloads

do I pick the Windows Vista 64 bit ones?


thx for any help
My System SpecsSystem Spec
09 Apr 2010   #5

Microsoft Windows 7 Home Premium, 64-bit
 
 

can anyone help?
thanks..
My System SpecsSystem Spec
09 Apr 2010   #6

windows ultimate 7 64 bit
 
 

try dell website for spec of your system or the documentation that came with the computer. or go into device manager double click the item you want and click details. theres many options for different details in there
My System SpecsSystem Spec
09 Apr 2010   #7

Windows 7 - Vista
 
 

The bugcheck 0x24 = NTFS file system - noted numerous times in your 1st post.

0x24 = hard drive. Run chkdsk /r

Regards. . .

jcgriff2

.
My System SpecsSystem Spec
Reply

 third time BSOD lucky. help!




Thread Tools



Similar help and support threads for2: third time BSOD lucky. help!
Thread Forum
Installed Win 7 on 40 machines and no issues or BSOD's. Am I lucky? Chillout Room
Very Lucky Driver And Passengers Chillout Room
my lucky day Chillout Room
I'm sooooo lucky. Chillout Room
Lucky Number Seven? News

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 02:12 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33