bsod round 2

[w7sucks]

Windows 7 . . .
- x64 ?
- original installed OS on the system
- an OEM
- OEM purchased it from retailer

- 1 year old
- Reinstalled a week ago

 

[JMH]

Windows 7 . . .
- x64 ?
- original installed OS on the system
- an OEM
- OEM purchased it from retailer

- 1 year old
- Reinstalled a week ago

Is there something you wish to ask or seek help with?
Or is this a rant attempt?
I can't agree with your what you imply with your user name.

 

[w7sucks]

I really need to get these BSOD issues resolved i put her together a year ago and i have been haunted with bsod since day 1 i have followed the steps that i am supposed to follow when posting a new thread if there is anything else you or anyone might need feel free to ask.

 

[w7sucks]

bump

 

[w7sucks]

WTF people

 

[ttran]

Hi there!

I can't understand why you tell us that kind of thing. But I will help you anyway because I don't want other people to misunderstood us. But as we serve you voluntarily, perhaps you can give us a little respect my friend

First of all, all of your stop codes are somehow suggest 3rd party antivirus are causing all of these. Please remove Norton/Symantec antivirus completely to see if the problem is solved.
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Install MSE instead:
Security Essentials Software Support | Microsoft Security Essentials

BugCheck 3B, {c0000005, fffff960001176fa, fffff8800932fb90, 0}

Probably caused by : win32k.sys ( win32k!RFONTOBJ::bMakeInactiveHelper+2e )

Followup: MachineOwner
---------
BugCheck 50, {fffff8a80476c008, 0, fffff80002d425d1, 5}


Could not read faulting driver name
Probably caused by : discache.sys ( discache!DisCreateObjectAttributeStore+ec )

Followup: MachineOwner
---------
BugCheck A, {fffffa8004a83090, 2, 0, fffff80002a7868b}

Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8b )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

Followup: MachineOwner
---------
BugCheck 50, {fffff68004001a70, 0, fffff80002acd2e2, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

Followup: MachineOwner
---------
BugCheck 1A, {41284, fffff980082b6001, 3b5e, fffff780c0000000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

Followup: MachineOwner
---------
BugCheck 50, {fffffd7fffffffeb, 0, fffff80002a9e5ff, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )

Followup: MachineOwner
---------

Run system file check please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Regard,

Tuan

 

[JMH]

Windows 7 . . .
- x64 ?
- original installed OS on the system
- an OEM
- OEM purchased it from retailer

- 1 year old
- Reinstalled a week ago

bump

WTF people

I support what ttran just said -

I can't understand why you tell us that kind of thing. But I will help you anyway because I don't want other people to misunderstand us. But as we serve you voluntarily, perhaps you can give us a little respect my friend

Perhaps your attitude problem is why help has not been forthcoming in a faster manner.
I suggest you rethink how you approach seeking help in the future.

Jan.